Feature Requests & Bugs

Today, there are two sets of data that a user utilizes: YNAB data Lumy data The first is "synced" by virtue of being on YNAB's servers. The second is never synced and remains local to the user's device. This includes: Frugal month data Spend trackers Category views Settings This data is lost if the app is uninstalled, but can be exported and imported on a new device. Note that as of 5/19/24 frugal months and app settings are not exported. While this was initially a security precaution (Lumy was designed to be local-only), some have found it confusing as the general expectation is that our account data follows us across devices. We should allow device sync (should it be the default?) by virtue of a proper backend. Note that this would require users to have a Lumy account (which would likely be tied to their YNAB account id).

Popular feature request for non-mobile users, but obviously a pretty big undertaking, both in development and support Notes: Need to support Lumy Premium (Stripe?), provide alternate PremiumStore implementation

Add a chart as a widget to the home screen, or maybe a spend tracker. Current thoughts/ideas: Highlights (left to spend, overspent, over budgeted) Spent this month Burndown In future: Goal progress (based on target or Lumy native goal)

When changing a category group name, the change is not sent back in delta requests, meaning group names become stale UNTIL a category within that group is modified, which is then sent back in a delta request including the changes for the surrounding group. Steps to reproduce: Make Postman request to categories, take note of last knowledge. Change group name in YNAB Make delta request, no change is sent (but server knowledge does increment) Delete or rename category in the group Make another delta request, change is sent back.