Opening offline is not enough
The useful test is whether a supported new operation is durably stored, marked honestly and later delivered without disappearing. An app that only displays an old list is not solving the same problem as one that accepts work.
Salelog distinguishes local persistence from server confirmation. A pending label may appear less seamless than permanent success, but it tells the user where the data actually is.
A practical test for the team
- Sign in and load the organisation while connected.
- Note the balance of a test product.
- Enable aeroplane mode.
- Complete the supported operation.
- Confirm that it is stored and shown as pending.
- Restore the connection and allow synchronisation.
- Check the result from web or another device.
Also test two devices changing the same record. Normal concurrency should become a visible conflict or deterministic outcome, not a silent overwrite.
What remains online-only?
Authentication, subscriptions, support destinations, configuration and server-only features can need connectivity. The web client does as well. Evaluate offline support per task rather than turning it into a promise about the whole application.
One operating rule prevents many duplicates
When a handset shows pending work, keep it available until delivery completes. Do not clear its data, sign out or repeat the same sale elsewhere simply because a colleague cannot see it yet.