Hand the drivers of one auto repair shop an app that follows their car from the drop-off lane to the pickup counter: 23 finished screens, a service lane painted with the six stations the car passes, an estimate answered line by line with initials and one signature, a 24-point inspection sheet with the technician’s photos, Google and Apple sign-in, in-app purchases, push, three languages, a Laravel back end whose Shop desk runs the floor, and a landing page. Light and dark on every screen.

Hoistora: answer the estimate, watch the car come off the lift, with every feature built in listed on the cover

Demo Instructions

The Live Preview starts on a page with four doors, described below under Try all four parts before you buy. The app’s sign-in screen contacts no server in the demo and lets any email and password through: type demo@hoistora.app with demo1234, or leave both fields empty and tap Sign in. Demo mode is already switched on, so there is nothing to register and nothing to install: Hoistora opens on a sample shop with three cars, one of them on the lift with an estimate waiting for your OK. Answer that estimate, then open Settings and tap Advance the shop to walk the car along the lane until it is ready for pickup. Once the back end in the download is running, a new driver confirms the sign-up with a six-digit code from email, and Forgot password works the same way; the Docker setup catches those emails in a Mailpit inbox at http://127.0.0.1:8025.

Driver account in the app — Email: demo@hoistora.app · Password: demo1234
Admin panel, after you install the back end from the download — Email: admin@hoistora.test · Password: password

Costs not included in the price

Google Sign-In, Sign in with Apple and push notifications only work with your own paid developer accounts and services (an Apple Developer Program membership, a Google Play Console account, a Firebase project), and so do analytics, crash reports, in-app purchases and publishing to the stores. Sign-up codes, password-reset codes and the shop’s emails to drivers go out through your own SMTP email provider. Hosting for the back end is a separate service too. All of them bill you directly and are not included in the purchase price of this item.

Three reasons a shop picks Hoistora

Every integration is wired, not sketched: Google and Apple sign-in, in-app purchases, push, analytics and crash reports, Face ID / fingerprint lock, update prompts, three languages with RTL, a share sheet and remote images each sit behind one interface, switched on from a single config file. In Hoistora the paywall gates sharing an inspection sheet or an invoice, and a push can open the work order it is about.
The shop’s side ships too: backend/ is a Laravel API with a Filament Shop desk where the front desk checks a car in, writes the estimate, punches the inspection, marks the car ready and records the payment; every press shows up in the driver’s app. landing/ is a one-page product site already painted in Hoistora’s colors.
Demo-ready the day you unzip it: 23 screens with their empty states, four pure Dart engines (stage, estimate, inspection, visit) run against the same table of cases as their PHP twins on the server; 139 app tests pass and the back end adds 163 of its own.

Nine things you will not have to build

Sign in with Google and Apple: the phone hands the provider’s id token to the included back end and gets a driver session back; a button shows only when its provider has client ids in the config.
In-app purchases and a paywall: the Pro screen lists App Store and Google Play products through one gateway, with store prices, an unlock that holds with the phone offline and a one-tap restore; Pro is what lets a driver share an inspection sheet or an invoice.
Push notifications: from the admin panel’s Send notification page to every install, now or scheduled, naming the screen a tap should open, such as the work order whose estimate is waiting; the permission is asked from Settings, not at launch.
Analytics and crash reports: screen views and the errors drivers actually meet, behind a consent switch in Settings; cars, plates, estimates and signatures never leave the phone this way.
Face ID / Touch ID / fingerprint lock: a lock on launch and, while it is on, the same check again before an approval with a signature is sent; it stays hidden on phones with nothing enrolled.
Three languages with RTL: English, Spanish and Arabic on every screen, with the lane and the approval sheet mirrored for Arabic; a fourth language is one copied file and one entry in a list, and the server answers in all three.
Update prompts: a soft nudge or a hard stop, announced from the admin panel’s App updates page on the day a release goes out, with the store links filled in.
Share sheet: an inspection sheet or an invoice leaves as text through the system share sheet, to a partner, a second shop or the driver’s own notes, anchored correctly on iPad.
Remote images: the technician’s inspection photos and the shop’s pictures load from your server, from the phone or from bundled assets through one widget, with placeholders while they arrive and a fallback when they do not.

Try all four parts before you buy

Nothing above has to be taken on trust: the Live Preview opens on a page with four doors, and an All demos link at the top of each brings you back to it.

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

The app: Hoistora itself, built for the browser and framed as a phone, already signed in to the sample shop with the car on the lift.
The manual: the same 43-chapter HTML file that sits in the download, with its 29 figures.
The admin panel: a read-only snapshot taken from a real install, with the dashboard, the Shop desk, every sidebar page and one opened work order.
The landing page: the one-page product site from the download, as it renders in Hoistora’s colors and type.

