Hype StackHypeStack
In every project the CLI creates

iOS and Android.
Same repo, same types.

Every project the CLI creates includes an Expo app in the same monorepo: your theme on its screens, your backend's types in its calls.

See the startersRead the docs
9:41

Aether

Good morning, Sarah

MRR

$18,940

412 subscriptions, same API as the web app

Payment received

sarah@acme.io moved to Premier

New organization

Northwind invited 4 teammates

One theme, every screen

Your design tokens, translated for native.

The web apps read OKLCH tokens and NativeWind wants HSL channels, so the CLI converts your theme when it scaffolds the project. During create you keep the frontend look with one keypress or pick a different theme for the phone, and the --mobile-theme flag does the same non-interactively.

One retheme still means editing one file. See how theming works.

What you get

What it does, and where to check.

Plain answers on the left, the file or command that proves each one on the right. The app is built with Expo, expo-router, and NativeWind, and it talks to the same Hono backend through the typed SDK.

  • A real Expo app inside the monorepo

    apps/mobile

  • Calls your backend with the same types as the web app

    sdk.users.$get

  • Your theme, converted for native screens

    --mobile-theme

  • File-based navigation, ready to extend

    expo-router

  • iOS and Android builds from one command

    deploy mobile

  • JS fixes shipped without a store review

    eas update
Ship it

The store run is one command.

hype-stack deploy mobile drives EAS for you: it checks your login, writes eas.json with the API URL from your web deploy, queues the iOS and Android builds, and can submit them to both stores. After launch, eas update ships JavaScript fixes over the air.

It also chains after the web deploy, so one session puts everything out. Read the deploy docs.

The payoff

What it saves you.

No second team, no second design system, no second API client. The phone app is another surface of the product you already run.

  • 2

    separate native teammonths
    apps/mobile, already thereday one

    App stores from the repo you already have

    One EAS run queues the iOS and Android builds and can submit both.

  • 1

    same palette, native screens

    Theme file covers the phone too

    The CLI converts your OKLCH tokens into NativeWind's format during create.

  • 0

    store review waitdays
    eas updateminutes

    Store reviews for a JavaScript fix

    eas update ships the fix over the air to apps already installed.

Feature packs to grow with

Every pack ships real source code: frontend, backend, and admin surfaces where the feature needs them. Add them when you need them, one command each.

FeatureTeamsTeam workspaces with members, roles, icons, and email invitations on top of your starter.Team workspacesMember rolesFeatureNotificationsReal-time notifications with WebSocket push, channels, in-app delivery, and admin broadcasts.WebSocket pushIn-app inboxFeatureProjectsOrg-scoped projects with members, favorites, icons, and a navbar switcher.Project CRUDMembers & rolesFeatureBilling (Stripe)Stripe integration, subscriptions, billing flows, and an admin revenue widget.Stripe checkout & portalSubscription plans
See all 12 packs

Questions, answered

Yes. Everything lands as plain source in your repository: frontend, backend, admin, database schema. There is no runtime dependency on us and nothing phones home.

Stop saying the app is on the roadmap.

apps/mobile is scaffolded with every new project. Theme it once, wire nothing, deploy it with one command.

See the startersSee pricing

included with every project