Offline-first is a data promise, not a marketing label
The important question is not whether an app opens without internet. It is whether a supported operation can be saved durably, clearly marked as local and synchronized without silently disappearing when connectivity returns.
Salelog distinguishes local persistence from server confirmation. That distinction can look less magical than a permanent “success” message, but it tells the user the truth about where the data is.
A realistic offline test
- Sign in and load the business while connected.
- Choose a test product and note its current quantity.
- Enable airplane mode.
- Complete the supported sale or stock operation.
- Confirm that the app shows a pending state.
- Restore the connection and wait for synchronization.
- Check the result from another device or the web app.
Also test two devices changing the same business data. A professional app should surface a conflict or deterministic result rather than quietly overwriting information.
What may still need the network?
Initial sign-in, subscription verification, support links, remote configuration and server-only features can require connectivity. The web browser client does as well. This is why “works offline” should be evaluated per workflow instead of applied to the entire product.
A simple operating rule for teams
If a phone shows pending work, keep it available until synchronization finishes. Do not immediately sign out, clear storage or repeat the same transaction on another device. When the connection returns, resolve any conflict and confirm the final quantity before moving on.