Most first apps do not fail because the code is bad. They fail because version one tried to be version three. A founder lists every feature a competitor has, adds a few more, and ends up with a long build and a stretched budget. The opposite mistake is just as common: an MVP so thin that customers try it once, find nothing useful, and never open it again. This guide is about drawing the line in the right place for a UAE audience, and about the small number of decisions that are cheap to make now and painful to change later.
What an MVP actually is (and is not)
A minimum viable product is the smallest version of your app that lets real customers complete one valuable job from start to finish, and lets you learn whether they want to keep doing it. Both halves matter. "Complete a job" means the journey works end to end, including payment, confirmation and support. "Learn" means you can see what people do, where they drop off and what they ask for next.
Step 1: Write the core journey in one paragraph
Before you list a single feature, describe the main journey the way a customer would experience it. For example: "A resident in Dubai Marina opens the app, picks a cleaning slot for tomorrow, pays by card or Apple Pay, gets a confirmation and a reminder, and can message the company if the cleaner is late." That paragraph is your scope in miniature. Every screen in version one should exist to make that paragraph work.
Then ask three questions of it:
- Who is the first user? Not "everyone in the UAE", but the one group you will market to in the first months. Their language, phone habits and payment preferences shape the build.
- What is the trigger? Why would they open the app instead of calling, using a website or sending a WhatsApp message? If you cannot answer this, the MVP needs to be rethought before it is scoped.
- What does success look like after the first visit? A booking, an order, a completed form, a repeat visit within a week. Pick one number you will watch.
A good MVP scope starts from one customer journey, not from a feature list.
Step 2: Sort every feature into three columns
Once the journey is written, collect every feature idea from the team, the sales staff and the competitor review, and sort each one into a simple table: Launch, Version two and Not now. The test for the Launch column is strict: if this feature is missing, can the customer still complete the core journey and trust the business? If yes, it moves to the right.
Features that usually belong in version one
- Sign-up and login that fit the audience, often phone number with a one-time code, plus email or social login if your users expect it.
- The core journey itself: browse, choose, book or order, pay and confirm.
- Basic account details: profile, order or booking history, and the ability to delete the account.
- Transactional notifications: confirmation, reminder, status change.
- A clear way to get help, which in the UAE very often means a WhatsApp button.
- A simple admin panel for your team to manage content, orders and users.
- Analytics and crash reporting.
Features that can usually wait
- Loyalty points, referral schemes and promo-code engines.
- In-app chat built from scratch, when a WhatsApp hand-off already solves the problem.
- Multiple branches, multiple currencies or multiple countries, unless you launch in them on day one.
- Advanced filters, wish lists, reviews and ratings.
- Deep integrations that can run manually for the first few months, such as pushing every order into an ERP automatically.
Step 3: Know which decisions are expensive to postpone
The three-column exercise works for features. It works badly for foundations. Some choices look like extras but are really structural, and adding them after launch means reworking screens, data and code that are already live. For UAE apps, these are the ones to settle in version one even if the MVP is small.
Arabic and right-to-left support
You may decide to launch in English only, and for some audiences that is reasonable. But the app should be built so that Arabic can be switched on without a redesign: text kept out of the code, layouts that use start and end rather than left and right, and a design system that has been checked in a right-to-left mirror at least once. Retrofitting this into a finished app costs far more than doing it from the first screen. If your first users include Arabic speakers, launch bilingual and make sure both languages feel designed rather than translated.
Your account and data model
How you identify users (phone, email or both), how families or companies share an account, and what personal data you store are hard to change later. Collect only what the journey needs. The UAE has a federal personal data protection law (PDPL), and it is much easier to build consent, data access and deletion into a small app than to bolt them onto a large one.
Analytics events
If you do not measure the core journey from day one, the first months after launch teach you very little. Define a short list of events before the build starts: app opened, sign-up started, sign-up completed, item viewed, checkout started, payment succeeded, payment failed.
Step 4: Choose UAE payment options for the MVP
Payments are where UAE MVPs most often grow without anyone noticing. It is tempting to offer every method at launch. A better approach is to pick the smallest set that your first users actually rely on.
- Cards through a local or regional gateway. The baseline for almost every app selling physical goods or services.
- Apple Pay and Google Pay. Widely used in the UAE and usually supported by the same gateway, so they add convenience without much extra scope.
- Buy now, pay later. Tabby and Tamara are popular with UAE shoppers, especially for higher-value baskets. If your average order is small, they can wait for version two. The Oxedge guide to Tabby, Tamara and Apple Pay for UAE online stores explains how these options are set up.
- Cash on delivery or pay at the venue. Still expected in some sectors. If you offer it, plan how staff will mark payments as received in the admin panel.
One rule to know early: if your app sells digital content or features used inside the app, such as subscriptions to premium content, Apple and Google generally require their own in-app purchase systems. Physical goods and real-world services, such as deliveries, bookings and appointments, normally use a regular payment gateway. Confirm which category you fall into before the payment screens are designed.
Start with the payment methods your first customers actually use; add the rest once you see demand.
Step 5: Notifications and WhatsApp without overbuilding
UAE customers are used to talking to businesses on WhatsApp, and they will expect your app to fit into that habit rather than replace it. For an MVP, the simplest pattern is usually the best:
- Push notifications for transactional messages only at launch: confirmations, reminders and status changes. Marketing campaigns can come later, once you have permission and a reason to send them.
- A WhatsApp hand-off from the help screen, an order page or a booking, which opens a chat with your team and ideally passes along an order reference. It is quick to build and solves most support needs.
Automated WhatsApp conversations, templated broadcasts and chatbots are powerful, but they are rarely MVP material. If you plan to use them in version two, the Oxedge article on the WhatsApp Business API in the UAE is a useful starting point.
Step 6: The admin panel is part of the product
The admin panel is the screen your team will use every day, and it is often scoped last and squeezed hardest. For version one, it needs to let staff do the jobs the app creates: see and update orders or bookings, manage the catalogue or schedule, look up a customer, issue a refund or cancellation, and edit the key text and banners in both languages. Reporting can start as a simple export. Fine-grained staff roles, approval workflows and custom dashboards can follow once you know how the team actually works.
A quick test: walk through a bad day (a failed payment, a changed booking, a late delivery). If staff need a developer to handle any of it, the panel is under-scoped.
Step 7: Plan App Store and Google Play submission early
Store submission is not a formality at the end. Several requirements affect what you build, so put them into the scope from the beginning:
- Developer accounts. Open them early in your company's name. Apple asks organisations for a D-U-N-S number, and verification can take time, so start before development finishes.
- Account deletion. If users can create an account, both stores expect a clear way to delete it from inside the app.
- Login options. If you offer Google or Facebook sign-in on iOS, Apple's guidelines expect an equivalent privacy-focused option, and Sign in with Apple is the usual way to meet that.
- Privacy declarations. Both stores ask you to declare what data the app collects and why. Your answers must match what the app and its third-party tools really do.
- Testing tracks. Use TestFlight on iOS and internal or closed testing on Google Play before release. Be aware that newer personal Google Play accounts must run a closed test with real testers before publishing, another reason to use an organisation account.
- Store listings. Screenshots, descriptions and a support URL in each language you launch in, plus a reviewer login if parts of the app sit behind sign-in.
Step 8: Test the journey, not just the screens
For an MVP, testing should focus on whether real people can finish the core journey on real phones. That means a mix of iPhones and popular Android models, slow connections, both languages if you launch bilingual, and real UAE data: +971 numbers, Arabic names, local addresses and area names, and AED amounts. Run the full payment flow, including failed and cancelled payments, then give the app to a handful of people outside the project and watch where they hesitate.
What drives the budget and the timeline
The size of an MVP is not measured in screens. These factors move the budget and schedule most:
- Whether a back end already exists. An app on top of an existing system is a very different project from one that needs its own database, APIs and admin panel.
- Platforms and technology. Native iOS and Android, or one cross-platform codebase such as Flutter.
- Payments and integrations. Each gateway, CRM, ERP or booking system the app talks to is its own piece of work.
- Languages. A properly designed bilingual app takes more design and testing time than a single-language one.
For realistic ranges and the factors behind a quote, see the Oxedge guide on what mobile app development costs in Dubai. On its service page, Oxedge notes that an app on a back end you already run typically takes 8 to 16 weeks, that a new app with its own back end takes longer, and that every app is quoted after a short discovery call with a written scope, price and timeline. App store fees, hosting and ongoing care sit on top of the build, so include them in the plan.
A simple WhatsApp hand-off often covers support at launch; automation can follow in version two.
After launch: let evidence write version two
The point of a tight MVP is to learn quickly. In the first weeks after launch, watch three things: where people drop out of the core journey, what they ask your team on WhatsApp and by phone, and what they say in store reviews. Those sources should fill most of the version-two column; features nobody asks for can stay in "Not now".
How Oxedge approaches the first version
The process described at oxedge.com/mobile-app-development-dubai follows similar logic. It starts with a short discovery: who will use the app, the three or four tasks they must complete quickly, and how the app connects to the business. That becomes user flows, a clickable prototype and screens in English and Arabic, tested with real users before code is written, with payments, push notifications and WhatsApp hand-off planned in from the start and analytics and crash reporting from day one. Arabic-speaking readers can read the Arabic version of the service page.
Frequently asked questions
How many features should an MVP have?
There is no right number. An MVP should include everything needed for one core journey to work from start to finish, plus the basics that build trust: secure login, payment, confirmations, support and account deletion. If a feature does not serve that journey, it can usually wait.
Should an MVP launch on both iOS and Android?
In the UAE, both platforms are widely used, so most consumer apps launch on both. A cross-platform framework such as Flutter makes this more practical for a first version. If your audience is clearly concentrated on one platform, launching there first is a valid choice.
Can we launch in English and add Arabic in version two?
Yes, if your first users are mainly English speakers. But build the app so Arabic can be added without redesigning it: no hard-coded text, direction-aware layouts and a design system checked in right-to-left. Adding Arabic to an app that was not prepared for it is expensive.
Bringing it together
A good MVP is a focused bet: one journey, done properly, for one group of users, with the foundations in place so that growth does not mean starting again. Write the journey down, sort features honestly, protect the decisions that are expensive to change, and let real customers tell you what version two should be.
Published by Oxedge, a digital agency in Dubai — oxedge.com.



Top comments (0)