TACTIFLAGThe offline model
TactiFlag prepares a team pack while the device is online. That pack contains the coaching information needed for core sideline workflows. When the connection disappears, supported work reads from and writes to device storage. After reconnection, queued changes upload and fresh team changes download.
What works and what requires internet
The boundary is intentionally conservative so the app never pretends a cloud action succeeded while offline.
| Action | Offline behavior |
|---|---|
| View prepared playbook, roster, drills, practices, install status, recent games | Available for prepared teams |
| Edit prepared plays | Saved on this device and queued |
| Operate Game Day and record events | Saved on this device and queued |
| Use the live whiteboard | Saved locally for recovery |
| Sign in for the first time or prepare a new team | Internet required |
| Invite staff, manage billing, share externally | Internet required |
| Receive another device’s changes | Requires synchronization |
Read the sync status
The global status reports whether the device is preparing, offline, syncing, synchronized, blocked, or in conflict.
- Offline: changes remain safely queued on this device
- Syncing: uploads and team updates are being processed
- Needs attention: access or another recoverable problem blocked an item
- Conflict: the same record changed incompatibly and needs a decision
What happens after reconnecting
TactiFlag requests synchronization when the connection returns, the app resumes, or a new supported offline change is created. You can also use Sync now from Offline readiness.