Local data
Catalogue, services, profile and history are available offline — from what is already loaded.
In a lift, a car park or a basement the app does not turn into a white screen: what is already loaded opens, and what was sent is not lost.
Nobody has to think about signal. The catalogue and their bookings open where there is no internet; a request sent in a lift goes through by itself once the connection is back. No «try again» and no lost form.
Offline is not a mode to switch on: the app simply keeps working.
Catalogue, services, profile and history are available offline — from what is already loaded.
An order, a booking or a message goes to the server once the connection is back.
The entry code and saved documents open without internet.
It is visible what has already gone and what is waiting for a connection — not «sent» after the fact.
If things changed while offline, the app says so instead of silently overwriting.
What changed is downloaded, not the whole catalogue again.
The rule is simple: reading from a local copy, writing through a queue. No step asks anything of the person.
What must open offline: catalogue, bookings, pass, documents.
Which actions wait for a connection and what the person sees while they wait.
What to do if the slot was taken or the price changed while there was no signal.
Tell us about your customer scenario — we'll suggest the right modules and the scope of the first release.
Discuss an appIt opens and shows what has been loaded — yes. New data of course only arrives with a connection, but nobody hits an empty screen.
It queues up and goes through when the connection returns. The person sees that it is not confirmed yet, rather than a false «accepted».
The app says so and offers another time. It will not quietly overwrite somebody else's booking.
Yes, the code is on the device. That is exactly the case offline exists for.