I'm building ShiftLog, a free shift and profit tracker for gig workers and drivers. One decision shaped the whole app: it works offline-first, with no account and no cloud.
Why? Gig workers lose signal all the time — in parking garages, on highways, in rural areas. And on a low-end phone with a small data plan, every megabyte matters. If tracking a shift needs the internet, it won't get tracked.
So ShiftLog stores everything on the device itself: shifts, income, expenses. Open the app, log the shift, done — signal or no signal. There is no sign-up screen standing between a driver and their own numbers, because there is no server holding them.
The trade-off is honest: there is no cross-device sync. Your data lives on your phone, which is a feature for privacy and a limitation for convenience, and I would rather say that plainly than hide it.
The app is free on Google Play: https://play.google.com/store/apps/details?id=com.shiftlog.app
If you drive, deliver, or work shifts: does offline-first matter to you, or would you trade it for sync? I am building in public and real answers shape the next update.
Top comments (2)
The explicit no-sync trade-off is more trustworthy than a vague privacy claim. A useful next test would be an export-and-restore flow on a second device: it keeps the default offline while showing whether people can recover years of shift data without turning a cloud account into a requirement.
Thank you, Alex — that's a really fair point, and you put the trade-off exactly right. Keeping everything offline by default is the honest choice, but it does raise the question you flagged: what happens to years of shift data if the phone is lost or replaced. An export-and-restore flow that stays local (no cloud account required) is a genuinely useful next test for that, and I'll keep it in mind as the app grows. Thanks for reading closely and for the suggestion.