FAQ

App questions
answered

19 answers on apps, PWAs, loyalty, memberships, push notifications and payments for online stores. Each answer stands on its own, so jump to whichever you need.

Mobile apps for ecommerce

Not every store does. An app makes sense when customers come back often, or when you can offer something the website cannot, such as rewards, member pricing or order alerts. If most visitors arrive once from search, a fast mobile website or a PWA may be the better first step.

A mobile website runs in the browser and is found through search. An app is installed from an app store, can send push notifications, uses phone features such as Face ID and the camera, and sits on the customer's home screen. A PWA sits between the two.

MobileCart builds custom shopping apps for online stores: iOS, Android and progressive web apps, with checkout, loyalty and rewards, memberships, push notifications and the integrations behind them. We build for your store. We do not sell a one-size template app.

We connect apps to Shopify, WooCommerce, BigCommerce, Magento, and custom or headless backends. If you use something else, we check whether it has the interfaces the app needs before we scope the work.

No. Your website stays your main source of search traffic and new customers. The app serves customers who already know you and want a faster way to shop and use rewards.

Process, cost and timing

The cost depends on the platforms, the features, the number of integrations and the design work, so we do not publish a single price. After the planner or a call we send a written scope with a price for the first release, and we explain what would change it.

A simple PWA takes much less time than a full iOS and Android app with loyalty, memberships and checkout. We give a timeline in the proposal, based on your scope, and tell you which parts are most likely to slip, such as app store review.

You do. The app is published under your developer accounts, and the source code and designs are handed over under the agreement. We do not hold the app or the listing.

A store we can connect to, your brand assets, and someone who can make decisions about the features. We guide you through the developer accounts and help you prepare the rest.

Yes. After launch we fix defects, update the app for new iOS and Android versions, and can plan new features. Apps need ongoing updates because phone operating systems change every year.

Native, cross-platform and PWA

Cross-platform tools such as React Native and Flutter share one codebase between iOS and Android and suit most shopping apps. Native builds suit apps that rely heavily on advanced phone features. We recommend one after seeing your feature list and say why.

It can be, especially at the start. A PWA can be installed, work offline for visited pages and send push on supported devices. It cannot use every phone feature and does not appear in the app stores. We help you judge from your customer mix.

We set a minimum supported OS version from your analytics, load images efficiently and test on older devices. We cannot make every old phone fast, but we make sure the app behaves well on the ones your customers use.

We follow platform accessibility guidance: screen reader labels, scalable text and enough color contrast. We test with the built-in screen readers on iOS and Android.

Loyalty, membership and push

Customers earn points on orders linked to their account, see their balance in the app and spend points at checkout. You set the rules, such as points per purchase, expiry and what returns do to points. We build them and add admin tools to review and adjust balances.

Yes. Paid tiers need recurring billing, renewal reminders and an easy way to cancel. For iOS, Apple has rules about what can be sold inside an app, so we check your plan against the current guidelines first.

The app registers the customer's phone with Apple or Google, and your backend sends messages through those services. Customers choose whether to allow them and which types to receive. We build the permission prompts, settings and sending rules.

Only to people who agreed to receive them, and with a way to turn them off. We build preference controls, frequency limits and quiet hours so campaigns do not push customers into switching notifications off.

Only what the features need, such as account details, orders, device tokens and, if you choose, analytics events. We help you fill in Apple's privacy details and Google's data safety form accurately, and your lawyer should review your privacy policy.

Question not covered?

Send it through the contact page or the app planner and we will answer it directly.

Ask us