PWA Studio 10: mega menus, store switching and payments

Adobe has released PWA Studio 10, an update to its open-source toolkit for building Progressive Web App storefronts. Three features stand out, and all three replace work teams were previously doing themselves.

What is in the release

Mega menu support. Native mega menu functionality, so multi-column navigation with product imagery and promotional content becomes configuration rather than a custom build. That matters most for large catalogues and multi-brand retailers.

Store switcher dropdown. Customers can browse and buy across storefronts inside the same application, with local currency and language preferences respected. If you run multiple brands or multiple territories, that is one fewer bespoke component to maintain.

Expanded payment options. Broader payment method support and simpler configuration for common providers — Apple Pay, Google Pay, traditional credit cards and regional methods — without custom development for each one.

Performance and developer experience

Alongside the features are performance optimisations, faster build times, better debugging tools and clearer documentation. Less friction for the team building the storefront, shorter time-to-market for the business waiting on it.

Where this fits

PWA Studio is Adobe's answer to merchants who want a modern storefront without inheriting the constraints of the monolith. These particular additions — menus, store switching, payments — are the ones almost everybody was building for themselves, which is a fair sign Adobe is reading the community rather than guessing at it.

We have been building headless experiences for over a decade, and the pattern is consistent: decoupling the storefront is only worth it when the platform underneath keeps pace. Releases like this one are how it does.

What this means for you

PWA Studio 10 is available now. If you are already running it, read the release notes and test the mega menu and store switcher in your own environment before you plan around them — those two are the most likely to replace code you are currently maintaining.