Budget Shortcuts
complete
Brandon Trautmann
Budget shortcuts would offer the ability to perform actions on your budget with the tap of a button. The primary use case would be in creating transactions. Consider the following examples:
- You just started a new home project, and want to track all transactions in the Home Improvement Category but you want to be able to run reports on this specific project. Create a Shortcut that, when tapped, prompts you for the amount and memo, and upon entering, automatically appends #kitchenrenovationto the end of the memo, without you needing to remember or input it.
- You pay your babysitter $50 every time they watch your children, but it's not on a set cadence (every 2 weeks, etc.). At the tap of a button, a $50 transaction is created for the correct payee, with the correct memo (e.g "Babysitting on 5/27/24").
- You often stop to pick up coffee on your way to work. The coffee is a small drop of joy in your daily routine, but adding the transaction isn't. Instead, tap the Coffee shortcut and automatically create a transaction with the correct information. Optionally, if you switched up your order that day, you can modify the amount before it's saved.
Notes:
- Creating a shortcut would allow you to enter a preset payee, account, amount, memo, etc.
- If all fields cannot be filled out (e.g the amount is different each time), you would set that field to "prompt me" and it would prompt you to fill it out before saving; all other fields would be preset
- You could set it to always prompt you, even if all fields are preset, in the event you like to check before you send.
- This feature would require writeaccess (and would be the first feature requiring this).
Brandon Trautmann
complete
Releasing in 1.23.x for beta
Brandon Trautmann
in progress
Brandon Trautmann
R
Ricori
I like convenience it provides as I start entering all transactions manually before syncing it with ynab. Would this feature be optional though? Can we opt in and opt out of the write access voluntarily in iOS app?
Brandon Trautmann
Ricori: I haven't explored how the transition from read -> write would work, but I suspect that it would require a new authentication token to be issued. It would probably look something like going through the YNAB login experience a second time. After that, though, I don't think it would be seamless to flip back and forth (i.e revoke write access until you want to use a shortcut). The feature would 100% be optional, we would still default to read access on initial login!