NetWorth 1.8

I’ve just uploaded a v1.8 release of NetWorth, my personal finance / net worth tracking / budgeting app for Android.

NetWorth 1.8 Fancy Graphing

Changes in v1.8

  • Replaced the graphing library used previously with MPAndroidChart. Graphs now look a lot better, and support a variety of touch gestures which ultimately expose a lot more information.
  • During a future projection, per-account data points are now captured. These can be viewed as a graph or a list by tapping the account within the projection balances list, as well as the budget items that affected the account during this projection, and by how much.
  • Expected performance is now plotted on the snapshot graph with your actual performance.
  • Fixed a very unpleasant and embarassing bug for new users where the budget activities would crash if you didn’t have any budget entries defined already.
  • Fixed bug with scheduled transfer transactions and account start dates when the destination starts later than the source.
  • Fixed bug where expected data is lost if you edit a snapshot.
  • Fixed the upgrade to pro / settings menu items opening each other.

Possible Upcoming Features

  • Implement expected taxation on investment accounts. (would likely require specifying the taxable amount in snapshots)
  • Allow flagging accounts as usable in retirement and allow viewing these separately in projection results. (eliminate short term cruft or assets you can’t really use in retirement from your net worth)
  • Retirement planning in general, calculate the date at which your expenses are less than 4-5% of your usable net worth. (will require users to properly flag budget end dates)
  • Complete overhaul of the budget overview page.
  • Mechanism to “save” a projection as a goal and compare how you actually did when you get there.
  • Add credit line/card accounts.
  • Implement better asset depreciation.

Future Considerations

The app is quite useful in it’s current state, but I’m very aware the user experience, especially for getting your initial data set up, needs a lot of work. My TODO list is currently 50 items long, and at the top of it are a variety of improvements that desperately need to be made for the fragments where you create accounts and budget transactions, the very first thing new users see and need to get through if the app is going to be of any use.

Despite this I’m pondering if it’s worth a port to React Native. This carries the promise of faster development, should get me very close to an iOS version, provide a chance to improve the account/budget creation, and get me some much needed Javascript experience. The level of abstraction involved is pretty worrisome to me however, I have a hard time seeing how it would be anything but a constant source of pain trying to replicate what you can do with the native SDK, but it appears to be popular with developers who are using it and might be worth a short experiment to see just how much the framework offers vs gets in the way.

comments powered by Disqus