Himalaya Your apps →

Real native apps that ship over the air.

Author on whatever machine you already have — no Xcode, no simulator. See a screen render in under a second. Publish to every device in seconds. Genuine iOS and Android, plus web, macOS and the wrist.

Start with your coding agent

Paste this into Claude Code, Cursor, Codex — whichever agent you use.

I want to create a mobile app for my business. Follow this skill:
https://apps.wix.com/_api/himi-serve/skill.md

Or build from Claude or ChatGPT — add the Wix Native App Builder connector, sign in with Wix, and describe your app. Nothing to install.

Connect →

Or open one that already works

Not skeletons, not code samples. Each tile below is a real, published app running on this plane right now — tap one and it boots in your browser exactly as its users would see it. Found the closest fit to your business? Copy its prompt and your agent starts from that app instead of from nothing.

The loop

Five steps from an empty directory to the app on a phone — and not one of them needs a Mac.

1

Author anywhere

From a bare directory, on whatever you already have. The CLI carries its own runtime, so there is nothing to check out, no per-app native project, and no Xcode.

$ himi init my-shop --template retail-store $ cd my-shop
2

See it under a second

HTML, a render tree and a PNG — light or dark, at real device sizes. No simulator, no build step. When a screen comes back blank, one endpoint names the binding that failed to resolve instead of leaving you to guess at pixels.

$ himi render himi_branded_home --png home.png --device iphone $ himi render himi_branded_home --scheme dark # same second
3

Prove it without writing tests

Every action your screens declare, dispatched against the real worker from a cold boot — once with the network empty, once with it failing. Derived rather than authored, because the test nobody writes is the test that never runs.

$ himi test --json
4

Publish in seconds

Screens, logic, tokens and config reach every device that has the app — staged to a fraction of them first, and revocable in minutes if one is wrong. Nothing is live until you promote it.

$ himi login --browser # once, with your Wix account $ himi push --draft # preview URL + release id $ himi promote --app my-shop --release <id> --target wix
5

Get the app on a phone

Ask for a build and a real signed iOS and Android app comes back in about four minutes, with an install link you can send to your testers or your client. No Mac, no Xcode, no certificates, no keychain — the platform builds and signs it for you.

$ himi icon generate # the template's own icon will not ship $ himi dist --app my-shop --platform ios,android --target wix

Building the same app from scratch, all five of those are yours to build first — and then to keep working, on two platforms, forever.

What you get out of the box

None of this is something you configure, assemble or keep working. It is what an app is here.

It looks and moves like the phone

Real native components on each platform — native scrolling, native gestures, native transitions, the system’s own type and dark mode. Not a website in a wrapper, and not a lookalike either: they are the platform’s own widgets.

It feels fast, without you tuning it

The first screen ships inside the app, so a cold launch paints immediately and then fills in live data. Images decode off the main thread at the size they are shown. Long lists build rows as they scroll, not all at once.

Your Wix business is already wired in

Store, bookings, events, blog, CMS, forms and members arrive as working native screens against your real site — products, prices, availability and orders, not placeholder content. Pointing an app at a site is two environment variables.

Push and deep links already work

Registration, permissions, tokens and delivery are handled. Schedule a notification on the device or send one from your server, and tapping it opens the exact screen it should. Links behave the same way — a URL, a QR code or a link in an email opens that screen directly, including from a cold start when the app wasn’t running.

The whole device, when you ask for it

Camera, location, biometrics, contacts, calendar, background audio, an on-device database. Declared per app, so only what you ask for ships — and each platform’s permissions and entitlements are generated from that declaration, never hand-edited.

Nothing to run, nothing to maintain

No GitHub, no Mac, no build server, no certificates, no simulator, no per-platform project to keep in step. You write the app; everything under it is handled.

Why an app and not just the site

A place on the home screen

An entry point that survives a closed tab, a cleared cookie and a forgotten URL. One tap — not a search, a banner and a login.

Reach people who left

A customer who hasn’t opened the app in a month is one notification away, on their lock screen — not an email in a promotions tab.

People spent 5.3 trillion hours in mobile apps in 2025 — time spent grew 3.8% year over year while downloads grew 0.8%. The people who already have an app keep coming back to it. Source: Sensor Tower, State of Mobile 2026