Most of the "native app for ecommerce" market is a Shopify story told with multi-platform words.
Open a builder comparison. Count how many hero cases run on Shopify only. Then look at your stack. WooCommerce with a plugin pile. PrestaShop multi-store. Magento with customer groups and messy configurables. Or two backends because the brand grew by acquisition. The screenshot stack does not care.
If that is you, a Shopify-first DIY tool is not a bargain. It is a detour. You will either force a platform migration nobody asked for, or stay on a mobile-responsive site while competitors own the home screen.
This is for ecommerce directors and brand owners who need a real native path on Shopify, WooCommerce, PrestaShop, Magento, or more than one of those at once. Not a feature laundry list. The jobs the app must do, why website-to-app wrappers plateau, what integration should look like by platform, and when a fully managed subscription is the rational route.
At ConvertNative we ship and run native iOS and Android apps on subscription across those stacks. Design, deploy, sync, push, optimisation. Same commerce jobs. Different backends.
The Shopify-only builder trap
Builders in the Tapcart, Shopney, and Plobal lane are sharp at one thing. Ship a themed app fast when your catalog lives in Shopify and your exceptions are light.
That is a real product. It is not a universal answer.
Three traps show up the week after the demo:
Stack lock-in marketed as "ecommerce." The landing page says ecommerce. The connector, theme blocks, and roadmap assume Shopify Admin patterns. Woo, Presta, and Magento teams get a polite no, a thin export hack, or a "coming soon" that never owns their edge cases.
Multi-store reality ignored. Brands that run Shopify plus a regional Presta shop, or Magento B2B beside a DTC Shopify front, cannot bolt one builder onto the P&L and call mobile done.
False choice framed as speed. "App this month or stay stuck" only works if your catalog fits their lane. If it does not, speed is fictional. You spend the month learning you picked the wrong operating model.
If you are pure Shopify with a standard catalog and a named owner for the dashboard, a builder can still be a fit. We cover that decision in fully managed vs DIY ecommerce app builders and the broader path choice in build, buy a builder, or go managed. This piece is for everyone the Shopify-only lane quietly leaves behind.
Jobs a native app must do (backend does not care)
Shoppers do not buy "a Shopify integration." They buy a loop that feels instant on a phone.
Day one, every serious native app for ecommerce has to clear the same bar:
Live catalog. Collections, variants, stock, prices, media. Wrong inventory kills trust faster than a plain UI.
Cart and checkout shoppers already understand. Coupons, shipping rules, taxes, payment methods, pickup or subscription quirks if you sell that way today.
Account without password theatre. Returning buyers land in a session that knows them. Order history and addresses travel. Forced login mid-funnel still burns mobile orders.
Push that earns the opt-in. Cart recovery, back-in-stock, drops, order updates, segmented win-back. Deep links into product or cart, not a dead home feed. Cadence detail lives in our push notification strategies guide.
Analytics that change next week. Activation, funnel steps, push-attributed revenue, early LTV. Install vanity is not a roadmap. See ecommerce app analytics that actually change weekly decisions.
Those five jobs are platform-agnostic. How you wire them is not. That is where multi-platform brands get sold a demo and inherit a science project.
Why website-to-app wrappers plateau on conversion
When a vendor cannot speak Magento or Presta fluently, the fallback is familiar. Wrap the mobile site. Ship a shell. Call it an app.
You get a store listing. You often keep the same friction that already hurts responsive CVR.
Full page reloads and script weight travel with you
Login and checkout still feel like a browser once you scratch the chrome
Home-screen presence without native navigation patterns fails the habit test
Push may exist, but deep product state and session quality stay weak
Wrappers help when the job is packaging stable content. They plateau when the job is conversion. Industry baselines stay blunt: desktop often near 5.4% CVR while mobile web lands around 1.8%. Packaging that gap inside a WebView does not close it. For the full math on responsive vs native, read why your mobile site converts at a fraction of a native app.
If a sales deck leans hard on "we turn any URL into an app" and soft on catalog sync rules, assume the conversion ceiling follows your current mobile web.
Integration expectations by platform
Good discovery starts with how you already sell, not with a theme picker.
Shopify
Cleanest connector story in the market. Admin API, webhooks, markets, and a huge app ecosystem. Still not a flip switch. Sacred apps (subscriptions, loyalty, bundles, reviews) need an explicit in-app, webview, or replace decision before build. Checkout constraints from Apple and Google need a plan, not a surprise in review week. Deeper notes: Shopify mobile app needs in 2026.
WooCommerce
Flexibility is the feature and the risk. Plugin stacks break theme parity myths fast. Variable products, custom fields, multi-currency plugins, membership gates. A native app has to integrate against the shop you run, not a default Woo demo. If a vendor only scrapes the storefront HTML, walk. Detail: when a Woo plugin theme is not enough.
PrestaShop
Strong in multi-store and EU retail patterns. Combinations, tax rules, carrier logic, and module debt all show up in mobile. Brands often hit a responsive ceiling while desktop merchandising stays rich. The app path has to respect multi-shop catalog boundaries instead of flattening everything into one naive feed. Detail: PrestaShop path off the responsive ceiling.
Magento (Adobe Commerce and Open Source)
Configurable products, shared catalogs, customer-specific pricing, MSI inventory. This is where thin builders choke. A native app that cannot honour group pricing or complex options becomes a support ticket machine. Plan API surfaces and which B2B flows stay on web. Detail: Magento guide for brands that outgrew the storefront.
Multi-stack and multi-brand
One icon can still serve one brand experience while backends differ by region or channel. What you need in writing:
Which catalog is system of record per market
How promos and stock conflict get resolved
Whether accounts are unified or split
Which stack owns checkout for each shopper segment
If a vendor goes quiet here, they have not done multi-platform work. They have done single-connector work twice on a slide.
What "good" looks like when the stack is not a demo shop
Channel quality shows up in commercial numbers, not star ratings alone. Across ConvertNative programs we see about +34% conversion versus the responsive baseline, roughly x2.8 LTV in-app (about $85 vs $30 on mobile web cohorts), around -20% reactivation cost when push carries weight email cannot, and time spent up to x10 in retained sessions. Push open rates near 45% (about 7x typical email) only matter if catalog and checkout sync hold under real rules.
Scale reference: Notino at €1.2B revenue and 7M downloads. Your catalog is not Notino. The lesson still holds. Native pays when browse, account, checkout, and messaging stay maintained after launch day, on the backend you already run.
For the LTV mechanics operators can track weekly, keep how native apps lift customer lifetime value next to this piece. CRM leads should also hold push open rates vs email.
Managed path when you run one stack or several
Custom build can clear multi-platform complexity. It also drops a permanent mobile org on your payroll. DIY builders optimise for Shopify speed. Wrappers optimise for publish optics.
Fully managed on subscription is the middle that multi-platform operators usually need:
Native iOS and Android, not a thin browser shell
Design and UX for app behaviour, not a squeezed desktop IA
Integration against Shopify, WooCommerce, PrestaShop, or Magento as they actually run
Store listing, rejection cycles, OS churn handled as normal work
Push and conversion optimisation after go-live, not a goodbye email at acceptance
Production in about 4–6 weeks when scope stays honest
Subscription commercial shape. No multi-year project theatre to start
You keep merchandising, offers, and brand rules. You stop pretending two app stores and four possible backends are a side quest for the ecommerce director.
Who should still wait or stay web-only: mobile traffic is small, or basic site speed and payment reliability are still on fire. Move when mobile already dominates sessions, under-indexes on revenue, and every builder conversation dies the moment you say "we are not only on Shopify."
A simple filter for this week
Write one page before another demo.
Stack map. List every backend that takes money today. Mark which one sales demos keep ignoring.
Exception list. Configurables, customer groups, multi-store, subscriptions, pickup, sacred plugins.
Owner test. Name the human who will run release QA and push quality if you buy DIY. If the name is blank, do not buy DIY.
Ceiling test. Ask the vendor where conversion lifts come from when the mobile site is already optimised. If the answer is only "we put it in the store," you are buying a wrapper.
Exit test. Store accounts, data, and what happens if you leave in month nine.
Anyone who dodges ownership and integration detail is selling a template lane. Multi-platform brands cannot afford template lanes dressed up as strategy.
Pick a path that matches the backends you run
Shopify-only builders will keep winning demos on Shopify-only catalogs. That is fine. It is not your path if Woo, Presta, Magento, or multi-store reality pays the bills.
Insist on native jobs done against the stack you have. Reject wrappers that freeze today's mobile CVR inside an icon. Prefer a managed partner when you need iOS and Android in production without staffing a studio.
If you want a straight read on fit, bring mobile share of traffic, mobile CVR vs desktop, and the messy integration list. We will say whether a native app is worth a slot this quarter, and how a multi-platform managed route would look on your backends.
Get a free mobile app audit. Straight scope. No Shopify-only theatre.