Every tailor I know keeps his whole business in paper registers. One notebook for measurements. Another one for orders. Payments live in a third place, which is mostly his memory. It works, right up until the busy season, when the pages fill with arrows and crossings-out and one regular customer's sizes end up in the margin of a book from two years ago.

TailorVexa is the app I built to replace those registers. It runs a tailoring shop from the phone in the tailor's pocket: customer profiles, measurements, orders and payments, all in one place. And the decision I made before writing a single screen still shapes everything about it:

No internet required. No account. No server. Everything stays on the phone.

Why offline-first was the whole point

In the markets where this app gets used, the connection comes and goes, and mobile data costs real money. An app that asks for a login before it will show a customer's chest size is an app that gets deleted by the end of the week. But connectivity was only one of three reasons.

Trust. A tailor's measurement book is his business. Plenty of shop owners do not want their customer list sitting on a stranger's server, and honestly, I understand them. The list is the shop.

Cost. A backend charges you every month, forever. I build with a zero budget, so every recurring cost is a countdown to the day the thing shuts down. An app with no server has no such countdown.

Speed. Reading from local storage is instant. A tailor standing at the counter, tape around his neck, a customer waiting — he will not stand there watching a spinner.

The stack

  • Flutter for the interface, one codebase aimed at Android
  • Drift on top of SQLite for storage — customers, measurements, orders and payments as proper relational data, all on the device
  • English and full Urdu, with a real right-to-left layout, because Urdu is the language the shop actually works in
  • PIN and biometric lock, because the phone gets passed around during a working day
  • JSON backup and restore, so the whole shop can move to a new phone from one exported file

That backup piece matters more than people expect. The first question anyone asks about an offline app is what happens when the phone is lost. A file the owner exports himself, keeps where he likes, and imports on the next phone answers it — no cloud, no signup, no subscription standing in between.

What the app actually does all day

Each customer gets a profile, and the profile holds everything: his measurements, his orders, what he has paid and what he still owes. A regular walks in after eight months and his full record is on screen in seconds. Anyone who has watched a tailor dig through last season's diary while the counter fills up knows what those seconds are worth.

Measurements got the most care, because they are the heart of the record. The standard sizes sit in their own fields — chest, waist, length, sleeves, the usual list. And because every experienced tailor keeps notes that never fit a printed form, the app lets him add his own measurement entries too: his own names, his own words, saved with the customer's profile and carried through backup and restore like everything else. One tailor's shorthand is another tailor's confusion, so the app does not force anyone into ready-made boxes.

Orders carry the booked date and the promised date, and where each one stands — pending, ready or delivered. Payments are written into the order itself: advance taken, part payment later, balance on delivery. When a customer asks what is left on his suit, the answer is a look at the screen, not a debate between two honest memories.

The honest trade-offs

No server means no sync between two phones, and no automatic cloud backup sitting somewhere. I do not dress that up. For a single-shop business, one phone is the office, and for that reality local-first is not the cheap option. It is the correct one.

The full app page, with screenshots and the download, is here: TailorVexa on AI Tech Apps.

If you build for people outside the always-online world, I would argue offline-first is not the fallback plan. It is the product.

More from AI Tech Apps: