Naming your app: title, icon and bundle id
Three decisions that are hard or impossible to change after launch: a name that survives search, an icon that reads at 40 pixels, and a bundle id to keep.
Designing a storefront that feels native, and changing it over the air without a new build or another review.
A store app should feel like an app, not a shrunken website. These posts cover the design side: home screen layouts that sell, bottom tabs versus a side menu, onboarding screens, product images and a small design system a brand can keep consistent.
They also explain over-the-air changes: how a new banner, layout or seasonal theme can reach installed apps without a new build or another store review, and where the limits of that are. If you are planning a redesign or a seasonal campaign, start with these posts, then test each change on a real phone before shoppers see it.
Three decisions that are hard or impossible to change after launch: a name that survives search, an icon that reads at 40 pixels, and a bundle id to keep.
Store apps do not need a tutorial. What the first launch should do, when to ask for notification permission, and why a signup wall costs you installs.
A method for picking an app palette and typography that survives real product photography, plus the contrast and touch-size rules that are not optional.
Navigation decides how much of your catalog people see. When tabs beat a drawer, how many tabs is too many, and the hybrid that works for deep catalogs.
How to plan a Black Friday campaign when a new build means a store review: which changes ship over the air, which do not, and the calendar that keeps you out.
What belongs above the fold in a shopping app, why it is not a smaller version of your website's homepage, and a layout order that works for most catalogs.
Hi! 👋 Ask me anything about turning your WooCommerce store into a native iOS and Android app — pricing, setup, publishing, or whether your store is a good fit.
AI assistant — it can be wrong. For anything important, contact us.