SERVICEFlutter for iOS + Android

Custom Offline-First App Development for Small Businesses

Custom offline-first app development for businesses that can't stop when the Wi-Fi does. We build Flutter apps for Android phones and iPhones that keep your bookings, stock, jobs or records on the device itself, so a dead router, a basement shop or a field with one bar of signal doesn't stop the day. Send us a brief and you get a fixed-price proposal within 24 hours.

Is this for you?

It is if you run a salon, a shop, a rental portfolio, a cleaning round, a farm or a clinic, and the apps you have tried don't fit. Some stop the moment the internet does. Some charge every month for as long as you use them. Some keep your customers' phone numbers and notes on a server you have never seen. You want an app built around how your business actually runs, that works with no signal, and that you own.

It's also for you if you are a founder with an app idea that has to work where the signal is bad: field teams, market stalls, rural areas, warehouses, anywhere a spinning wheel costs you a customer. You need an offline app developer who has already solved the local storage, reminders and backup problems, not one who will learn them on your budget.

It isn't the right fit if your app is mostly about things that need the internet by nature: customers booking themselves online, live chat, or taking card payments. Those need a connection however the app is built, so an offline-first design is the wrong starting point, and the proposal will tell you so. If you are still working out what “works offline” should mean for your business, our plain-language guide to offline business apps explains the three kinds of app and what still needs a connection, written for owners rather than developers.

Three problems an offline-first app solves

No signal, no work

Most business apps treat your phone as a window onto someone else's server. Every save goes across the internet and waits for an answer. When the router drops on a Saturday morning, the booking screen spins and the queue at the door grows. An offline-first app saves to the phone first, so the screen updates straight away whether you have full signal or none.

The monthly bill

An app whose records live on the phone doesn't need a server to keep it running, so there is no hosting bill behind it. You pay for the build once. The costs that remain are developer accounts if the app goes on the stores, and our time if you want changes later. The exception is syncing between phones, covered below, which brings a server and its bill back.

Your customers' data

Client notes, tenants' phone numbers, gate access codes and pet records stay on your device instead of on a company's server. Nobody else can see them, and nobody else can lose them for you. The flip side is that the phone becomes the lock, so it needs a PIN and a backup routine. We build the backup in; the routine is yours.

What we build

Every custom Flutter app we build starts from the same offline-first foundation, then gets the screens and records your business needs. The proposal lists exactly which of these your app includes.

  • One app for Android and iOS. Flutter builds both from a single codebase, so you are not paying for the same app twice.
  • Screens built around your day. Bookings, stock counts, jobs, tenants, patients, fields: whatever your paper book or spreadsheet holds today, laid out in the order you actually use it.
  • A local database on the phone. Every save is written to the device first. Our own apps use Hive CE and Isar Community, and we choose for your records rather than out of habit.
  • PDF receipts, invoices, estimates and reports, made on the phone with no signal. Sending them to a customer by WhatsApp or email waits until you are connected again.
  • Reminders scheduled by the phone itself, with no server involved, so an appointment or rent reminder still goes off when the shop has no signal.
  • Backup and restore to a single file that you can send off the phone, with a restore that checks the file before it changes any records.
  • Your name, logo and colours, plus the languages and currency your business uses.
  • Optional: syncing between phones. If two staff need the same records, the app still works offline and sends its changes to a server when the connection returns. That needs a backend, which runs on hosting you pay for every month, and we price it as a separate line. If you already bought an app that came with its own server and only need it deployed, that's our backend setup for purchased app templates, not a custom build.
  • Finished builds, ready for Google Play and the App Store, or installed straight onto your own phones with no public listing if the app is only for you and your staff.

How offline-first works, in plain words

Think of a paper appointment book that also happens to copy itself. You write in the book, not in a letter you post to head office and wait for a reply. The app reads and writes its own records on the phone, so nothing waits for the internet. If your app has a server, the phone sends its changes in the background whenever a connection is available, and nobody has to watch it happen.

That design has two honest trade-offs:

  • One phone, one set of records, unless you add syncing. Without it, a second phone starts empty.
  • The backup matters more. A lost phone with no backup takes its records with it. No feature fixes that after the fact; a habit of backing up at closing time does.
