github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-11 01:18:59 -05:00
Code Issues 1.6k Packages Projects Releases 57 Wiki Activity

[GH-ISSUE #5938] [Feature] Allow creating Schedules on mobile #16784

New Issue
Closed
opened 2026-04-14 19:47:22 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-14 19:47:22 -05:00
Owner
Copy Link

Originally created by @rtbick on GitHub (Oct 16, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5938

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

I would love to work on it if I knew how to develop mobile UI.

Pitch: what problem are you trying to solve?

In Actual, it is recommended that future transactions should be created as Schedules. Adding a transaction dated in the future is often undesirable because it is then included in calculating the account balance.

The mobile UI does not allow users to create Schedules. The current alternative on mobile is to add a transaction dated in the future, then go back and fix it on a PC later. This additional workflow overhead negates the value provided by the mobile UI.

Reducing user friction around managing transactions is important in a budgeting app, because it increases the likelihood the user will keep up with their budget. Therefore, it's important that key features such as schedules should be available on mobile devices.

Adding the entire Schedules page to the mobile UI is outside the scope of this feature request. I'm only requesting the ability to create schedules, so that future-dated transactions can be added correctly via mobile.

Describe your ideal solution to this problem

The Schedule creation could be integrated with the Add Transaction screen:

  1. Tap "+ Transaction" and enter the payee, category etc. as usual.
  2. Add a toggle that says "Schedule".
  3. If the toggle is On, the form would update to include the options unique to Schedules (e.g. the Repeat options).
  4. Submitting this form would then create a Schedule rather than a Transaction.

Alternatively, a separate "Create schedule" button could be added to the mobile toolbar instead of integrating it with "+ Transaction". This would directly show the Create Schedule menus instead of using a toggle. However, I feel that it is more intuitive to create a Schedule via the Transactions workflow, since a schedule is essentially an automated transaction.

Some Schedule options could be omitted to keep the mobile UI streamlined. The most important options are "Repeats" and its submenu options. Other features, such as the table listing matching transactions, could be limited to PC only.

Teaching and learning

There currently doesn't appear to be any documentation dedicated to the mobile UI in general. The mobile Schedules UI should be intuitive and supported by the current Schedules documentation.

Originally created by @rtbick on GitHub (Oct 16, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5938 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? I would love to work on it if I knew how to develop mobile UI. ### Pitch: what problem are you trying to solve? In Actual, it is recommended that future transactions should be created as Schedules. Adding a transaction dated in the future is often undesirable because it is then included in calculating the account balance. The mobile UI does not allow users to create Schedules. The current alternative on mobile is to add a transaction dated in the future, then go back and fix it on a PC later. This additional workflow overhead negates the value provided by the mobile UI. Reducing user friction around managing transactions is important in a budgeting app, because it increases the likelihood the user will keep up with their budget. Therefore, it's important that key features such as schedules should be available on mobile devices. **Adding the entire Schedules page to the mobile UI is outside the scope of this feature request.** I'm only requesting the ability to create schedules, so that future-dated transactions can be added correctly via mobile. ### Describe your ideal solution to this problem The Schedule creation could be integrated with the Add Transaction screen: 1. Tap "+ Transaction" and enter the payee, category etc. as usual. 2. Add a toggle that says "Schedule". 3. If the toggle is On, the form would update to include the options unique to Schedules (e.g. the Repeat options). 4. Submitting this form would then create a Schedule rather than a Transaction. Alternatively, a separate "Create schedule" button could be added to the mobile toolbar instead of integrating it with "+ Transaction". This would directly show the Create Schedule menus instead of using a toggle. However, I feel that it is more intuitive to create a Schedule via the Transactions workflow, since a schedule is essentially an automated transaction. Some Schedule options could be omitted to keep the mobile UI streamlined. The most important options are "Repeats" and its submenu options. Other features, such as the table listing matching transactions, could be limited to PC only. ### Teaching and learning There currently doesn't appear to be any documentation dedicated to the mobile UI in general. The mobile Schedules UI should be intuitive and supported by the current Schedules documentation.
GiteaMirror added the feature label 2026-04-14 19:47:22 -05:00
GiteaMirror commented 2026-04-14 19:47:24 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 16, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

<!-- gh-comment-id:3411891919 --> @github-actions[bot] commented on GitHub (Oct 16, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-04-14 19:47:25 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Apr 9, 2026):

This was added a few months ago.

<!-- gh-comment-id:4216796670 --> @youngcw commented on GitHub (Apr 9, 2026): This was added a few months ago.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#16784
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?