Offline Access and Native Performance
Store owners check their numbers in bad places — on a train, in a basement stockroom, on hotel wifi that has quietly given up. A store app that shows a spinner in those moments is not much of a store app. My Woo Stores keeps the data it last loaded on your device and is built natively rather than wrapped in a browser, so it opens to your figures instead of a loading screen.
What actually works with no connection?
- The dashboard, with the figures from the last time it loaded
- The order list and individual order details you have already opened
- The product catalogue and product details you have already opened
- Your connected stores and which one is active
- Your language and theme settings
The cache survives closing the app and restarting your phone — it is written to the device, not held in memory. Reopening the app after two days on a plane shows you the numbers from two days ago, clearly, and then updates them when it can.
What needs a connection?
- Changing an order's status
- Editing or creating a product
- Uploading product images
- AI Rewrite and Voice Input
- Refreshing any figure to today's number
The rule is simple: reads work offline, writes do not. Anything that changes your store is a live call to the WooCommerce REST API, and if it cannot reach your store the app tells you so.
Why aren't offline changes queued and sent later?
Because on a live store, a write that silently succeeds twenty minutes later is worse than one that clearly fails now.
Imagine marking an order completed on the underground. Twenty minutes later you surface, the queued write fires — and in the meantime a colleague already refunded that order, or the customer cancelled it. The queued change lands on top and nobody knows. Multiply that across a shared store and the app becomes a source of quiet, hard-to-trace errors.
So the app does not pretend. If a change cannot reach your store, you find out immediately, while you still remember what you were doing and can decide what to do about it.
Does it force you to log in again when you're offline?
No, and this is the sort of detail that decides whether an app is actually usable on a bad connection. When a store’s authorisation needs renewing, the app checks whether you are online before sending you to the reconnect screen. If you are not, it leaves you alone with your cached data rather than throwing you into a login flow that cannot possibly complete.
Being asked to re-authenticate at the exact moment you have no internet is the single most annoying thing a mobile app can do. It is worth the small amount of code required not to do it.
What does 'native' mean here, and does it matter?
The app is built with React Native, which means the screens you scroll are real platform views rather than a website inside an app shell. Lists scroll at the frame rate the platform is capable of, gestures behave the way they do everywhere else on your phone, and the app starts without waiting on a web view to boot.
The charts are drawn with a GPU-accelerated graphics engine rather than rendered as images on a server, so changing the period on the dashboard redraws instantly and works offline like everything else on the screen.
Does it matter? For an app you open for forty seconds several times a day, yes — more than it would for one you sit in for an hour. The entire value of checking your store from your phone evaporates if checking takes longer than opening a laptop would have.
How do you refresh the data?
Pull down on any list or the dashboard. Data also refreshes when you open a screen and the cached copy is stale, so most of the time you do not have to think about it — you pull to refresh when you specifically want to know whether something changed in the last few seconds.
Does it use much battery or data?
There is no background polling. The app fetches when you open a screen or pull to refresh, and does nothing at all while it is closed — so it is not draining your battery to keep a number fresh that nobody is looking at.
New-order alerts arrive as push notifications instead, which are delivered by the platform’s own notification service. That is the difference between an app that costs you an hour of battery a day and one that costs you nothing measurable.
Is there a dark theme?
The app is dark by default, with a light theme available, and the choice persists across restarts. Given how much of this app’s use happens early, late, or in a badly lit stockroom, that is a practical decision rather than an aesthetic one.
Which devices does it run on?
iOS 15 and later, and Android 10 and later — iPhone, iPad and Android phones and tablets. It is distributed through the App Store and Google Play as a native application.
Offline caching, native rendering and push notifications are all on the Free plan, along with unlimited stores and every core management feature. See the plan comparison.
Try it on your own store
The Free plan includes every core feature and there is no account to create — connect a store and look at your real numbers.