E-commerce Mobile App Without Coding: Build, Publish and Grow From Your Dashboard

In the Gulf, shopping happens on the phone. Shoppers in Riyadh, Dubai and Kuwait browse on Instagram and TikTok, ask questions on WhatsApp and pay with Apple Pay, Mada or instalments, all from the same device. A mobile website covers the first order. An e-commerce mobile app is what turns that buyer into a regular: the store sits on the home screen, login is remembered, the cart is one tap away, and you can reach the customer with a push notification instead of paying for another ad. The old obstacle was cost: a native app meant an agency, months of development and a second codebase to maintain. This guide explains what a store app actually needs, what you can now do without writing code, and how the MobileApp builder on Commera handles design, build, publishing and notifications from the store dashboard.

When does a store need an e-commerce mobile app?

Not every store does. An app pays off when you have customers who come back, because its value is in the second, fifth and twentieth order. It usually makes sense when:

• You sell consumables that are reordered: supermarket and grocery, coffee, supplements, baby care, perfume, cosmetics.
• You run frequent drops, flash sales or seasonal campaigns (Ramadan, White Friday, back to school, National Day) and want a channel you control.
• A growing share of your revenue already comes from returning customers.
• You run loyalty points, a customer wallet or a paid membership and want customers to see their balance every time they open their phone.
• Customer service is flooded with "where is my order?" messages that automatic notifications could answer.

If most of your buyers order once a year, invest first in your website, SEO and abandoned-cart recovery; an app can wait.

What "without coding" really means

No-code app builders differ widely. Some wrap your website in an app shell, which looks and feels like a website. Others give you a real app connected to your store's data. With Commera's store mobile app plugin, the app is connected directly to your store: the same products, prices, orders, customers and payment methods. You design the home screen, categories, product page, cart, checkout and the "my account" area from the dashboard, with a live phone-shaped preview, and you build the app files from the same place.

The important detail: the design is fetched from your store when the app runs. When you publish a change to colours, sections or pages, it reaches the app without building a new version. A rebuild is only needed when you change the app name, icon, package ID, splash-screen colour, Google Maps key or default language.

Designing the app: home screen, pages and identity

A home screen you arrange yourself

The home screen is built from ready sections that you order and configure:

• A header with your logo, delivery address and delivery time, plus the search bar.
• A banner slider, taken from your store's slides or from banners you choose.
• Circular and square category tiles, all categories grouped, banner grids, a banner strip and single banners.
• Product sliders and grids filled from best sellers, newest, offers, a category, a brand or products you pick by hand.
• Brands, spacing blocks and an invite-a-friend card.

Each section can have a start and end date, and an audience: everyone, visitors only, signed-in customers or premium members. You can prepare a White Friday block in advance and let it appear and disappear on its own. You work on a draft, preview it, and publish when ready, and you can always return to the default design.

Brand identity that does not break

You choose colours, one of ten fonts that support Arabic and English, corner rounding and text size, plus three design styles (Soft, Bold and Calm), and you can give each group of pages its own style. Shades and a readable text colour are derived from your colours automatically, so the design holds whatever you change. Dark mode is optional: off, chosen by the customer, or following the device, with a separate logo for dark mode if you want one.

Product, cart, checkout and "my account"

Every element has a switch: on product cards (featured badge, old price, add button, lines of title, image ratio), on the product page (share, brand, description, specifications, similar products), in the cart (address, share, recommendations) and at checkout (map, a different recipient, notes, coupons, savings). The bottom tab bar holds up to five tabs with your own names and icons, including a tab for a specific category, such as a Ramadan offers section. The "my account" screen is assembled from groups and rows: orders, addresses, payment history, favourites, notifications, coupons, contact us, FAQs, terms and privacy.

The shopping experience inside the app

The app is where repeat customers spend their time, so the details matter:

• Search with live suggestions, highlighted links and smart lists before the customer types, and trending terms taken from real searches or written by you. A "search by list" mode lets a shopper paste a whole shopping list, line by line, and find a match for each line, which suits grocery and pharmacy-style catalogues.
• Sign-in with Google or Apple in one tap (verified on the server), email and password, or a one-time code if you enable it. Guest checkout is available, and a guest's cart moves to their account if they sign up later.
• In-app payment with the delivery address on a map, shipping choice, coupon, loyalty points and wallet balance at checkout. The product page can show Tamara and Taly instalments.
• Orders on a timeline with shipment tracking; customers can cancel a pending order, reorder an old one in one tap and review their payment history.
• Your plugins appear in the app. Reviews, bought-together, quantity offers, campaign badges and loyalty points show as ready blocks. Wallet, premium membership, loyalty, referrals and coupons get their own screens when those plugins are active. If a plugin has a problem, it is logged and skipped; it does not stop the app.
• Deep links: when someone opens a link to a product, category, brand or page from your store and has the app installed, it opens on the right screen. Your store serves the verification files Android and iOS require.

Building and publishing on Google Play and the App Store

Android: APK and signed AAB from the dashboard

