Bug fixes and performance improvements

- Fixes an issue where the app may request write access even after being granted it. - Fixes an issue where transaction templates would not reflect the settings they were created with (fire immediately, flag, etc.).

- Fixes an issue where transaction templates would not reflect the settings they were created with (fire immediately, flag, etc.).

Fixes: - Fixes an issue with currency input for some currencies in the transaction template screens. Previously, currency input was constrained to too small an input length, but that constraint has been lifted and large amounts are better supported. Changed: - As part of the above fix, all currency input across the app is now the same. This applies primarily to frugal months and transaction templates, but will apply to any future inputs as well. - Sub-transaction amount input for transaction templates is no longer done via a modal. Instead, input occurs directly on the transaction template screen for more rapid entry.

New: - Introduces device syncing capabilities, allowing you to automatically back up your Lumy data and access it on other devices by linking your email address. Existing users will be prompted to link an email address but maintain the option to continue as a guest. Those who choose the "guest" option can continue using Lumy without linking an email, but are at risk of data loss in the event of a logout or uninstall (the same as before!). Now, users with a mobile device and tablet (or multiple mobile devices!) can easily use the same Lumy data across their devices. Important Notes (please read!): - This was a major architectural overhaul as this type of functionality wasn't planned from the beginning. Most obstacles were easily overcome, but one that was difficult was migrating the data itself. This resulted in a one-time need for existing users to manually back up their data before it being accessible. You should be prompted to do so as soon as you choose an authentication option (link an email or remain a guest). Once done, you never have to it again. If you aren't prompted, head over to the Settings tab and scroll down to "Backup Lumy data". - Regarding _what_ data is synced: ONLY Lumy data is ever synced across devices. This means your spend trackers, category views, frugal months and transaction templates are synced, while all of your financial data fetched via YNAB remains on YNAB-servers _only_. This is both done to reduce redundancy (i.e. having copies of YNAB data and no single-source-of-truth), but also for your peace of mind. Changed: - A bit of UI freshening, as it's hard to do a major rewrite without sprucing some things up along the way.

