Barbr Biz
Mobile & Backend Engineer
Booking and business platform for barbers — native iOS and Android apps plus the backend architecture powering scheduling, payments, and client management.
Service
Mobile Apps (iOS & Android)
Native and cross-platform apps, shipped through review to both stores.
I started in mobile: native Android, then Swift and Kotlin, then React Native — along with the APIs, scheduling, and payments behind them. Apps I've built are live on the App Store and Google Play today.
Sound familiar?
You probably need this if…
If two or more of these land, this is the right conversation to have.
You need one app for customers and another for staff, sharing a backend.
Your web product needs a phone-shaped version, not a wrapped website.
It works on the simulator and breaks on real devices in bad signal.
Nobody on the team has been through App Store review before.
Deliverables
What actually gets built.
Artifacts, not slides — all of it yours to keep and run without me.
- 01
Apps on both platforms
Swift and Kotlin where native matters, React Native where a shared codebase pays for itself. I'll tell you which one your product actually needs before we start.
- 02
The backend behind them
APIs, auth, push notifications, scheduling, and payments — designed alongside the app rather than bolted on afterwards.
- 03
Offline tolerance
Local state and sync that survives a lift, a tunnel, and a connection dropped halfway through a booking.
- 04
Store submission handled
Signing, provisioning, store listings, screenshots, and review responses — including the rejections, which are part of the job.
- 05
A release process, not a ritual
Automated builds, TestFlight and internal-track distribution, and versioned releases your team can run without me.
Process
How this one runs.
Three phases, with something demoable at the end of every week.
- 01
Decide native vs cross-platform
A short, honest evaluation against your feature list, team, and budget — before a line of app code is written.
- 02
Build the vertical slice
One complete flow, on a real device, in your hands early. Everything after it follows the pattern that slice establishes.
- 03
Ship and iterate
Store submission, crash reporting and analytics, then release cycles driven by what real users actually do.
The stack
What I reach for.
Defaults, not dogma — I'll work in yours where it makes more sense.
- Swift
- Kotlin
- Android
- iOS
- React
- Node.js
- PostgreSQL
Proof
Where this has shipped.
Real products, in production, with real users on them.
FAQ
Before you ask.
Native or React Native?
Depends on the app. Heavy on device APIs, background work, or animation — go native. Mostly forms, lists, and API calls with a small team — React Native saves real money. I've shipped both.
Can you take over an existing app?
Yes, including ones where the original developer is long gone. The first task is usually getting a clean build off a fresh checkout.
Do you handle the App Store and Play Store accounts?
I'll set up and drive the submission process on your accounts. You keep ownership of both, always.
What if we already have a backend?
Fine — I'll work against your API and flag early where it will hurt on mobile: chatty endpoints, missing pagination, no partial responses.
Related
Often paired with.
Need help with Mobile Apps (iOS & Android)?
Tell me what you're working on. I'll tell you what it takes — and whether it's worth building at all.