A restaurant owner in Sharjah gets a call from an agency: “Your competitors have apps. You need one.” A week later a furniture showroom in Dubai hears the same pitch. For the restaurant, an app may earn its place on customers’ phones; for the showroom, it would be an icon opened once and deleted. We build apps, and we also tell clients when not to. This article settles when a mobile app for online store customers pays off, when a better mobile site is the smarter spend, which kind of app to build, what it costs to run, and what to agree before a deposit.
Quick Answer
Your store needs a mobile app when customers come back often and the app lets them do something your mobile site cannot do as well: reorder in 2 taps, track an order, book a slot, collect loyalty points, receive notifications. It does not need one when people buy from you once or twice a year, or when the app would only wrap your website, which Apple’s review guidelines say may not be accepted. Then spend the money on the mobile site and checkout. If an app makes sense, choose native, cross-platform or a PWA, publish it under your company’s own developer accounts, and agree scope, milestones and code ownership in writing before any deposit. Our mobile app development team builds all three types.
The Question to Ask First
How often does a customer buy from you? And what would they do in an app that they cannot do on your mobile site?
If the answers are “once a year” and “nothing”, stop here. An app has to be found, downloaded and kept on a phone among dozens of others; in our experience it earns that place only when the customer has a reason to open it again next week.
The app does not replace the website: new customers still arrive on your site from Google, ads and social posts, and the app serves the ones who already know you. So the site comes first either way; if it is slow or hard to buy from on a phone, fixing that through website optimisation helps every customer, including the ones an app would never reach.
When a Mobile App Pays Off for an Online Store, and When It Doesn’t
Native, Cross-Platform or PWA
Native. Separate apps for iOS and Android: the fullest access to device features, at the highest effort, with 2 codebases to build, test and update.
Cross-platform (Flutter or React Native). One codebase builds both apps. For a typical store app (catalogue, cart, account, orders, notifications) this is our usual recommendation: one codebase to maintain, both stores covered.
PWA. A progressive web app is your website built to install on the home screen. No store review, no store fee, one codebase with the site. Since iOS and iPadOS 16.4, a web app added to the Home Screen can receive web push notifications, provided the permission request follows a direct user action such as tapping a subscribe button. The limits: customers add it themselves, and it is not in the App Store.
Whichever route you take, an app must be more than your website in a frame. Apple’s App Store Review Guidelines, under 4.2 Minimum Functionality, say an app should offer features, content and UI that take it beyond a repackaged website. Rule 4.2.6 adds that apps made from a commercialised template or app generation service will be rejected unless the provider of the app’s content submits them. And under 3.1.3(e), physical goods and services consumed outside the app are paid with methods other than in-app purchase, such as Apple Pay or card entry, so your existing e-commerce payment setup stays in place.
Design the screens before anyone writes code; that is UI/UX work. Recommendations or a chatbot, through our AI solutions, can come once the basics are used.
Running Costs People Forget
Developer accounts. The Apple Developer Program is a US$99 annual membership. Google Play charges a US$25 one-time registration fee.
Yearly platform updates. Since 31 August 2026, Google Play has required new apps and app updates to target Android 16 (API level 36), and the requirement rises with each Android version; existing apps that fall behind stop being available to new users on newer devices. In our experience iOS apps also need work after major releases. An app is a yearly budget line, not a one-off purchase.
Store review and upkeep. Apple’s guidelines say every App Store app is reviewed, and an app that is no longer actively supported will be removed. Plan releases before Ramadan or a sale with margin.
The backend. The app reads products, prices, stock and orders from the same store backend as your website, and like a checkout page, those requests are live and cannot simply be cached. If the store is already slow, the app will be slow too, so fix the hosting first; our guide to the best hosting for a WooCommerce website explains what a busy store needs from its server. Still choosing a platform? Our comparison of Shopify and WooCommerce for a UAE store covers the costs of each.
Analytics, notifications and reviews. Someone decides which notifications are worth sending and answers store reviews in Arabic and English.
What to Agree Before You Pay a Deposit
Written scope and screens. Every screen and what it does, with approved wireframes.
Milestones with acceptance criteria. Each payment tied to something you can test on your own phone: “a returning customer can repeat the last order in 2 taps, on iOS and Android”.
Source code. In a repository your company owns, or handed over at each milestone.
Store accounts in your company’s name. When an organisation enrols in the Apple Developer Program, its legal entity name is listed as the seller, and Apple asks for its D-U-N-S Number; members can then be added to the team. Google Play offers an Organization account type. Publish under your own accounts and add the developer as a team member, never the reverse.
Maintenance after launch. Who handles OS updates and bugs, at what monthly cost.
Refund terms. Read any developer’s refund terms before the deposit. Ours are published: our refund policy states that development services, including mobile apps, are non-refundable once initiated, and that advance and milestone payments are not refunded. That is why the written scope, milestones and acceptance criteria above matter: they define what each payment buys.
Our usual timeline is 4–6 weeks for a simple app and 2–4 months for a complex project.
From Our Work
A restaurant with weekly regulars. A restaurant client’s customers ordered from it every week. Here an app made sense: saved orders that a customer can repeat without building the basket again, and order-status notifications. The customer had a reason to open the app every week, which is the test from the start of this article.
A furniture store that did not need one. A furniture store asked us for an app. Its customers buy once every few years, and an app earns its place only when there is a reason to open it often. We advised improving the mobile site and the checkout instead, which every customer uses, new or returning.
An app in someone else’s account. A business came to us whose previous developer had published its app under the developer’s own store account. Updates to an app go through the account that holds it, which made later updates difficult. For every app we build now, publishing under the client’s own developer account is a condition.
Frequently Asked Questions
Does my online store need a mobile app?
Only if customers buy often and the app gives them something the mobile site cannot: fast reordering, order tracking, bookings, loyalty or notifications. If most customers buy once or twice a year, a faster mobile site and a simpler checkout will do more for the same budget.
How much does it cost to publish an app on the App Store and Google Play?
The store fees are US$99 a year for the Apple Developer Program and a one-time US$25 registration fee for Google Play. Development and maintenance are separate and depend on the scope; ask for a quote only after the screens and features are written down.
Can I turn my website into an app?
Wrapping the website in an app shell is the case Apple’s guideline 4.2 describes: an app should be more than a repackaged website, or it may not be accepted. If the site is good, a PWA that installs on the home screen is often the honest version of this idea.
Is a PWA as good as a native app?
For catalogues, bookings and reorders, a PWA can do much of the job: it installs on the home screen and, on iOS and iPadOS 16.4 or later, receives push notifications once added. It is not listed in the App Store, and native apps keep fuller access to device features.
How long does it take to build an app for my store?
Our usual timeline is 4–6 weeks for a simple app and 2–4 months for a complex project. Store review, content and your own testing at each milestone add time, so plan the launch date with margin, especially before Ramadan, Eid or a planned sale.
Sources
- App Store Review Guidelines — Apple Developer (accessed 2026-10-03)
- Apple Developer Program — Apple Developer (accessed 2026-10-03)
- Enrollment — Apple Developer Support (accessed 2026-10-03)
- Get started with Play Console — Play Console Help (accessed 2026-10-03)
- Target API level requirements for Google Play apps — Play Console Help (accessed 2026-10-03)
- Web Push for Web Apps on iOS and iPadOS — WebKit blog (accessed 2026-10-03)
Where We Are
BIGBANG ITS has planned and run technology for UAE businesses since 2003, headquartered at the Sharjah Research, Technology and Innovation Park with a branch in Business Bay, Dubai. Support runs 24/7 and the office is open Saturday to Thursday, 09:00–18:00 Gulf time. For an honest answer on whether your business needs an app, contact us or call +971 4 378 2255.
Talk to us directly — we usually reply within minutes during business hours.