Updates the calculation for spent amount in the Targets Health report such that categories with durations longer than the currently selected date range will show the average spent for the entire duration of the target, not the date range. This is helpful in cases where you're viewing a shorter date range than the target duration and within that date range you paid the full amount of that target. Previously, that would've skewed your target health to look unhealthy--now, (assuming you haven't actually overspent your target), the target will correctly be healthy. Categories with monthly targets or targets less than the currently selected date range will continue to show average monthly spending across the entire date range.

- Fixes an issue where the Target Health Report was not updating when changing budgets. - The Choose Period bottom sheet now closes after a period is selected. This better conforms to how other bottom sheets behave in the app.

New: - Adds the ability to quickly see over-spending for categories and category groups in the Budget Burndown. Previously, over-spending was not shown and a $0 remaining balance was shown instead. Fixes: - Ensures that changes to category group names are reflected immediately. This was previously not happening due to a YNAB API limitation, but we added a workaround to ensure a better user experience. - Ensures the ordering of category groups and their categories matches what you see in YNAB. Previously, ordering in Lumy only matched that of YNAB until you changed the order in YNAB. This is because the YNAB API does not communicate ordering changes in delta requests, which Lumy makes use of. Now, categories are pulled fresh and so the ordering can be respected. - Fixes an issue where transactions created via templates were always inflows, even if they were configured as outflows.

Introduces transaction templates, which will roll out slowly. Templates are a new (in beta!) premium feature that allow you to configure certain properties of common transactions and then tap a button to instantly create that transaction or fill out the remaining properties and then create the transaction. Please note that this is the first feature that _writes_ to your budget, and as such, will require you to provide write access before creating any transactions. Note about the beta: Right now, for ease, templates are written to your settings. Logging out will delete them. Additionally, they may be deleted if breaking changes are introduced. We will do our best to avoid that though! Some common use cases: - You purchase the same thing at a vending machine at work every so often: You could create a "Candy bar" template that has the payee "Vending Machine", an amount of $1.99, a category of "Snacks", and an account "My Checking". Maybe even throw in a memo of "My favorite mid-day treat". If you set up the template to "fire immediately", you can simply tap the template from your Budget Tab to instantly create that transaction whenever you want. - You tend to split a meal with friends at lunch:_You could create a template that has a split transaction configured, and only enter the amounts once you know them, categorizing your amount as "Dining Out" but the remainder as "Money I'm Owed". There are a lot of other use cases I'm sure, and maybe ones that we don't yet support. We'd love your feedback on what we can add/change about this feature.

Allows for quicker modification of spend tracker names by pre-populating the name field with the existing name during modification. Previously the existing name was shown as a "hint" that could not be modified.

Allows for quicker modification of spend tracker names by pre-populating the name field with the existing name during modification. Previously the existing name was shown as a "hint" that could not be modified.

By popular request (mostly in Discord, which you should join to take part in these conversations!), all types of transactions are now shown on the Payees tab of the Recurring Transactions screen. Previously, this screen aimed to be more of a "subscriptions" tracker, but since Lumy can't really know which of your transactions are "subscriptions", this led to a confusing experience where some transactions (such as transfers or inflows) were not shown. Now, everything is shown. Let us know if you dislike this change and we can consider making this setting configurable!

By popular request (mostly in Discord, which you should join to take part in these conversations!), all types of transactions are now shown on the Payees tab of the Recurring Transactions screen. Previously, this screen aimed to be more of a "subscriptions" tracker, but since Lumy can't really know which of your transactions are "subscriptions", this led to a confusing experience where some transactions (such as transfers or inflows) were not shown. Now, everything is shown. Let us know if you dislike this change and we can consider making this setting configurable!

Additions: - Design updates across the application to simplify the design system and make it simpler to introduce new UI - Added the ability to sort the Recurring Transaction (by Payee) report alphabetically and by amount in both ascending and descending fashion. - Report periods are now "trailing", meaning if you select, for example, the Latest 3 Months Period in December, you will initially see reporting for October, November, and December. However, on Jan 1, you will start seeing reporting for November, December, and January without needing to re-select Latest 3 Months like you would've had to do prior to this change. This was one of the primary changes as a result of [this ticket](https://lumyforynab.canny.io/features-and-bugs/p/timeframe-chooser-improvements). - The Frugal Month Section on the Budget Tab now highlights the Left to Spend amount instead of the status. The status can be seen by tapping the Frugal Month tile. Additionally, when a Frugal Month is active, it shows above the Spent this Month section. Fixes: - Fixed an issue with the Advanced Spend Tracker Query Builder for Advanced AST users where having enough conditions would make it impossible to add more. - Fixes the Send Feedback form so you can actually send feedback via the app now...We were wondering why it'd gotten so quiet! Removals: - I have decided to remove the (barely in beta) Goals feature. It may be revisited at a later time, but the amount of work it would take to maintain the feature as initially scoped would be way too high for a one-man team. For now, I'd like to focus most of my efforts on functionality I feel is more at the heart of what Lumy aims to do, such as more advanced reporting functionality. - Additionally, the "Highlights Section" has been removed from the Budget Tab for a couple reasons. The Left to Spend metric was redundant with the Burndown section title and now that the Frugal Month section shows the current Left to Spend amount, it was no longer needed. The Days of Buffer metric was confusing more folks than it was helping as it didn't align with the DOB metric shown on the Reports tab due to them using potentially different look-back periods (for reasons explained in Discord but not worth rehashing here). If you want your DOB number, check out the report on the Reports tab. For the most part, this number shouldn't change often or have huge swings, so having it front and center on app-launch seems a bit unnecessary. Lastly, the Overspent and Over-budgeted metrics were removed as well due to the fact that there is nothing you can do within Lumy (at this point) to take action on those, so they weren't really helpful.

Additions: - Design updates across the application to simplify the design system and make it simpler to introduce new UI - Added the ability to sort the Recurring Transaction (by Payee) report alphabetically and by amount in both ascending and descending fashion. - Report periods are now "trailing", meaning if you select, for example, the Latest 3 Months Period in December, you will initially see reporting for October, November, and December. However, on Jan 1, you will start seeing reporting for November, December, and January without needing to re-select Latest 3 Months like you would've had to do prior to this change. This was one of the primary changes as a result of [this ticket](https://lumyforynab.canny.io/features-and-bugs/p/timeframe-chooser-improvements). - The Frugal Month Section on the Budget Tab now highlights the Left to Spend amount instead of the status. The status can be seen by tapping the Frugal Month tile. Additionally, when a Frugal Month is active, it shows above the Spent this Month section. Fixes: - Fixed an issue with the Advanced Spend Tracker Query Builder for Advanced AST users where having enough conditions would make it impossible to add more. Removals: - I have decided to remove the (barely in beta) Goals feature. It may be revisited at a later time, but the amount of work it would take to maintain the feature as initially scoped would be way too high for a one-man team. For now, I'd like to focus most of my efforts on functionality I feel is more at the heart of what Lumy aims to do, such as more advanced reporting functionality. - Additionally, the "Highlights Section" has been removed from the Budget Tab for a couple reasons. The Left to Spend metric was redundant with the Burndown section title and now that the Frugal Month section shows the current Left to Spend amount, it was no longer needed. The Days of Buffer metric was confusing more folks than it was helping as it didn't align with the DOB metric shown on the Reports tab due to them using potentially different look-back periods (for reasons explained in Discord but not worth rehashing here). If you want your DOB number, check out the report on the Reports tab. For the most part, this number shouldn't change often or have huge swings, so having it front and center on app-launch seems a bit unnecessary. Lastly, the Overspent and Over-budgeted metrics were removed as well due to the fact that there is nothing you can do within Lumy (at this point) to take action on those, so they weren't really helpful.

- Fixes a bug that caused Starting Balance transactions to be included as income when they shouldn't be - Allows transactions without a payee to be included as income (this matches native YNAB). Previously, they were filtered out and not shown which could've impacted figures for folks who don't assign a Payee to their income transactions.

Frugal Months: Past Frugal Months have been removed from the Reports Tab and are now viewable by going to Settings; they're under the Data section. Recurring Transactions (New feature): Note: This feature is rolling out slowly. A Recurring Transactions report has been added to the General section of the Reports Tab. Inside, you'll find two ways to view your recurring transactions: - In the Payees Tab, you'll see your recurring transactions listed by payee. This is an easy way to view all of your recurring transactions and their frequency. At this time, they're ordered from highest total amount to lowest, but let us know if you would like different sorting capabilities. We've also added a toggle to show all amounts as annual amounts which can sometimes be enlightening and allow you to better ask the question, "Is this worth it?". - In the Timeline Tab, you'll see your recurring transactions laid out by when they will next occur. The timeline goes for a full year, showing each instance of all your recurring transactions. We've left this basic for now, but let us know what else you'd like to see on the timeline! Note: Right now, the categories selected on the Reports Tab influence the transactions shown on this screen. Let us know if you think we should add the ability to filter categories and/or accounts specifically for this report like we do with Income v Expense. Other: A bit of design work was done to offer more real estate to visuals like charts.

- The Spend by Category Pie chart now shows percentages of total spend for both category groups and categories for the selected timeframe and Category View. It also preserves the ability to "dive in" by tapping a category group. When doing that, the percentage shown for each category is the percentage of spend of the selected category group. This is similar (maybe even identical) to how it works natively in YNAB's Reflect report. This was requested in this ticket: https://lumyforynab.canny.io/features-and-bugs/p/show-percentages-in-spend-by-category-group. - Similar to the above, the Spend by Payee Pie chart now shows percentages of total spend for the selected timeframe and Category View. - Fixes a bug where some charts weren't getting the memo about an updated Category View and were sticking with the old one.

Frugal Months: Frugal Months got a bit of love with this update, check out the deets below: - When creating a Frugal Month, you now select the categories and accounts first. Then, when setting a target limit, the selected categories and accounts are used to suggest a limit that is 90% of average spending. - Now, when creating a Frugal Month for the *current* month, you will no longer be able to accidentally set a limit that is less than you've already spent for the month. - The projected spending shown on the Frugal Month chart is more granular; rather than an average daily spend being applied to all days in the month, each day has its _own_ average spending. This means that if you generally have a lot of spending on certain days, the projection should reflect that, rather than the line simply being linear. - Because of the above, the status shown for a Frugal Month is more accurate. The status now correctly utilizes the _expected_ spending (based on the projection) to determine whether you're on track or not. As always, please reach out in Discord, on Reddit, or via email if you see anything funky with these changes! General: - Fixes a few minor bugs you (probably) haven't noticed!

- Fixes a bug in the Targets Health Report that sometimes caused incorrect spent amounts to be shown, leading to incorrect analysis of a target's health. - Fixes overflow of long category names in transaction rows - Ensures users are logged out if they revoke their token from YNAB settings.

General - Revamps dialogs across the app to better fit the platform. Goals Beta - Adds ability to delete and rename goals (still only debt goals are supported). - Changes the behavior for determining a debt goal's original balance. Now, when a goal is created, the remaining balance is used. You can change the original balance (for instance, if you want it to reflect your mortgage's original balance) by tapping the menu on the Goal Details screen and tapping Edit Balances. Note that this is a breaking change and since goals are still in beta, you will need to delete and recreate existing goals. - Fixes other minor goals bugs!

