Offline Mode & Installation

Legitski works even without internet. Install it as a native-feeling app on any device, continue working offline, and let the sync engine handle the rest when you reconnect.

Installing as an App

Legitski is a Progressive Web App (PWA). You can install it on your device for a native app experience with an icon on your home screen or dock.

Chrome / Edge
  1. Open Legitski in Chrome or Edge
  2. Click the install icon in the address bar
  3. Confirm by clicking "Install"
Safari (iOS)
  1. Open Legitski in Safari
  2. Tap the Share button (square with arrow)
  3. Select "Add to Home Screen"
Firefox
  1. Open Legitski in Firefox
  2. PWA install may not be available
  3. Use Chrome or Edge for best support

Auto-prompt

On supported browsers, Legitski automatically shows an install prompt after your second visit. You can dismiss it and install later from the browser menu.

Connection Status

A small indicator in the navigation bar shows your current connection state. The indicator changes color and label based on network activity.

OnlineConnected and synced
OfflineNo internet connection
SyncingUploading queued changes
PendingChanges waiting to sync

Automatic detection

Legitski monitors your network status and transitions between states automatically. No action is required on your part.

What Works Offline

Most core features work without an internet connection. Changes are queued locally and synced when you reconnect.

Offline Feature MatrixLive Preview
FeatureOffline
View inventory
Create items
Edit items
Delete items
Process sales (cashier)
View activity log
View reports (cached)
Invite team members
Change subscription
Real-time updates

Data freshness

While offline, you are working with locally cached data. If another team member makes changes at the same time, you will see their updates only after reconnecting and syncing.

How Sync Works

When you go offline and make changes, the sync engine handles everything automatically. Here is the four-step process.

1
Queue locallyChanges are saved to local storage and added to a sync queue with timestamps.
2
Detect connectionThe app monitors network status and triggers sync when connectivity is restored.
3
Upload in orderQueued operations are sent to the server in chronological order, one at a time.
4
Resolve conflictsIf a conflict is detected, the operation is flagged for manual resolution.

Retry on failure

If a sync attempt fails (e.g., the connection drops again), the operation stays in the queue and retries automatically on the next connection.

Pending Operations Panel

When you have unsent changes, a panel shows the list of pending operations with their status. You can monitor sync progress from here.

Operations QueueLive Preview
Pending Operations3
ThinkPad X1 Carbon Gen 12Updated quantity: 14 -> 12
pending2 min ago
New Wireless KeyboardCreated with 5 fieldsNetwork timeout
failed8 min ago
USB-C Hub 7-in-1Updated price: $44.99 -> $39.99
conflict12 min ago

Failed operations

Operations marked as "failed" will be retried automatically. If they continue to fail, you can choose to discard them or manually resolve the issue.

Resolving Sync Conflicts

A conflict occurs when the same item was modified both offline and by another user online. The conflict modal shows both versions and lets you choose which value to keep.

Conflict ResolutionLive Preview
Sync Conflicts
Price
Your change$39.99
Server value$42.99
Quantity
Your change8
Server value6

Field-level resolution

You can choose to keep your changes or accept the server values. The decision applies to all conflicting fields for that item at once.

Tips for Working Offline

Follow these best practices to get the most out of offline mode and minimize sync conflicts.

1
Sync before going offlineMake sure all pending operations are synced before intentionally going offline. This ensures you have the latest data.
2
Coordinate with your teamIf multiple team members work offline simultaneously, coordinate which items each person edits to minimize conflicts.
3
Reconnect regularlyThe longer you stay offline, the more likely conflicts become. Reconnect when possible to keep your data fresh.
4
Check pending before closingBefore closing the app, check the pending operations panel. Unsent changes are preserved but syncing requires the app to be open.
5
Keep the app installedThe installed PWA caches assets locally, making offline startup faster and more reliable than using a browser tab.

Queue limits

The offline queue can hold up to 500 operations. If you reach this limit while offline, you will need to reconnect and sync before making additional changes.