A prototype hledger application for Android
120 views
Skip to first unread message
Emanuele Petriglia
Jun 7, 2023, 2:43:08 PM6/7/23
to hledger
Hello everyone!
I'm Emanuele, a student at the University of Milano-Bicocca in Italy. Three months ago I sent an email asking for the hledger file format reference for an exam project. Three months later, here is the result: a fully functional prototype, using the Flutter framework.
The application is more advanced than cone[0], and it is a standalone application, not a web frontend like MoLe[1].You can set up a hledger file (or create a new one) and use the application to view the transactions and some analytical data: the balances, the accounts and others. The user can edit a transaction, create a new one or delete. The modified data is automatically written to the selected file, just like what `hledger add` does.
The application is in a prototype state. It works and I use it every day, because we designed it to support my workflow. It doesn't have many features like hledger, because they are not easy to implement (at the moment the application can only parse and generate a subset of the hledger file format), others because I don't use them.
Now for the future: I would like to release this application on F-Droid as free and open source software. But there is a big technical problem: this was our first application using the Flutter framework and the Dart language: we made a lot of mistakes and there is, after only three months, there is a lot of technical debt. So I thought of a solution: in early autumn I'm going to rewrite it in Flutter, but with idiomatic code and patterns, then I'm going to release the source code and try to publish the application on F-Droid. I use hledger every day, so I have a strong need to develop a solution on the smartphone, and this application can be a solution (but *my* solution, maybe not for other users).
[0]: https://f-droid.org/packages/info.tangential.cone
[1]: https://f-droid.org/it/packages/net.ktnx.mobileledger/
I'm Emanuele, a student at the University of Milano-Bicocca in Italy. Three months ago I sent an email asking for the hledger file format reference for an exam project. Three months later, here is the result: a fully functional prototype, using the Flutter framework.
The application is more advanced than cone[0], and it is a standalone application, not a web frontend like MoLe[1].You can set up a hledger file (or create a new one) and use the application to view the transactions and some analytical data: the balances, the accounts and others. The user can edit a transaction, create a new one or delete. The modified data is automatically written to the selected file, just like what `hledger add` does.
The application is in a prototype state. It works and I use it every day, because we designed it to support my workflow. It doesn't have many features like hledger, because they are not easy to implement (at the moment the application can only parse and generate a subset of the hledger file format), others because I don't use them.
Now for the future: I would like to release this application on F-Droid as free and open source software. But there is a big technical problem: this was our first application using the Flutter framework and the Dart language: we made a lot of mistakes and there is, after only three months, there is a lot of technical debt. So I thought of a solution: in early autumn I'm going to rewrite it in Flutter, but with idiomatic code and patterns, then I'm going to release the source code and try to publish the application on F-Droid. I use hledger every day, so I have a strong need to develop a solution on the smartphone, and this application can be a solution (but *my* solution, maybe not for other users).
I leave you with some screenshots and a demo video with dummy data. Let me know if you like it!
The video is too big, here is a link to my Google Drive:
[1]: https://f-droid.org/it/packages/net.ktnx.mobileledger/
Simon Michael
Jun 7, 2023, 2:55:47 PM6/7/23
to hledger
Hello again Emanuele. Congratulations on the progress, and thanks for the update!
--
You received this message because you are subscribed to the Google Groups "hledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hledger+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hledger/80078e71-d7c7-475f-af4a-3d36e6f06836n%40googlegroups.com.
<2_transactions_page.png><5_expenses_page.png><4_payees_page.png><3_edit_transaction_dialog.png><6_burger_menu.png><1_homepage.png>
Simon Michael
Jun 7, 2023, 3:02:29 PM6/7/23
to hledger
PS what are the chances of seeing it on IOS (ipados, macos..) also ?
To view this discussion on the web visit https://groups.google.com/d/msgid/hledger/BE65F954-9C73-4A27-B172-2CDD855BEA87%40joyful.com.
Aimuz me
Jun 7, 2023, 10:05:38 PM6/7/23
to hledger
Cool, does he work on iOS?
Emanuele Petriglia
Jun 9, 2023, 4:16:56 AM6/9/23
to hledger
Hello there!
Flutter is designed to create cross-platform applications, so in theory the application can be built and can run on iOS. However there are two problems:
1. Design: my group and I have developed the application following the Material Design, because the target is Android. To make a version for iOS, we have two options: 1) Write specific widgets in iOS style and show them when the application is running on iOS, 2) Make an agnostic design for both platforms.
2. Hardware: to build an application for iOS I need MacOS and an iPhone (at least for testing). I do not have such hardware.
When I rewrite the application to solve the technical debt I'll focus on Android, but the source code will be available so anyone can work on it.
Have a nice day!
Flutter is designed to create cross-platform applications, so in theory the application can be built and can run on iOS. However there are two problems:
1. Design: my group and I have developed the application following the Material Design, because the target is Android. To make a version for iOS, we have two options: 1) Write specific widgets in iOS style and show them when the application is running on iOS, 2) Make an agnostic design for both platforms.
2. Hardware: to build an application for iOS I need MacOS and an iPhone (at least for testing). I do not have such hardware.
When I rewrite the application to solve the technical debt I'll focus on Android, but the source code will be available so anyone can work on it.
Have a nice day!
Reply all
Reply to author
Forward
0 new messages