Using Lumicura offline
What works without a connection (reading what you've already loaded), what doesn't (sending anything), and how the app tells you.
School gyms, parking-lot pickup lines, and field-trip buses are not famous for their cell signal. Lumicura is built to stay useful when the connection drops — within limits worth knowing.
What works offline
Reading. Content you’ve already loaded stays readable: recent announcements, the messages you’ve seen in your channels, your service-hours tally as of the last time it loaded. Open the app with no signal and your recent world is still there.
What doesn’t
Anything that changes something. Sending a message, signing up for a shift, scanning a check-in code — these need a live connection. Lumicura deliberately doesn’t queue actions to send later: nothing worse than a message you thought went out at noon arriving at 9pm out of context. If it didn’t send, the app says so, and you send it again when you’re back online.
How you’ll know
A banner appears when the app is offline, and disappears when the connection returns. While the banner is up, treat the app as read-only. Anything you’re reading may also be slightly stale — it’s a snapshot from the last successful load.
After you reconnect
Nothing to do — the app refreshes itself as soon as it’s back online. If something looks out of date a moment after reconnecting, give it a beat or pull to refresh.
Two practical tips
- Volunteering somewhere with weak signal? If your shift uses QR check-in, step toward a window or doorway when scanning — the check-in needs a connection to record. If it truly won’t go through, tell the shift organizer so they can credit you manually.
- Sent a message right as the signal dropped? Check whether it actually posted before retyping it — if it isn’t showing in the channel, it didn’t send.