Ship a car maintenance and fuel log app with the parts you would otherwise build for weeks already in the box: 18 finished screens, a fuel tape that settles consumption only between two full tanks, a service board of dipsticks that fill as you drive, a cost wheel with the real cost per kilometer, a handover sheet for the next owner, Google and Apple sign-in, in-app purchases, push, three languages, a Laravel cloud backup with an admin panel and a landing page. Dark and light, every screen walked by a test driver.

Garagora: every fill-up, every service, one honest number, with every feature built in listed on the cover

Demo Instructions: the live preview opens on four demos, listed below under See every part before you buy. In the app, the sign-in form arrives filled with the demo account, demo@garagora.app / demo1234, and any other email and password work too, including empty fields. Demo mode is on out of the box, so there is nothing to register and no network needed: the Garage tab opens on three sample vehicles with eighteen months of fill-ups, services and costs.

Why this one

The integrations are already done: Google and Apple sign-in, in-app purchases, push notifications, analytics and crash reports, Face ID / fingerprint lock, update prompts, three languages with RTL, a share sheet and remote images, each behind one interface and switched on from one config file. The paywall lifts the two-vehicle limit of the free plan.
A server and a landing page come with it: backend/ is a Laravel cloud backup with a Filament admin panel: the app backs up every account’s garage and its photos by itself after each change, and the panel opens any snapshot record by record; landing/ is a one-page product site already in Garagora’s colors.
Ready to show on day one: 18 screens with empty states, kilometers or miles, liters or gallons, and a driver that walks every screen before each release; 123 app tests pass, and the back end has 88 more of its own.

Nine things you will not have to build

Sign in with Google and Apple: the id token is exchanged with the included back end for a session; buttons appear only for the providers you configure.
In-app purchases and a paywall: App Store and Play products behind one gateway; prices come from the store, the unlock survives offline, restore is one tap.
Push notifications: send from your admin panel to every install, naming the screen a tap opens; permission is asked from Settings, foreground display included.
Analytics and crash reports: every screen view and the errors people actually hit, behind a consent switch.
Face ID / Touch ID / fingerprint lock: lock on launch, since the garage and its photos are kept on the phone; disabled on phones with nothing enrolled.
Three languages with RTL: English, Spanish and Arabic; add a language by copying one file; the server answers in the same language.
Update prompts: gentle and forced updates you announce from the admin panel’s App updates page, the day you release.
Share sheet: the handover sheet goes to a buyer or a mechanic as an image through the system sheet, iPad anchored.
Remote images: vehicle photos from the camera, your server or bundled files, with placeholders and fallbacks.

See every part before you buy

Everything above is one click away in the Live Preview, not just the app. It opens on a page with four demos, and All demos brings you back from each one:

The Live Preview entry page with four demos: the app, the documentation, the admin panel and the landing page

Mobile app: the Flutter app running in your browser inside a phone frame, with the sample garage already loaded.
Documentation: the full HTML documentation, the same file that ships in the download.
Admin panel: a read-only snapshot of the Laravel admin from a live install: the dashboard, every sidebar page, the backups list and the settings.
Landing page: the product website included in the download, already in Garagora’s colors and type.

Only the source code waits for the download.

The fuel tape

Every fill-up prints onto a thermal receipt; a full tank is stamped with its consumption, a top-up is carried into the next full one, and a tank far outside the car’s own range is set aside instead of bending the average.

The fuel tape: consumption that survives a top-up, settled only between two full tanks

The service board

Every service item is a dipstick that climbs as you drive, with a lower mark for due soon and an upper mark for due; each item runs on distance, on time or whichever comes first, and its due date is worked out from how far you actually drive.

The service board: every service item on a dipstick that climbs as you drive

The cost wheel

Fuel, service, insurance, parking, tolls and the rest as spokes as long as what they cost, with the cost per kilometer in the hub; tap a spoke to see just that category.

The cost wheel: what a kilometer really costs, one spoke per category

The garage

Each vehicle on a card with its photo, a rolling odometer and what is due next; the bell collects everything due across the garage.

The garage: every vehicle with its odometer and what is due next

The handover sheet

The odometer, the last twelve months of distance, consumption and spend, the service history and what is coming up, on one page to share.

The handover sheet: one page for the next owner

Plus the screens a real app needs: onboarding, sign-in and sign-up, vehicle editor, fill-up, service and expense sheets, service item editor, due list, units and currency, settings with backup and CSV export, cloud backup, about and the Pro screen.

Units: kilometers or miles, liters or gallons, four separate settings

Every screen a driver needs, dark and light, in three languages

Landing page included

The download ships a one-page product website for your app (landing/): hero with two phone mock-ups, three feature tiles, a screen gallery, FAQ and store buttons, already set in Garagora’s colors and type; swap the copy and the store links and publish it anywhere static HTML is served.

The included one-page product website, in Garagora's colors

Laravel back end included

backend/ is a Laravel cloud backup with a Filament admin panel: people sign up from the app, which then backs up by itself a little after each change, photos included; each upload is kept as a version per account (the newest five by default) and the latest one restores on a new phone in one tap, photos and all. The panel opens any snapshot to show every vehicle, fill-up, service and expense it holds, with the account’s photos, and adds Pictures, App updates, Send notification with scheduling, Push history, social sign-in exchange and a Docker compose file. Point the app at it with one --dart-define=API_BASE_URL, or type the address in the app’s settings. It needs PHP 8.4 or Docker.

The included server: a garage that survives a new phone, with versioned backups per account

Built for developers

Clean GetX architecture: View, Controller, Service, with every calculation in plain Dart engines the screens only call.
Three pure Dart engines: fuel, service and cost, each with its own tests and liftable into another app.
Metric inside, any unit outside: every record is stored in kilometers and liters, and distance, volume, the consumption format and the currency symbol are separate settings that only change what is printed.
One config file for every integration: feature_config.dart holds the product ids, client ids and switches.
One color file re-skins the app, and the icon and the landing page are generated from the same palette.

What you get: full Flutter source code with the nine feature packs, the Laravel cloud backup with admin panel, the landing page, a README, offline HTML documentation (38 chapters, 30 figures), sample data, dark and light themes, and 11 licensed photographs.

What you get: screens, features, tests, the cloud backup, the landing page and the documentation

Notes

The app records what the driver types in: odometer readings, fill-ups, services and expenses. It does not connect to the car, read an OBD port or fetch fuel prices, and due items are shown inside the app, on each vehicle’s card and in the due list, rather than scheduled as device notifications.

Without a server the app runs in demo mode on its bundled sample garage; connect the included back end when you deploy it. Photos travel with the cloud backup; the JSON file the app exports through the share sheet carries the records only. Figma or Sketch source files are not part of this item.

Third-party services and external costs: connecting Garagora to hosting, Firebase or the app stores will involve those third-party services, and using Google and Apple sign-in, push notifications, analytics or in-app purchases will incur their own separate costs and developer accounts, which are not included in this item.

Garagora | Flutter Car Maintenance and Fuel Log App with Laravel Cloud Backup