The mechanic asks when the brakes were last checked. You know it was "sometime last year". The receipt is in the glovebox, or a drawer, or gone.
That's the problem AutoLog started from. People with a car, a motorbike and a work truck, or a freelancer with one van, who keep the service history in their head and the fuel receipts in a pile. We wanted an app that answers three questions fast: what was done to this vehicle, what's due next, and what has it cost.
We also wanted it to run without a server. AutoLog has no backend, no account and no network code. Everything lives on the device in Hive CE, with Provider on top. That one constraint shaped most of the decisions below.
1. The odometer is a rule, not a text field
Service entries and fuel logs both carry an odometer reading. If users can type anything, you end up with a fill-up at 48,000 km sitting between two at 51,000 km, and every total built on it is quietly wrong.
So in AutoLog a reading has to fit between the logs around it. And when a new log is higher than the vehicle's current odometer, the vehicle's odometer moves up on its own. Nobody has to remember to update it.
// simplified
String? validateOdometer(int reading, DateTime date, List<LogEntry> logs) {
final before = logs.where((l) => l.date.isBefore(date));
final after = logs.where((l) => l.date.isAfter(date));
final floor = before.isEmpty ? 0 : before.map((l) => l.odometer).reduce(max);
final ceiling = after.isEmpty ? null : after.map((l) => l.odometer).reduce(min);
if (reading < floor) return 'Must be at least $floor km';
if (ceiling != null && reading > ceiling) return 'Must be at most $ceiling km';
return null;
}
// in VehicleProvider, after a log is saved
if (log.odometer > vehicle.odometer) {
vehicle.odometer = log.odometer;
await vehicle.save(); // Hive CE object
notifyListeners();
}
Odometer rules are one of the areas the unit tests cover, next to backups, number input, reminders and settings. They're the kind of rule that breaks without anyone noticing.
2. Reminders by date, scheduled on the phone
A service entry can carry an optional "next service" date. When it does, AutoLog schedules a local notification for 09:00 local time on that day, using flutter_local_notifications and timezone. No push service. No server.
We kept reminders date-based on purpose. A mileage-based reminder needs to know how far the vehicle has gone, and the app only learns that when someone logs something. A date is something the phone can act on by itself.
The harder part was keeping reminders honest over time:
- deleting a service entry cancels its reminder
- restoring a backup rebuilds every reminder from the restored data
- the in-app Notifications screen labels each item Overdue, Due today or "Due in N days"
// simplified
Future<void> rebuildReminders(Iterable<ServiceLog> services) async {
await notifications.cancelAll();
final now = tz.TZDateTime.now(tz.local);
for (final s in services) {
final due = s.nextServiceDate;
if (due == null) continue;
final at = tz.TZDateTime(tz.local, due.year, due.month, due.day, 9);
if (at.isBefore(now)) continue;
await scheduleReminder(id: s.notificationId, title: s.serviceName, at: at);
}
}
Rebuilding from the data, instead of patching reminders one by one, means a restore can't leave a ghost notification for a service that no longer exists.
3. One PDF per vehicle, in the user's language
Sooner or later the history has to leave the phone. A buyer wants to see it, or it goes into an expense folder. AutoLog exports a PDF report for any vehicle: its details, a service table, a fuel table and totals in the user's currency, built with the pdf package.
The app ships in 7 languages, Arabic among them, so the report had to handle right-to-left text. We bundle Noto fonts rather than trust whatever the device has, and flip the page direction for Arabic. Hindi reports use English labels.
// simplified
final doc = pw.Document();
doc.addPage(
pw.MultiPage(
theme: pw.ThemeData.withFont(base: notoRegular, bold: notoBold),
textDirection: isArabic ? pw.TextDirection.rtl : pw.TextDirection.ltr,
build: (context) => [
vehicleHeader(vehicle),
serviceTable(vehicle.services, currency),
fuelTable(vehicle.fuelLogs, currency),
totals(vehicle, currency),
],
),
);
The fuel and trip side follows the same idea of doing the arithmetic for the user. A fuel log takes litres and price per litre and works out the total. Trips are tagged Business or Personal, and the monthly list shows total, business and personal distance.
What it doesn't do
Some of these are choices, some are just not built. Either way, better to know up front.
- No sync. There's no network code, so data stays on the device it was entered on. Backups are JSON files shared through the system share sheet (Drive, iCloud, email, files). There's no direct cloud integration.
- Date-based reminders only. Odometer-based reminders aren't included.
- Kilometres and litres. There's no unit switch.
- Totals, not tax. Trips give you business and personal distance. They don't calculate tax rates or deductions.
- The web preview is partial. Backup, restore, PDF export and notifications only work in the Android and iOS apps.
- No ads, analytics or login. Good for privacy, but if you wanted any of those built in, you'd be adding them yourself.
Try it
- Web preview: https://guide.stacklynlabs.com/autolog/preview/
- Android APK: https://drive.google.com/file/d/17CtPubwb5Xt8LKvB1fhOHHptX1hxH_q5/view?usp=sharing
- Product page: https://stacklynlabs.com/product/autolog/
AutoLog is $29. It needs Flutter 3.44 or newer and runs on Android 7.0+ and iOS 14.0+.
If you've built a log-style app, did you validate readings against the history like this, or let users fix mistakes later?


Top comments (0)