Local work with explicit synchronization
Supported entries are stored locally first. Once connected, the app sends named, validated changes to the server. Permanent conflicts stay visible.
Offline & data ownership
Poor reception is part of boating. A digital record must not become useless while you are standing in front of the engine.
Supported entries are stored locally first. Once connected, the app sends named, validated changes to the server. Permanent conflicts stay visible.
The local database is a working projection and queue, not a second rule engine. Permissions, membership and product rules are checked centrally.
Reading, search, original download, export, transfer and deletion remain possible. Deactivated modules are hidden; records are not destroyed.
Start free or try Skipper for 30 days without payment details.