PocketExpo
Sign Up
Now in private beta@zabir_claude_bot

Build mobile apps in a chat.
AI does the coding.

Open a Telegram chat with Pocket Expo. Describe the app you want. Watch a real Expo + Supabase codebase scaffold itself — then scan the QR and run it on your phone.

Open in TelegramSee how it works
Expo SDK 53SupabaseClaude CodeK8s Isolated
PE
Pocket Expobot · typing…
online
Build me a recipe app. Save favourites, share via link.now
On it. Spinning up recipe-pocket with Expo Router + Supabase auth.
● agent worker w17302 — installing deps
Ready. Scan to preview on your phone.
exp://recipe-pocket.craftusingai.comScan with Expo Go bundle live
add dark mode + onboarding screennow
Send a message…
0+Apps Built
0+Developers
0Countries
0.0%Uptime
Powered by
How it works

From sentence to running app in three steps.

01

Describe your app

Open the bot in Telegram and tell it what you want to build, in plain English.

build me a habit tracker with daily reminders
02

Agents do the coding

Claude Code agents scaffold Expo Router + Supabase, run the build, fix their own mistakes, and stream progress back.

✓ scaffolded · ✓ deps installed · ✓ Metro bundling
03

Scan and preview

The bot sends a QR code. Scan it with Expo Go and your app is running on your phone within seconds.

exp://uabc-pXYZ9.craftusingai.com
What you get

A full mobile stack, driven from a chat thread.

Pocket Expo isn't a sandbox demo. Each app is yours — owned, isolated, exportable. The bot is just the interface.

AI-powered code editor with syntax highlighting and neural network visualization

Claude Code as your engineer

Long-running Claude sessions edit your code, run tests, fix their own mistakes, and stream the diff back to chat.

Real Expo apps, not mockups

Every project is a real Expo Router + Supabase codebase you can `eas build` and ship to TestFlight or Play.

Vault for your secrets

GitHub PAT, Expo token, Supabase keys — encrypted with AES-GCM, injected into your workers at run-time, never logged.

Isometric illustration of isolated Kubernetes containers connected by glowing blue lines

Isolated K8s sandbox per user

Each account gets its own Kubernetes namespace with gVisor microsandbox and an FQDN egress allowlist. Your code never touches anyone else.

Real git, real GitHub

Every change lands as a commit on a real repository. Push, pull, branch, revert — the bot uses git the way you would.

Live QR over Cloudflare Tunnel

Metro runs in your sandbox, exposed through a Cloudflare-Tunnel ingress. Scan once; reload as the agent ships changes.

The boring parts — done right

Vibe-coding with production isolation underneath.

Every account runs in its own Kubernetes namespace with kernel- level sandboxing and FQDN egress filtering. Your code, your vault, your sessions — nothing crosses the line.

Isolation
gVisor microsandbox · NetworkPolicy egress allowlist
Runtime
DigitalOcean Kubernetes · KEDA scale-to-zero
Tunnel
Cloudflare Tunnel · per-project subdomain
Database
Supabase · row-level security per account
Secrets
AES-GCM at rest · injected at worker spawn
Code
Real git + GitHub repo · `eas build` ready
Commands you'll actually use

Or just talk — the bot figures it out.

Type a command when you want to be exact. Type a sentence when you don't. Behind both, the same supervisor decides what to do next.

@pocket_expo_bot
  • /new <app-name>scaffold a fresh Expo + Supabase project
  • /qr <slug>reveal the Expo Go QR for an existing project
  • /edit <task>spawn a worker against the current project
  • /projectslist everything you have built so far
  • /vaultadd or rotate API keys (GitHub, Expo, Supabase)
  • /deploykick off `eas build` against your Expo account
@zabir_claude_bot

Your next app is one message away.

Open the bot, tell it what you want, scan the QR. Free tier, no credit card, your code is yours.

Open in TelegramSee pricing