On the build page you enter the app name in Arabic and English, the package ID, version number, icon, splash colour and default language, and optionally a Google Maps key to show the map in the app. You build an APK for testing and an AAB for the store. The build runs in the background; you follow its status and log, download the files, and keep a history of recent builds.

For signing, the platform can generate the key for you, or you can upload your existing key if your app is already published. The key is stored encrypted, you can download a copy with your password, and you can see its SHA-1 and SHA-256 fingerprints, which app links and Firebase require. Keep a copy somewhere safe: without it you cannot update your app on Google Play.

To publish, you connect a Google Play service account and choose the track (internal, closed or production), the release status (draft or completed) and release notes in Arabic and English. You publish the AAB with a button, or have it uploaded automatically after every successful build.

iOS: a ready project in your brand

For iPhone, the plugin prepares an iOS project with your store name, icon and bundle ID, together with a ready Codemagic configuration. The iOS build runs on a Mac or on a cloud build service such as Codemagic and is uploaded to TestFlight from there; it is not built from the dashboard. Plan for this step with your developer or with our team.

Developer accounts you will need

Publishing requires your own accounts with the stores. As of 2026, Google Play charges a one-time registration fee of 25 US dollars and the Apple Developer Program costs 99 US dollars a year; check the official sites for current terms. Opening these accounts is done on Google's and Apple's sites, following written steps, and company accounts may ask for business verification documents, so start early.

Push notifications: the reason the app pays for itself

The app notifications plugin sends notifications from your own Firebase project, so the account and the data stay under your control. You upload the service-account file (stored encrypted), enter the Firebase app details for Android, iOS and the web, and send a test notification to your own devices before going live. The plugin does not charge per notification; sending runs on your Firebase account under Google's terms.

Automatic notifications

• Order placed, being prepared, out for delivery, delivered, cancelled or returned, and any other status change. Each type has its own switch and text, and tapping it opens the order in the app.
• Wallet balance added, referral reward credited, premium membership activated or about to expire (three days before, checked daily), and back-in-stock alerts for products the customer subscribed to.
• Editable title and text in Arabic and English, with variables such as the customer's name, order number, amount, status, date or product name. Customers receive the language of their device.

Campaigns to segments

You write a title and text, add an image of up to 1 MB, and choose the audience: all app users, customers who have ordered, premium members, customers who have not ordered for a number of days you set, or a customer segment if you use the segments plugin. You see how many people will receive it before you send. The tap can open a product, a category, an external link or a screen inside the app (home, cart, wallet, orders). Send now or schedule by the store's time zone, then follow status, reach and failures in the campaign log. Sending runs in batches, resumes if interrupted, and removes invalid devices automatically. Customers who turned notifications off are skipped. With web credentials and a VAPID certificate, the same campaigns can also reach signed-in customers in the browser on your website.

For how to combine push with WhatsApp and email to bring back hesitant buyers, see our guide to abandoned cart recovery, and for building the audiences themselves, our article on customer segmentation.

After launch: updates, ratings and crash reports

For Android and iOS separately, you set the minimum allowed build number (anything older is asked to update), the latest build and the store link, and choose between a forced update and an optional prompt that the customer can close, with your own message in both languages. You can also ask for an app rating after a number of orders and days that you define. None of this needs a new build. A crash dashboard groups similar crashes and counts them, filters by status, platform, version and fatal crashes, and reopens a crash automatically if it returns in a newer version. Usage events flow into the analytics plugin, and a page lists every API endpoint of your store with an OpenAPI export for developers.

Website-only, wrapper app or connected app: a comparison

Good to know before you start

• The Android build and Google Play publishing run from the dashboard, and the iOS build is produced on a Mac or a cloud build service.
• You need your own Google Play and Apple developer accounts.
• If you sell in several countries with the Markets plugin, the app uses the store's base settings while markets run on the website. Our guide to a multi-country online store explains the markets layer.

Frequently asked questions

Do I need to know how to code?

No. Design, build and Android publishing all happen from the dashboard. The initial set-up of your Google Play and Apple accounts is done on their sites following written steps.

If I change the design, do I have to rebuild the app?

No. Colours, sections and pages are published and reach the app automatically. A rebuild is needed only for the app name, icon, package ID, splash colour, maps key or default language.

Does the app work on iPhone?

Yes. The plugin prepares an iOS project in your brand, which is built on a Mac or a cloud build service and uploaded through TestFlight.

Can customers sign in with Google or Apple?

Yes. If the social login plugin is active, the app shows the buttons automatically for whichever providers you enabled.

Do I pay for each push notification?

The plugin itself does not charge per notification. Notifications are sent from your own Firebase account under Google's terms.

Can I send a notification to one specific customer?

Campaigns go to an audience (all, customers, premium, inactive or a segment). Individual customers receive the automatic notifications for their own orders, wallet and membership.

Launch your store app with S-Plus

S-Plus has designed and marketed online stores for Gulf brands for more than fifteen years, and we built Commera's app builder for stores that want their own app without a separate development project. We can set up your developer accounts, design the screens, prepare the iOS build and plan your first push campaigns alongside our social media management team. See the full feature list on the Commera mobile app page, then contact us to plan your app and get a quote.