Mobile Prototypes
Two kinds of mobile app, chosen when you pick App: an instant web app you can try immediately, or a real React Native project for iOS and Android.
Which one to choose
| Instant web app | Cross-platform app | |
|---|---|---|
| What it is | A phone-shaped app that runs in the browser | One React Native + Expo project for iOS and Android |
| Ready | The moment it finishes | Preview in the browser; run it with Expo on your machine |
| Device features | None — no camera, GPS or notifications | Camera, location and Face ID can be wired in the source |
| Data | Kept in memory while the app is open | Your code decides |
| Take it with you | A shareable link | Download the project source |
Instant web app
Several screens with real navigation and transitions, working forms with validation, empty, loading and error states, and data that persists as you move around the app — seeded with realistic examples. It runs in a sandboxed frame, so it cannot reach your account or the network, and it forgets its data when the page is closed. It is generated in one pass and is not tested in a browser before you see it, so check the flows you care about.
- 1GenerateAI call
One forced tool call returns a self-contained HTML document (inline CSS and JS, no external resources).
- 2SandboxCode
Renders into a sandbox="allow-scripts" iframe with an opaque origin — no cookies, no same-origin, no reach into our APIs.
Cross-platform app
Describe the app and Webforgia shows a plan — the screens it will make and why — that you can untick before building. Screens are earned from what the app needs: an app with accounts gets a sign-in screen, a QR scanner does not. The result is a validated app specification turned into a TypeScript Expo project with one editable file per screen.
- 1App plannerCode
11 app-type playbooks. Screens are earned from the type and its capabilities, never from a fixed template.
- 2GenerateAI call
One forced tool call returns the whole validated App Spec.
- 3Defect checkCode
Walks the navigation graph for dangling targets, duplicate ids and unreachable screens. Correctness, not quality.
- 4AuditCode
Scores structure, navigation, flow, content and accessibility.
- 5RepairAI call· the audit scores below 85
One targeted edit. Discarded unless it scores better.
- 6EmitCode
Turns the spec into an Expo + React Native + TypeScript project as a file map. Screens are editable TSX; the components are fixed.
- 7EditorAI call· NOT a build stage — this runs when an existing app is edited, on a different request entirely
Applies an instruction to an existing app. Rejected only if it introduces a structural defect nobody asked for.
The builder previews the app in a phone frame, drawn from the same specification the project is generated from, so you can walk the flow before downloading. It is a preview, not a device simulator.
Limits worth knowing
- Downloading the cross-platform source needs a paid workspace — any top-up, or Pro and above. Building and previewing do not.
- Store builds (.ipa, .aab) and App Store or Play submission need your own Apple and Google accounts; Webforgia gives you the project.
- Skills do not apply to app builds yet.