StoreToNative – Mobile App Builder for WooCommerce
| 开发者 | storetonative |
|---|---|
| 更新时间 | 2026年10月24日 09:07 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Install this plugin and open the StoreToNative screen. Read the free Store readiness check and fix what it flags, and preview your own store as an app. No account yet, and nothing is sent anywhere.
- Start a 14-day free trial and connect your store with a pairing code. Connecting takes about a minute.
- Design your app beside a live phone preview, then build it and publish it on Google Play and the App Store under your own developer accounts.
- Store readiness check (free, no account). Fourteen checks over your own WooCommerce settings for the things that quietly break a mobile app — "Coming soon" mode left switched on, no payment method enabled, Plain permalinks, no shipping zone, a stale product price index, downloadable products that both app stores reject — each in plain language, with what it costs you and exactly which screen to fix it on. They run entirely inside WordPress, send nothing anywhere, and work before you pair.
- 1-click connect. Paste a short pairing code from your StoreToNative console. No OAuth redirect, no "approve this application" screen to trip over on security-hardened sites.
- Deep-link hosting. Serves
.well-known/apple-app-site-associationand.well-known/assetlinks.jsonfrom your store's own domain — which is what iOS Universal Links and Android App Links require, and which nothing outside your site can do for you. - Smart app-install banner. Once your app is live on the App Store or Google Play, shows shoppers browsing your storefront on that kind of phone a lightweight banner to install it (you can switch it off), plus an
apple-itunes-appmeta tag so Safari's own native banner takes over on iOS. - Shopper sign-in. Shoppers sign in to your app with the WooCommerce account they already have. Passwords are checked by WordPress itself and never reach StoreToNative. Accounts that can run your store — administrators, shop managers, editors and anyone else who can write posts — cannot sign in to the app; to try your app as a shopper, use a customer account. If you protect
wp-login.phpby its address (a hidden login URL, an IP allowlist, or server password protection), apply the same protection to/wp-json/storetonative/v1/shopper/: it is a second place your site checks passwords.
- A native catalogue — swipeable galleries with pinch-zoom, colour swatches, a full variation picker, ratings and reviews, instant search, filters and a persistent wishlist
- A design studio with a live phone preview beside every control: colours, typography, product grid, storefront presets and a drag-to-reorder home screen
- Over-the-air updates — change your theme, banners and home layout, and installed apps pick it up on their own. No rebuild, no app-store re-review
- Push notifications: order-status updates and broadcast campaigns, plus abandoned-cart recovery on the Pro plan
- Signed Android builds, with guided checklists for Google Play and App Store submission — or direct APK distribution, no Play account required
- First-class Arabic and right-to-left layouts
- Your own payment gateways, and no commission on your sales
- WooCommerce must be installed and active. This plugin does nothing without it.
- A StoreToNative account, to build and publish an app. The Store readiness check and the app preview work without one. The app itself is built and published from the StoreToNative console, a paid subscription with a free trial; this plugin is what pairs your store with it.
- HTTPS. Pairing is refused on a plain-http site.
安装:
- Upload the plugin to
/wp-content/plugins/, or install it directly from the WordPress plugin directory. - Activate the plugin through the "Plugins" screen in WordPress. WooCommerce must already be installed and active.
- Go to the new "StoreToNative" menu in your wp-admin sidebar.
- Read the Store readiness check and fix anything it flags. It works before you pair, with no account.
- When you want the app: open your StoreToNative console, generate a pairing code for this store, and enter it on the connect screen.
- Once paired, the dashboard shows your app's connection status, deep-link readiness, and the smart banner toggle.
屏幕截图:
常见问题:
How do I turn my WooCommerce store into a mobile app?
Install this plugin, start a StoreToNative free trial, and connect your store with a pairing code from the console. Then choose your colours and home screen in the design studio, build the app, and publish it under your own Google Play and Apple Developer accounts. There is a full video tour at the top of the description.
What does this plugin do for free, without an account?
It runs the Store readiness check: fourteen checks over your own WooCommerce settings for the things that quietly break a mobile app, each with what it costs you and which screen to fix it on. The check runs inside WordPress and sends nothing anywhere. You can also preview your own store as an app at https://app.storetonative.com/demo . Building and publishing the app needs a StoreToNative plan.
Can it turn any WordPress site into an app?
No. StoreToNative is made for WooCommerce stores: the app is built from your products, categories, cart and customer accounts, so WooCommerce must be installed and active. A WordPress site without a store is not supported.
Does it work with my theme and my other WooCommerce plugins?
Your app does not use your WordPress theme. It is drawn natively from your store's data, and you style it in the StoreToNative design studio. Your payment gateways keep working because checkout runs on your store's own checkout page. For other plugins, see the tested list at https://storetonative.com/supported-plugins/ before you start.
Is this a WebView wrapper?
No. Your storefront — home, catalogue, search, product pages, cart and account — is drawn natively on the phone from your store's live data. Checkout runs on your store's own checkout page inside the app, so your payment gateways work unchanged; with native checkout switched on, shoppers fill in their details in a native form and only the payment step opens your checkout.
How much does it cost?
StoreToNative is a subscription with a 14-day free trial. Plans are Starter at $29 a month, Pro at $79 and Agency at $249. StoreToNative never takes a commission on your sales. This plugin itself is free.
Do I need an Apple or Google developer account?
To publish in the App Store or Google Play, yes: your app is published under your own Apple Developer and Google Play accounts, never ours. Android apps can also be installed straight from a download link with no Google Play account at all.
Can I try it before paying?
Yes. Preview your own store as an app at https://app.storetonative.com/demo, and run this plugin's store readiness checks before you connect anything.
Do I need a StoreToNative account?
Yes, to build and publish an app. This plugin pairs your store with a StoreToNative account — it isn't a standalone app builder. The store readiness checks work without one, and the plugin's connect screen links to a free trial.
Does this send data before I connect?
No. Installing or activating this plugin makes zero network requests. The very first request it ever makes is the pairing request, and only after you've pasted a pairing code into the connect screen yourself. See "External services" above for exactly what that first request contains.
Does it work without HTTPS?
No. This plugin refuses to pair — and therefore never talks to the StoreToNative API at all — unless your store itself is served over https. That check happens locally, before any network request is made, so a plain-http site can't even attempt it.
Pairing fails with "could not confirm this site". What does that mean?
While you pair, StoreToNative makes one request back to your store, and your store did not answer it in time. The usual causes are a security plugin or firewall that blocks the WordPress REST API, or a slow host. The help page lists each cause and its fix: https://storetonative.com/docs/troubleshooting/ . The code you typed is used up, so create a new one after the fix.
What happens if I deactivate WooCommerce?
The plugin shows an admin notice explaining that WooCommerce is required and does not register any of its other functionality until WooCommerce is active again.
What happens if I uninstall the plugin?
Uninstalling removes all of this plugin's local data (pairing, settings, cache, and the WooCommerce API key it created for itself) and stops your store from syncing with your native app. It does not make any remote request — your StoreToNative console will simply notice the store has gone quiet the next time it checks in. Reconnecting later starts a fresh pairing.
Does this work on WordPress multisite?
This has not been tested on a multisite installation. Use on multisite at your own risk until this is verified.
Is this compatible with WooCommerce's High-Performance Order Storage (HPOS)?
Yes, compatibility is explicitly declared. The plugin does not read or write order data.
更新日志:
- Security: when a shopper resets their password on your store's own "Lost password" page, they are now also signed out of your app on every phone. Before, on WooCommerce 8.0 to 10.8, an old app sign-in could keep working after the reset.
- The plugin's screen is in the current StoreToNative look: a light header, the violet mark and a new sidebar icon.
- Connected stores get a column on wide screens: open your app in the console, send a push, design, publish, this week's numbers (new installs, orders in the app, revenue, pushes sent) and help links. The numbers come back with the daily check-in; nothing new is sent.
- The directory screenshots show the new screen.
- The directory page now leads with what is free: the Store readiness check, which needs no account and sends nothing. The readiness check is the first screenshot. Nothing about what the plugin does or sends has changed.
- The plugin's directory page is shorter and easier to read. Nothing about what the plugin sends has changed.
- Older changelog entries moved to
changelog.txtinside the plugin. Older versions: seechangelog.txtin the plugin folder.