Wix Himalaya: AI-built native apps are coming alongside Studio Two
Wix is preparing a new platform for mobile apps, and it works the way the new editors do. Its working name is Himalaya. An AI agent talks to the business owner, writes a plan, builds a native iOS and Android app from a template, brands it from the owner's Wix site and hands over a private preview. While Wix Studio Two (also written as Studio 2) rolls out, Himalaya is already public enough to try.
Status: not announced. There is no product name for customers, no price and no launch date. Wix's own Himalaya page says authoring is currently for Wix developers and their agents. Everything below comes from public sources: that page, the agent skill, an npm package published since 17 September 2026 and API documentation from early November.
What Wix is releasing this autumn
Himalaya is one of several AI releases that land around Studio Two. Each is at a different stage:
Wix Studio Two. Announced on 2 November 2026 with Aria 2.0, a React code layer and export to standard React. Rolling out to Wix Partners first, then to all users.
Harmony to Studio Two. Moving Wix Harmony sites into Studio Two without starting over. The Studio Two page lists it as coming soon.
Symphony by Wix. A separate AI agent platform for running a business, launched in August 2026 as an app for iOS, Android and desktop.
Himalaya. Native mobile apps built by an AI agent. Public traces, no announcement.
Today Wix sells mobile apps through its app builder and the Branded App plan. The AI chat in that builder launched in 2024 with plans from $99 a month, and Wix still describes the builder for Studio agencies in October 2026. Himalaya is a different engine underneath.
What Wix Himalaya is
Himalaya draws native screens from a description stored on the server. The app on the phone contains the platform's own components, and a screen is data that tells it what to show. That is why changes reach every installed app over the air, without a new App Store build. Wix says the same app runs on iOS, Android, the web, macOS and watches.
Native, not a wrapped website. Scrolling, gestures, transitions, type and dark mode come from each platform.
Wix business data built in. Store, bookings, events, blog, CMS, forms and members appear as working screens connected to the real site.
Push and deep links. Notifications and links open the right screen, also from a cold start.
Builds without a Mac. Wix builds and signs the iOS and Android files in about four minutes and sends an install link for testers.
Made for agents. The page starts with one prompt to paste into Claude Code, Cursor or Codex. The package includes an MCP server.
An update for every Wix mobile app
The clearest signal for existing app owners is in the agent skill. It has a separate route that reconstructs a published One App, Branded or Spaces app on Himalaya. In the API, most new projects already get the platform value for Himalaya, while older ones keep separate iOS and Android values.
Wix has not said when or how existing apps move.
If the migration route is what it looks like, apps built in the current builder will get native screens, over-the-air updates and the new templates without a rebuild from scratch. We read that as good news, with the caveat that nothing is announced.
One more change matters for course and content businesses. Apple requires digital goods in iOS apps to be sold through its own payments, which was a known limit of Branded App. The Himalaya guides describe App Store in-app purchases for Online Programs, digital products and one-time pricing plans. Subscriptions are not supported yet.
The loop: from an empty folder to a phone
Wix's Himalaya page describes the developer loop in five steps, none of which needs a Mac:
Author anywhere
Start from a template in an empty folder. The tool carries its own runtime, so there is no Xcode and no native project per app.
See it in under a second
Render any screen as a picture at real device sizes, light or dark, without a simulator.
Prove it without writing tests
Every action a screen declares runs automatically from a cold start, once with no network and once with a failing one.
Publish in seconds
Screens, logic and styles reach installed apps, first a small share of devices, and can be rolled back. Nothing is live until it is promoted.
Get the app on a phone
Ask for a build, and signed iOS and Android files come back in about four minutes with an install link.
Same logic as the new Wix editors
If you have used Plan mode in Studio Two or asked Aria to build a section, the agent's journey will feel familiar: describe, plan, build, review. The skill gives the agent eight steps:
Get to know the business, including how its customers pay.
Work out the starting point: a Wix site, a business without a site, Wix Headless, a Base44 app or a new app outside Wix.
Write a plan with the screens and who may see which data, then wait for the owner's approval.
Build from the closest template.
Brand it from the site.
Run the checks.
Review a private preview in the browser.
Make test builds only when the owner asks.
Between those steps sit approval gates. Creating a paid Wix site, connecting to Wix data, reading orders or members, publishing a preview, going live, setting up push notifications and building app files each need their own yes, right before the action. Approving the plan does not cover them. Reading the published site needs no approval, because it is the same as opening it in a browser.
We saw the same pattern in our test of the Harmony editor skill, where an AI chat rebuilt a template on Harmony: the agent plans, shows, checks and asks before anything goes live.
No jargon, and something to look at
Two instructions in the skill say a lot about who Wix builds this for. The agent must not make the customer learn Himalaya's terms, and it must keep the owner watching. The skill says a build takes most of an hour, so the agent shows pictures instead of status text:
a first picture of the app as soon as a template exists;
no more than about five minutes of silence without a line on the current step and the next one;
a build board in the browser that fills itself with every rendered screen and check;
at the handover, a making-of page that shows the app taking shape, next to the preview link.
The questions come first: the agent starts by learning the business, and it may not present a demo on sample data as the customer's app. It has to connect real data or say plainly what is fake. Text taken from the customer's site counts as untrusted data, quoted but never followed, which protects the agent from instructions hidden in a page.
Many templates, typical apps
The public catalog lists 45 templates today, and each one is a working app you can open in the browser. 25 are built for Wix sites. Ten verticals come in pairs, an app for customers and one for the owner: beauty salon, gym, yoga studio, restaurant, retail store, events, community club, nonprofit, podcast and portfolio. The other 20 are general apps such as ride hailing, food delivery, banking, stay booking, a course player and a habit tracker.
This is a trade-off. A business gets a tested app for its vertical in hours instead of months, and the screens follow known patterns: a salon books treatments, a restaurant shows its menu and opening hours. Expect many Himalaya apps to look related.
The skill pushes against that with a branding step: the agent studies screenshots of the site, takes the accent colour from the site itself instead of inventing one, uses the site's own headings and button labels in its language and checks dark mode.
You can open the ride-hailing template and the rest of the catalog in any browser.
Who builds the app now
Put together, the process is designed so that a site owner and an AI agent can get from idea to app without a designer, a developer or an agency. The agent asks the questions, writes the plan, takes the brand from the site, generates the icon, runs the tests and requests the build. The owner approves each step that matters.
Two limits stand between that design and today. Wix says authoring is currently for Wix developers and their agents. And the skill stops at test builds: publishing to the App Store and Google Play is not part of the agent's job yet.
We also tried it ourselves. Without a Wix account, the package created two template apps, rendered their screens and ran a live preview on a Mac in a few minutes. Without a connected site, photos and prices stay empty, which matches the skill's rule that a demo on sample data is not the customer's app.
parnii note
For small businesses on Wix, a branded app has mostly been a nice-to-have with a monthly price. Himalaya could change that, especially for course and booking businesses that need App Store payments. If our reading of the migration route is right, existing Wix apps will benefit too. When the platform opens, we would start with one vertical template, connect a test site and see how far the owner gets without us.
FAQ
Has Wix announced Himalaya?
No. As of 6 November 2026 there is no press release, product name, price or launch date. What is public is a Wix web page about the platform, an npm package, an agent skill and the Containers Projects API documentation.
Will Himalaya replace the Wix Branded App?
Can I sell online courses inside an iOS app built with Himalaya?
The package guides describe App Store in-app purchases for Online Programs, digital products and one-time pricing plans. Subscriptions are not supported yet, and Google Play billing is not described.
Do I need a Mac or Xcode to build a Himalaya app?
No, according to Wix's Himalaya page. The command-line tool runs on any computer, and Wix builds and signs the iOS and Android files in the cloud in about four minutes.
Sources
Part of our Wix Studio Two (Studio 2) series. Based on public sources and our own test on 6 November 2026. Last checked: 06 November 2026.