General: - Revamps dialogs across the app to better fit the platform. Goals Beta: - Adds ability to delete and rename goals (still only debt goals are supported). - Changes the behavior for determining a debt goal's original balance. Now, when a goal is created, the remaining balance is used. You can change the original balance (for instance, if you want it to reflect your mortgage's original balance) by tapping the menu on the Goal Details screen and tapping Edit Balances. Note that this is a breaking change and since goals are still in beta, you will need to delete and recreate existing goals. - Fixes other minor goals bugs!

- Debt Goals have begun rolling out to beta testers. Want to test them out and give feedback? Feel free to join the Discord server, hop into #feat-goals, and let us know! You can join the server from Settings by tapping Join the Community. - Fixes a visual bug related to the pages in the Spend by Category Pie chart for some users. - Fixes a bug that caused inputting currency amounts during frugal month creation to misbehave for currency formats that did not include a decimal separator.

- Changes the percent remaining calculation for category groups in the Budget Burndown to more accurately reflect the amount remaining in the group (shown via the progress bar). Previously, the percent was an average of all the remaining percents for categories in that group. Now it is the percent remaining of the initial balance, which is more accurate. - Fixes a bug that could have prevented some users with Firefox set to their default browser from being able to log in. - Fixes a bug in category selection when creating Category Views or Frugal Months that caused it to be impossible to choose certain categories in a specific order. - Fixes a bug that caused the app to fail to launch for users with completed Frugal Months.

- Allows spend trackers to consider tracking accounts. Note that some conditions are not compatible with tracking accounts, such as "Is Income" and "Is Expense", or "Category Is" because tracking accounts transactions do not have categories. We've added "Is Outflow" and "Is Inflow" to support filtering tracking account transactions. - Fixes a pesky out of memory bug that could have happened when modifying a category view. - Fixes a bug that caused it to appear as if a premium subscription purchase did not work (this could be worked around by restarting the app prior to this fix). Now, premium purchases are immediately reflected in the app. - Some more UI polishing as we prepare for the Goals (Beta) feature to be released soon. Stay tuned! - Minor performance improvement