Background app limitations

WatchKeeper is designed to keep your watch schedule reliable, but it still operates within the background limits imposed by iPhone. That means the app can save your schedule, recompute the correct state, and deliver notifications through the system, but it may not behave like an always-open navigation display running continuously in the foreground.

On iPhone, apps do not have unlimited freedom to run in the background. If WatchKeeper is not open on screen, the system may pause most live app activity to preserve battery and manage device performance. This is normal iPhone behavior. It does not usually prevent scheduled notifications from firing, but it can affect anything that depends on the app actively running in real time while closed.

For that reason, WatchKeeper is built around local persistence and schedule recovery rather than constant background processing. The app saves the underlying schedule and any changes, then rebuilds the correct active state when needed. This makes it more dependable than relying on a continuously running background session, especially on long trips where the app may be opened and closed many times.

If something does not look current when reopening the app, that does not always mean the schedule was lost. In many cases, the app simply needs to recompute the active watch from saved data and current time. The important thing is that the schedule model remains intact and recoverable.

What Background Limits Can Affect

• Real-time screen updates while the app is closed
• Immediate in-app state changes before reopening
• Some behavior that depends on the app staying continuously active

What Should Still Work

• Saved crew and watch schedule data
• Recovery of the current watch state after reopening
• Scheduled notifications, if permissions and device settings allow them

Best Practices

• Do not rely on the app staying open in the background indefinitely.
• Make sure notification permissions are enabled.
• Reopen the app to confirm the current watch state after long idle periods if needed.
• Test alarm and recovery behavior before departure.

Background limitations are a normal part of iPhone behavior, not a sign that the schedule is broken. WatchKeeper is designed to handle that by saving the important data and rebuilding the right answer when the crew needs it.