See your schedule and assignments
Read your upcoming trips and assignments, and understand how the app keeps them current offline.
Your schedule is the list of trips you are assigned to, grouped by trip, with your role on each. This page covers what you see and how it stays current — including with no signal.
Steps
- Open the Schedule tab. It lists every trip carrying one of your assignments, most-urgent first, each row showing the trip id and your role badge (PIC / SIC / FA) for that trip.
- Check the Up Next card. At the top of the list, if you have a future assignment with a report time, the app shows an UP NEXT card with the trip id, your report time, and a live countdown. The countdown turns amber inside the final hour before report.
- Tap a trip to open it. Both the Up Next card and any row in the list link straight to that trip's detail view — there is no typing an id.
- Pull to refresh. Pulling down re-runs a sync pass immediately instead of waiting for the next automatic one.
How your schedule stays current — including offline
The app does not re-download your whole schedule every time. It keeps a cursor (a timestamp) of the last assignment change it received, and asks the server for only what changed since then:
The server returns just the assignments that changed after that cursor, plus a new cursor to save for next time — a delta sync. Every assignment the app receives is written into a local SQLite database on your device, so the schedule you see is read from that local copy, not fetched live on every screen open. That is what "offline-first" means here in practice: the Schedule tab renders instantly from what's already on the device, and a sync pass in the background quietly brings it up to date when you have a connection.
The same sync pass also prefetches the legs (and a route-map image) of your soonest few upcoming trips, so opening a trip you have not looked at yet still works with no signal — not just the schedule list itself.
Actions you take in the app — acknowledging an assignment, checking in for duty, logging a flight — work the same way in reverse: they are written to a local write-queue first, then sent to the server when you have a connection, with automatic retry if a send fails. See acknowledge or decline an assignment for how that looks for one specific action.