Offline-first app vs normal app: one waits on a server for every save, the other saves on the phone first
An offline-first app saves on the phone first, so a dropped connection doesn't stop your day.

A few things still need a connection in any app: card payments (the bank has to approve them), sending a receipt or backup to someone else, app updates, and ads if an app shows them. Everything else keeps going. If someone on your side wants the technical version, hand them our offline-first architecture blueprint for Flutter apps. It is written for developers, so you don't need to read it yourself.

Offline-first apps we have already built

We don't have client case studies or testimonials to show you. What we can show you is our own apps. Each one below is an offline-first Flutter app we wrote and sell as source code to other developers. They are products, not client projects, and each has a demo you can try on an Android phone or in your web browser. A custom build uses the same foundation; what changes is the screens and records, which are yours.

Salons and barbers

StyleBook, our offline salon and barber app, keeps a client list with photos and visit history, books appointments with a reminder 1 hour before each one, and tracks income, expenses and net profit. All data stays on the device, and its backup is a single ZIP file that includes every client photo. It comes in four languages, including Arabic laid out right to left.

Landlords and rentals

Rent Folio, an offline rent tracker for landlords, shows every tenant as Paid, Due soon, Overdue or Upcoming, turns any payment into a PDF rent receipt, logs repairs and what they cost, and sends a reminder from the phone 2 days before each rent due date. It has no server, no account, no ads and no analytics, and it checks a whole backup before restoring anything.

Cleaning and field jobs

CleanSync, our cleaning job and invoice app, runs each job with a timer and a checklist, keeps client properties with their gate or access codes, and makes PDF estimates and numbered invoices. It has no backend, no Firebase project and no user accounts, so it works without a connection from the first launch.

Pet records

Vet Vault, an offline pet health records app, holds medical records, vaccination reminders and a shareable PDF health passport for each pet. Its release Android build has no internet permission at all. It is built for pet owners; for a clinic, groomer or shelter it shows the approach, not finished clinic software.

How our custom offline-first app development works

  1. You send a brief through the hire form, with Mobile App as the service. Plain words are fine. Describe a normal day and what you want the app to keep track of.
  2. You get a fixed-price proposal within 24 hours: what the app will do, what it won't, the price, the timeline, and anything that still needs a connection. Nothing starts until you agree. Larger projects are paid in milestones rather than all up front, by PayPal, Wise or bank transfer.
  3. We build it and send you working builds to try on your own phone at each milestone, so you see progress in your hands rather than in a status report.
  4. We test it offline. Phone in airplane mode, a full normal day: book, sell, log, print, back up, restore. Then the connection goes back on and we check nothing was lost or counted twice. We ask you to run the same test before you sign off.
  5. We launch it. Either we install it on your phones, or we publish it to the stores from your own developer accounts, doing the same work as our Google Play and App Store submission for finished apps. You get the full source code at the end.
Custom offline-first app development process: brief, fixed-price proposal within 24 hours, build, offline test, launch
Nothing starts until you agree to the fixed-price proposal, and the source code is yours at the end.

What we need from you

  1. A description of a normal working day, and the busy one: who uses the app, when, and what they enter.
  2. What you keep track of today: a photo of the paper book, the spreadsheet, or the app you want to replace.
  3. How many people and phones will use it, and whether they need to see the same records. This one question decides whether you need syncing.
  4. Which phones: Android, iPhone or both, and any tablets.
  5. Must-haves and nice-to-haves, kept as two separate lists. It keeps the first version affordable.
  6. Your business name, logo and colours, plus the languages and currency you use.
  7. Samples of what the app must produce: a receipt, an invoice, a report you hand to your accountant.
  8. Whether it goes on the stores, and if so, developer accounts in your name, or a note that you don't have them yet.
  9. Your budget range and any deadline, so the proposal fits them or tells you plainly what would.

Not sure about some of this? Send the brief anyway and we'll ask what we need.

