Custom iOS and Android apps for Kuwait and the GCC. Arabic RTL and KNET built in from the start, not bolted on at the end.
An app that works in a demo and an app that survives real users are different products. The second one needs a backend that holds up, a data model somebody thought about, and a developer who has shipped into the App Store before and knows what gets rejected.
I build custom iOS and Android apps for clients across Kuwait and the GCC, and I build the backend behind them, so nothing falls between two vendors.
Building for Kuwait is not building for a generic market
This is the part most quotes skip, and it is where projects run over.
Arabic RTL that was designed, not mirrored. A layout flipped at the last minute looks flipped. Bilingual architecture from the first screen costs less than retrofitting it in month three.
Local payments. KNET, MyFatoorah and Tap, alongside Stripe where the audience needs it. A Kuwaiti checkout that only takes international cards loses most of its customers at the last step.
Local context. I have worked with clients in Kuwait, Bahrain and Saudi Arabia, including the data and business rules that come with that.
Where projects usually start
An MVP. One user journey, everything else cut, something real in your hands in weeks rather than months. The point is to find out whether people want it before you spend the rest of the budget.
Growth. You have users and feedback. Features get added and the infrastructure scales to match what the numbers now say.
A full platform. Customer app, driver or vendor app, web dashboard, admin panel and reporting. I have built multi-role platforms for food, retail and services businesses.
An MVP I build is meant to grow into the second and third of those, not to be thrown away and rebuilt in six months.
The stack
React Native, Flutter and Expo on the app side. Laravel or .NET for the API and business logic. Firebase or Supabase where real-time and auth matter, PostgreSQL or MySQL where the data has structure worth keeping. Docker and GitHub Actions for deployment.
The framework gets chosen to fit the project. There is no default.
How it works
- A call. You show me the idea and who it is for. Free, 30 minutes.
- Scope. Users, core features, what is deliberately out, and what it costs. In writing.
- Design and build. Wireframes before code, then sprints with working builds you can install and use.
- Store submission and handover. App Store and Google Play listing, then source, documentation and a deployment your team runs.
What I will tell you first
If the idea needs a different shape than the one you arrived with, you hear it on the call. If a web app would serve you better than a native one, which happens more often than you would think, I will say so before you pay me.
Ready to start?
Tell me what you want to build and who it is for. If it is a project that needs rescuing rather than starting, say that too.
Reach me by email, on LinkedIn, or fill in the form on this page.