Mobile app development
A complete product, from idea to the stores
A mobile app, an admin dashboard and the backend behind them, released to the App Store and Google Play. One engineer owns the whole build, so nothing falls between teams, and testing is part of it from day one.
Remote from Cairo, for business owners in Egypt and the Gulf.
What you get
- iOS and Android apps from one codebase, in Flutter or Kotlin Multiplatform.
- An admin dashboard to run the business day to day.
- The backend and API behind them, on servers in your name.
- Release to the App Store and Google Play under your own developer accounts.
- Arabic and English, with right-to-left screens designed, not mirrored.
- Testing from day one, and the full source code handed over at delivery.
Work that shows it
- TerixTerix lets wholesale customers browse one catalogue and order from several suppliers, through to delivery. I built the whole product; it is live on the web, App Store and Google Play.Live
- RamtexRamtex gives a tissue and paper-products manufacturer one app for its customers, sales reps and drivers, plus a dashboard. I built and deployed all of it; the app is live on the App Store.Live
- Malam EventsMalam Events is a Saudi marketplace where clients find an event photographer, book and follow the booking. I built the iOS app, dashboard and backend; the app is live on the App Store.Live
- VoltWashVoltWash lets customers in the UAE book a car wash online and sends each job to the wash team. I built the whole platform. The website is live; the apps are not on the stores yet.Website live
How the work goes
- 01 / Define
Map the real workflow
Users, roles, failure points and the business state each screen depends on.
- 02 / Build
Connect the surfaces
Mobile, API, dashboard, data and release tooling designed as one system.
- 03 / Stress
Test the risky paths
Permissions, payments, offline state, APIs, regressions and the ugly edge cases.
- 04 / Release
Ship with a clear status
Each project shows where it stands: live, in production, delivered to the client, pre-launch, beta or prototype.
Questions owners ask
Who owns the code, the store accounts and the server?
You do. Store accounts and servers are created in your name, and I hand over the full source code and access when the work is delivered.
How long does an MVP take?
It depends on the scope. We agree a written scope first, then I deliver working parts every week so you can see progress and change direction early.
How do payments work?
In milestones tied to the parts I have delivered, agreed in writing before the work starts.
What happens after delivery?
There is a bug-fix period after delivery, and ongoing support is optional. Both are agreed in writing, so you know what is covered.