What's not included

  • Hosting fees, if your app syncs through a server. You pay the provider directly, every month the app is live.
  • Developer account fees. You pay Google and Apple directly, on accounts in your name.
  • Card payment processing. Taking a card needs the bank, and the bank needs a connection. Card payments stay with your card reader and its own rules.
  • Entering your existing records into the app, unless the proposal says otherwise.
  • Writing your privacy policy. We tell you what the app collects; the policy is yours.
  • A guarantee of store approval. Apple and Google decide.
  • Changes and new features after the support period stated in your proposal. We quote those separately.

Custom build, subscription app, or a rebranded ready-made app

A custom build isn't always the right answer. A subscription app gets you started today, and one of our ready-made apps with your brand on it costs far less than a build. If one of them covers your business, our service for rebranding one of our ready-made apps is the cheaper path. Here is how the three compare.

Subscription appReady-made app, rebrandedCustom offline-first build
What you payUsually a monthly fee, for as long as you use itThe app's licence plus a rebrand from $150A fixed price in your proposal, paid once
Works with no internetDepends on the product; test it in airplane modeYesYes, designed in from the start
Fits how you workYou adapt to its featuresThe app's features as they are, with your brandBuilt around your day and your records
Where your records liveUsually on the company's serverOn your phoneOn your phone, plus your own server if you add syncing
Two phones, same recordsUsually yes, liveNo, not without custom workYes, if you include syncing
Time to startOften the same dayOur part typically 5 to 10 business daysStated in your proposal
If you stop payingCheck the provider's terms for your dataNothing to stop; the app is yoursNothing to stop; the app and code are yours

Subscription apps win on syncing and on starting today, and for a business with many staff sharing live records, that can outweigh everything else. The two right-hand columns win when the internet is unreliable, when the monthly fee adds up, or when you would rather your customers' details stay on your own device.

FAQ

Frequently Asked Questions

The questions business owners ask before they send us an app idea.

Yes, that is the point of building it offline-first. Your records live on the phone or tablet, so booking, selling, logging a job or making a PDF receipt works with no connection at all, for as long as the connection is down. A few things around the edges still wait for a signal: taking card payments, sending a receipt or backup to someone else, and app updates. We list those for your app in the proposal, so there are no surprises on a busy day.

We don't publish a price for custom builds, because a three-screen job logger and a shop till with stock, receipts and two languages are very different jobs. Send a brief and you get a fixed-price proposal within 24 hours, before any work starts. If one of our ready-made apps already covers what you need, the proposal will say so, because rebranding one of those starts from $150 and is far cheaper than a build.

Not with a purely offline app. Each phone keeps its own records, so a stylist and a receptionist would not see each other's bookings. Sharing one set of records between phones needs syncing, which means a server and a monthly hosting bill. We can build it, and the app still works offline and catches up when the connection returns, but it is a bigger project. Tell us in the brief if you need it and we price it as a separate line.

If there is no backup, they go with the phone. That is the trade-off of keeping records on the device. Every app we build includes a backup to a single file that you can send to Google Drive or your own email, and a restore that checks the file before it changes anything. Make a backup at closing time and test a restore once, before you need it.

You do. You get the full source code when the project is finished. If the app goes on Google Play or the App Store, it is published from developer accounts in your name, not ours, and you pay Google and Apple their fees directly. All projects are under NDA by default.

No. Apple and Google make that decision, and nobody can honestly promise their answer. What we do is build and prepare the app so the common reasons for rejection are out of the way first: privacy forms filled in, a privacy policy that loads, screenshots at the right sizes and a build that meets the current store rules. If the app is only for you and your staff, we can also install it straight onto your phones with no public listing.

It depends on how many screens and records the app has, and on whether it needs syncing. The timeline is written into your proposal next to the price, so you can plan around it. Most delays come from waiting on answers, logos or account access, not from the build itself. Store review comes after our part and isn't something we control.

It is different rather than simply safer. No outside server holds your customers' names and notes, so they cannot leak from one. But the phone itself becomes the lock, so protect it with a PIN or fingerprint and keep a backup somewhere private. If you need the records encrypted on the phone as well, put it in the brief and we include it in the scope.
Ready to Build

Ready for an app that works with no signal?

Tell us what your business does, what you keep track of, and how many phones will use the app. You'll get a fixed-price proposal within 24 hours, before any work starts.