A published app, in your name
Submitted and released on the App Store and Google Play from developer accounts registered to your company. If we stop working together, you keep publishing.
Services
Mobile app development in Cairo, for iOS and Android
One Flutter codebase, published to the App Store and Google Play under your own developer accounts. Two of the apps we have shipped are live in both stores right now, and you can open them before you talk to us.
Who this is for
- A business whose customers already ask for an app — a gym, a clinic, a service company, a retailer.
- An operation running on phone calls and WhatsApp messages that should be bookings, orders or job tickets.
- A founder who needs a first version in front of real users, not a prototype that only demos well.
- A company with an existing app that has been abandoned by whoever built it.
What usually goes wrong before we are called
Almost every rescue project we take on has the same three symptoms. The app was quoted per feature, so the price grew every month. It was built twice, once for iOS and once for Android, so every fix has to be made and tested twice. And the developer accounts are in someone else's name, so the client cannot publish an update without them.
All three are avoidable, and all three are decisions made in the first week rather than the last.
What you get
One codebase for both platforms
Flutter, so a fix or a new screen is written once. That roughly halves both the build and the ongoing maintenance cost against two native apps.
The parts that break in production
Accounts and sign-in, payments, push notifications, offline behaviour, deep links and analytics — specified in the quote, not discovered later.
An admin side, if you need one
Most apps need somewhere for you to manage content, users and orders. We build that as part of the same system, not as a separate project.
How we build it
Flutter for the app itself. It renders its own interface rather than wrapping a web page, so scrolling, gestures and animation feel native, and one team can hold the whole product in their head.
For the backend we use Firebase when the app is mostly reads, notifications and authentication, and Node.js with PostgreSQL when it has real business rules, reporting or role-based access. We tell you which one we are proposing and why, before the quote.
Payments are integrated with the gateway that actually settles into your bank in your country. We have shipped MyFatoorah and Stripe in production; PayTabs and other regional gateways are straightforward to add.
Arabic and right-to-left support is built in from the first screen rather than retrofitted. Three of the apps in our portfolio ship bilingual Arabic and English interfaces.
- Flutter · one codebase for iOS and Android
- Firebase or Node.js + PostgreSQL, chosen per project
- Stripe, MyFatoorah, PayTabs and regional gateways
- Push notifications, geolocation, deep links, Apple Wallet passes
- Full Arabic / right-to-left layout and Hijri dates
Timeline and milestones
A focused app is two to four months from the scope call to the store. The work is split into three or four milestones, and you see a build you can install at the end of each one.
- Week 1 — scope call, written scope summary, fixed quote and milestone plan.
- Weeks 2–3 — screens and flows agreed before development starts.
- Milestones 1 to 3 — a working build at each, with 30% paid upfront and the rest per accepted milestone.
- Launch — store submission from your accounts; we handle review feedback until it is live.
- Then twelve months of free support, with small changes free for the first three.
What it costs
Every project is quoted as a fixed price in USD after a free scope call — never per hour. The number depends on how many user roles the app has, whether it takes payments, and how much of a backend it needs.
Tell us the budget you have in mind and we will tell you honestly what fits inside it, or whether a smaller first version reaches the same goal. If it does not fit, we say so rather than quoting something that will run over.
- Fixed quote in USD, written, before you commit.
- 30% upfront, the rest per delivered milestone.
- Running costs (Firebase or a server, plus $99/year for Apple and a one-time $25 for Google Play) are billed to your own accounts and estimated in the quote.
Related work
Q-Fight Gym
Gym booking app · Qatar
Read the case study →
Al-Muslim
Daily companion app
Read the case study →
Ezhal
Multi-role car-service platform
Read the case study →
Common questions
Will the app be as good as a native one?
For the apps most businesses need — booking, content, accounts, payments, notifications — a Flutter app is indistinguishable from native in daily use, and it ships to both stores at once. If your product depends on something Flutter cannot reach well, such as heavy on-device video processing, we will say so and quote native instead.
Do you submit the app to the stores for us?
Yes. Store submission is part of launch, and we handle review feedback until the app is published. The developer accounts are registered in your company's name, so the listing, the reviews and the ability to publish updates stay with you.
Can you take over an app someone else built?
Yes. We start with a short code review and give you a written verdict — fix, refactor or rebuild — before any larger commitment. Sometimes the honest answer is that the code is fine and the problem is elsewhere.
Do you build the backend too?
Yes. An app is rarely just screens: it needs accounts, an admin side, and somewhere for the data to live. We build the whole system, and you own all of it.
Get a fixed quote for your app
Describe what it should do and who will use it. You get a scope summary and a written price in USD, before you commit to anything.