Your customizations come with you
Modules, price rules and theme changes reach the app when you deploy them to the storefront.
For Magento and Adobe Commerce
The app loads your live storefront, so group prices, checkout extensions and store views keep working. Nothing to install on your server. Preview it free on your phone.
Before you paste: Enter the production storefront URL; VPNs, IP allowlists and maintenance mode block the preview.
See how it worksComes with you
Modules, price rules and theme changes reach the app when you deploy them to the storefront.
Point native tabs at order history, search, cart and account. On Adobe Commerce B2B, Quick Order and requisition lists work too.
Send a title, text, image and link from your own Firebase project. Sent to everyone who opted in.
Your developer can pass the mini cart count to the tab with our JS SDK.
We fill in your name and icon. AI sorts your links into a header, side menu and tabs, and writes the script that hides your site’s own header and pop-ups. You adjust the rest.
Scan a code and use your real site as an app, before you pay.
You may be asked to install our preview app first.
We build in the cloud, so you need no Mac or Xcode. iOS lands in TestFlight in your Apple account; Android downloads as an AAB or APK. You submit for review from your own accounts.
App extensions and custom builds read your store through a connector or the API, so each customization is rebuilt on the app side.
You need barcode scanning, offline ordering for field reps, push triggered by orders or segments, or a team to handle store submission.
The app shows your site in a WebView, which behaves like a mobile browser with a few differences worth checking.
Prices and catalog visibility are set on your server for each account, so the app shows the same.
Try it: Open the app as retail and wholesale; compare prices.
Magento decides prices and catalog visibility on the server for each customer, so a wholesale buyer sees wholesale prices in the app as on the site. Adobe Commerce B2B pages such as company accounts, Quick Order, requisition lists and negotiable quotes are ordinary storefront pages you can open from a tab or the menu. Two things to test on both phones: the Quick Order CSV upload and downloading an invoice PDF.
Filters, search and product options are your storefront pages and load as on mobile web.
Try it: Search by SKU, filter, open a product, swipe back.
On a large category, apply two or three layered navigation filters, open a product and confirm that swipe-back returns you to the filtered list. Then add a configurable product, a bundle and one with custom options. The app is as fast as your mobile storefront, so a slow category page will be slow here too.
Card fields rarely differ; 3-D Secure and redirect methods must return to the success page.
Try it: Pay with 3-D Secure through to the success page.
Checkout is your own Magento checkout with your shipping methods, tax rules and payment extensions. Card fields from gateways such as Braintree, Adyen or Stripe are web forms. Spend your testing time on methods that leave the page: a 3-D Secure challenge, PayPal, pay-later providers and bank redirects all have to return to your success page inside the app. Apple Pay and Google Pay depend on what the embedded browser exposes, so test those in the preview too.
Magento signs idle customers out after an hour by default; Persistent Shopping Cart keeps only the cart.
Try it: Reopen the app after an hour; check sign-in and cart.
Magento’s default cookie lifetime is 3,600 seconds, so a customer idle for an hour is signed out, which feels like a fault in an app. The setting is under Stores > Configuration > General > Web > Default Cookie Settings. A longer lifetime is a security trade-off to agree with your developer. Also watch the mini cart count after an add to cart and after checkout; Magento fills it in from the browser’s local storage.
Email sign-in is dependable; Google sign-in can be blocked in apps, so test social buttons.
Try it: Tap every social and SSO button and finish signing in.
Email and password sign-in is the dependable path. Storefront reCAPTCHA normally loads as it does on mobile web. Social login extensions run on other domains, and Google can block its sign-in screen inside in-app browsers, so a “Sign in with Google” button can fail in the app while working in Chrome. Test every option you offer, and treat corporate SSO or punchout from a procurement system as outside what an app like this is for.
The app opens one store view, so pick it and keep the store switcher reachable.
Do this: Switch store view and currency from inside the app.
The app opens the URL you give it. If each store view has its own domain or a store code in the path, choose the one your app customers should land on and keep the store and currency switchers reachable. If an extension redirects visitors by location, check where a customer abroad arrives and that tabs still point at pages in that store view.
These are a starting point for your free preview, not a claim that every site setup or integration has been tested. Not for apps that need Bluetooth, AR, heavy offline use or background processing.
Planning the build?Setup walkthroughReadiness checklist
Website changes show up in the app without a rebuild. No subscription, and the price doesn’t change as your app gains users.
Paid to Apple and Google
Later rebuilds, such as a new icon, are included.
Yes, you can turn a Magento store into an iOS and Android app with SiteTo.App without rebuilding it. The app loads your live Magento store, adds your branding and menus, and costs $29 for Android, $79 for iOS or $99 for both, paid once per platform. Apple and Google developer accounts are separate.
Yes. SiteTo.App works from your public storefront URL, so the edition and hosting do not matter. Luma, Hyvä and headless storefronts load the same way. The app is as fast as your mobile storefront, so fix a slow theme first.
No. Nothing is installed on your Magento server and SiteTo.App does not use your REST or GraphQL API. The optional JavaScript SDK, used for extras like a cart badge on a tab, is a small script a developer adds to your theme.
Customers see the latest version of your website when they open or refresh the app, so ordinary content, product and page updates do not need a new app build. A new app icon, app name or launch screen needs a new build.
Apple decides, so nobody can guarantee it. Apple can reject apps that add nothing beyond a website (Guideline 4.2), so plan for real app features such as native navigation and push, and test your key journeys in the preview first.
Yes. Paste your URL and open the preview on your own phone. You don’t need an account or a card to preview, though you may be asked to install our preview app first. You only pay when you choose a build.
Paste your store URL, sign in as a customer on your phone and check your prices.
No account or card to preview.