Why Your iPhone Widget Shows Old Data: Refresh Budgets and Timelines
Short answer: An iPhone widget is not a tiny running app. It is a set of pre-built snapshots that iOS shows on a schedule, and the system decides how often your widget may ask for new ones. If your owner or staff widget shows old figures, the cause is usually a timeline that was built for the wrong moments, a refresh request that was never sent from the app, or data that the widget cannot reach. Each of these has a specific fix, and none of them involves making the widget "run harder".
How a widget actually gets its content
Apple's WidgetKit framework asks your widget for a timeline: a list of entries, each with a date and the content to show from that date. iOS then displays the right entry at the right time without waking your code. When the last entry is used up, or when the timeline's reload policy says so, the system may ask for a fresh timeline.
The word is "may". Apple documents that the system gives each widget a limited refresh budget, shaped by how often people look at it, how much battery is left and what else is happening. A widget on the first Home Screen page that the owner glances at forty times a day is treated more generously than one buried in a Today View stack. Your developer cannot buy more budget, but they can spend it sensibly.
That explains the most common complaint. A bakery owner installs a widget showing "orders to bake today". It was correct at 6 am, and at 10 am it still shows the early count. Nothing is broken. The timeline was probably a single entry with no plan for the rest of the morning.
Symptom, cause and fix
Use this table when you brief your developer or check a build.
| Symptom | Likely cause | Fix to request |
|---|---|---|
| Figures are hours old, then jump | One long timeline entry with a late reload date | Shorter timeline entries around the times that matter, such as opening and cut-off |
| Widget never changes after an order arrives | The app never tells WidgetKit that data changed | Call a timeline reload from the app whenever new data is saved |
| Widget shows "No data" after a reboot | Data stored where the widget cannot read it | Share a small data store between app and widget using an App Group |
| Widget updates only when the app is opened | Reload is triggered only on app launch | Also reload after background tasks or push-driven syncs |
| Widget works on your phone, not a colleague's | Signed-out state not handled | Show a clear "Open the app to sign in" entry instead of a blank tile |
| Time-sensitive tile is wrong by a few minutes | Relying on frequent reloads for a countdown | Use date-based text that the system counts itself |
Design the timeline around the business, not the clock
The best fix is to decide which moments change what your staff do, then build entries for those. A plumber's "next job" widget does not need a refresh every minute. It needs one entry per scheduled job start time, because the content changes when the job changes, not when the clock ticks.
Ask your developer to write down, for each widget, three things:
- What the widget shows. One idea per size. A small widget might show only "Orders waiting: 7".
- What changes it. An event in the app, a server update, or simply the time.
- How wrong it is allowed to be. Five minutes late for a stock level is fine. Five minutes late for a collection time is not.
If the answer to the third question is "must be right to the minute", a widget may be the wrong tool. A live notification, or a Live Activity on the lock screen, is built for time-critical state. Widgets are better for glanceable summaries.
Getting fresh data from the app into the widget
There are three routes, and most business widgets use more than one.
Reload from the app
When your app saves new data, it can ask WidgetKit to reload one widget kind or all of them. This is the cheapest and most reliable route, because the app already knows something changed. The catch is that it only works when the app runs, so an order that arrives while the app is closed is not seen until the next route kicks in.
Fetch inside the widget
The widget can make its own network request while building a timeline. This suits data that anyone can read, such as a public opening-hours status. For private data it needs a stored sign-in token that the widget extension can read, which means a shared keychain group. Your developer should treat that token carefully, as widgets run in a separate process.
Push-driven reload
Apple has added ways for a server push to prompt a widget reload on newer iOS versions. Support depends on the iOS version your customers or staff run, so as of November 2026 check Apple's current WidgetKit documentation and set a minimum iOS version that makes sense for your devices.
Testing a widget honestly
Developers often test in the simulator, where refresh budgets behave generously. Insist on a real-device checklist:
- [ ] Install a release-style build on a physical phone, not a debug build
- [ ] Leave it untouched for a full working day and note what the widget shows at three set times
- [ ] Change data on the server, then watch how long the widget takes to follow
- [ ] Restart the phone and confirm the widget still shows real content
- [ ] Sign out and sign in, and check both states look intentional
- [ ] Try Low Power Mode, which can reduce background activity
Write the results into a short table: time, expected value, actual value. Without numbers, "it feels slow" turns into a long argument.
Mistakes that keep widgets stale
Showing everything. A medium widget with eight figures needs eight data points to be fresh. One headline figure is easier to keep correct.
Hiding the age. Add a small "Updated 10:42" label. Staff forgive a stale number they can see is stale far more readily than one that pretends to be live.
Treating the widget as a button panel. Newer iOS versions allow limited interactivity, but a widget that is expected to perform full workflows will frustrate people. Keep the heavy actions in the app and let the widget open the right screen.
Skipping the empty state. New staff will have a widget that has never loaded. Design that screen too.
FAQ
Can we force a widget to refresh every minute?
No. iOS controls the schedule and rations reloads. You can request reloads, and well-planned timelines make the content correct between them, but a guaranteed per-minute refresh is not offered.
Does an Android widget behave the same way?
Not exactly. Android widgets have their own update rules and limits, and the fixes differ. Brief each platform separately so the expectations are right.
Is a widget worth building at all for a small business app?
Often yes, if the widget answers one daily question, such as today's jobs or open tickets. If the answer needs live accuracy or deep interaction, spend the budget on notifications instead.
What should we ask the developer to show us?
A short test log from a real phone, with expected and actual values at fixed times, and the list of events that trigger a reload.
If your widget keeps showing yesterday's numbers, tell us what it should show and we will plan a timeline that fits.