The full source code is included with every license type, Regular and Extended alike.

The service lane

Six stations painted on the workshop floor, from checked in to ready for pickup; the car’s hang tag hangs over the station it is at, each station passed gets a sprayed tick, and a red slip drops from the tag when the shop needs your OK.

The service lane: the car on the shop floor, with its hang tag over the station it is at

The estimate, line by line

Every part and every hour of labor on its own line, grouped as safety now, soon and can wait; initial a line to approve it, tap again to strike it out, watch the total move, sign once and send.

The estimate: say yes line by line, with initials and one signature

The punched inspection sheet

24 checks in five groups in the order a technician walks round the car, each punched green, amber or red with the measurement and the photo the technician took; every estimate line that comes from a red or amber check points back to it.

The inspection sheet: punched green, amber or red, with the technician's photo

The windshield sticker

Every car carries the next service by mileage or by date, whichever comes first, counted from its last visit, and turns amber when it is close.

Your cars: the next service on a windshield sticker

Book a visit

Pick the car, pick from the shop’s own service menu, say what you noticed, then a morning or an afternoon; closed days and passed windows cannot be picked.

Book a visit: a morning or an afternoon, asked for

The work order and the invoice

What you said, what the shop says, the estimate and the inspection in short, every move along the lane with its time, and the invoice once the car is paid for.

The work order: everything the shop said, in one place

Around them, the screens that make it a whole app: onboarding, sign-in and sign-up, the car list, car detail with its service history, the car editor, the visit requested screen, the photo viewer, account, the shop’s contact page with call, email and directions, settings, about and the Pro screen.

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

Landing page included

Under landing/ you get a one-page product site for Hoistora: a hero with two phone mock-ups of the lane and the estimate, three feature tiles, a gallery of the screens, a FAQ and store buttons, already painted in the app’s colors and set in its typefaces. Replace the copy and the store links and host it on any static server.

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

Laravel back end included

backend/ is a Laravel API with a Filament admin panel whose center is the Shop desk: every car booked in or sitting in a bay on one page, with Check in, Advance, Write estimate, Fill inspection, Mark ready and Close within reach of the front desk. Drivers sign up from the app, ask for visits, answer estimates and see every move the next time they open it; the same rules that run in the app decide on the server which station a car may move to, checked against one shared table of cases. The driver gets a six-digit code by email to sign up or to reset a forgotten password, and an email when a visit is requested, when an estimate is waiting for an OK, when the car is ready and with the receipt. The panel also holds the service menu, the bays, the inspection sheet’s points, App updates, Send notification with scheduling, Push history and the social sign-in exchange, and the folder carries a Docker compose file. One --dart-define=API_BASE_URL points the app at it. PHP 8.4 or Docker is required.

The included server: the shop desk behind every move, with the estimate lines it holds

For the developer who takes it over

GetX, kept thin: views, controllers and one ShopService; the arithmetic sits in four plain Dart engines that the screens only call.
Four engines, one table of cases: stage, estimate, inspection and visit, each run against the same JSON cases as the PHP versions on the server, so the app and the Shop desk cannot disagree about a total or a move.
One repository interface, two sources: the bundled sample shop and the live API, and the sample shop is the same JSON file the server seeds from.
Every switch in one file: feature_config.dart holds the product ids, the client ids and the on/off for each integration.
Re-skin from one palette: the colors file drives the app, and the launcher icon and the landing page are generated from the same values.

What you get: the complete Flutter source with its nine integrations as local packages, the Laravel back end with the Filament Shop desk, the landing page, a README, offline HTML documentation (43 chapters, 29 figures), the sample shop, light and dark themes, and 14 licensed sample photographs with their license list.

What you get: screens, features, tests, the back end, the landing page and the documentation

AI disclosure

AI-assisted tools were used to help write and review the source code and the documentation of this item. The author reviewed, tested and finalized every part before release. The 14 photographs are licensed Pexels stock, each listed with its photographer in assets/images/shop/LICENSES.txt; no image-generation model was used. Nothing in the app or the server calls an AI model while it runs.

Notes

Hoistora is the driver’s side of a single shop. Payment is taken at the counter and recorded by staff in the admin panel; the app shows the approved total, the invoice and the moment it was settled.

Until the back end is deployed and the app pointed at it, Hoistora runs on its bundled sample shop, which is enough to try every screen. Figma and Sketch files are not included; the interface is defined in the Dart source. The sample photographs are Pexels stock, listed with their sources in assets/images/shop/LICENSES.txt, and the car makes in the sample shop are invented.

Hoistora | Flutter Auto Repair Shop App With Laravel Admin