mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 22:54:03 -05:00
[GH-ISSUE #6806] [Bug]: PWA Opening Performance (Android) / Keep resident in memory #117249
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#117249
Reference in New Issue
Block a user
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?
Originally created by @ppittle on GitHub (Jan 28, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6806
Verified issue does not already exist?
What happened?
Opening the Actual PWA on Android (GrapheneOS / Valandium / Firefox / Brave / IronFox) takes 45-90 seconds after a reboot.
Reopening the PWA app can be instant.
But after some time the PWA again takes 45-90 seconds to open. Is this expected behavior? Is there a way to keep Actual page loaded or cached?
For reference, the YNAB4 app (with same data set) loads in ~4-6 seconds.
How can we reproduce the issue?
Open the PWA app on Android.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Other
Operating System
Mobile Device
@youngcw commented on GitHub (Jan 28, 2026):
The difference is that with YNAB the app isn't generating data its just requesting it, Actual is calculating all the budget data locally. What you are seeing is the budget cache being regenerated. It gets regenerated occasionally to make sure all the numbers are correct.
@youngcw commented on GitHub (Jan 28, 2026):
So in that sense its not a bug. Ill close this off.
@nyreed commented on GitHub (Jun 8, 2026):
Seconded on the experience frequently needing 45-90 seconds to load the PWA on Android. Like anytime the app goes out of memory.
If this is due to intended behaviour does there need to be some thought towards optimisation for mobile devices? As is it's a pretty poor user experience.