FB Forkbase Home

MVP loop

One magical install is enough.

The first version should prove that a user can open the Forkbase app, connect Hermes, OpenClaw, or another agent, and let that agent find a real app, build it locally, install it into the shared iOS container, use it through the UI, switch to tools when helpful, and make one small source change.

The First Demo

“Install a workout tracker and create my first push day.”

  1. 01User opens the Forkbase app.
  2. 02User connects Hermes, OpenClaw, or another agent.
  3. 03User asks for a workout tracker and first push day.
  4. 04Agent browses the Forkbase registry.
  5. 05Agent chooses an app, explains permissions, and builds it on the Mac.
  6. 06IPA imports into Forkbase Container.
  7. 07Agent launches the app inside Forkbase.
  8. 08Agent uses UI control to complete onboarding.
  9. 09If the app exposes tools, agent switches to tools.
  10. 10User sees the app actually filled out.
9:41 Agent active

Installed from Forkbase

Push Day A

Bench press4 x 6
Incline DB3 x 10
Lateral raise3 x 15
The wow moment is not app generation. It is an agent actually using software.

What Ships First

Small surface area. Real end-to-end proof.

01

Registry

A tiny web catalog of app repos, screenshots, manifests, and verification status.

02

Manifest

A `forkbase.json` recipe with build steps, permissions, UI support, and optional tools.

03

Mac builder

The user's Mac runs Xcode and packages the app, instead of pretending mobile build infra is free.

04

Forkbase app

The app users open to connect their preferred agent and run marketplace apps.

05

Agent driver

Screenshot, UI tree, tap, type, scroll, launch, and app-tool bridge for the connected agent.

06

One remix

The agent changes one small thing, shows a diff, and proves the app can become personal.

Nope, Not Yet

Do not burden the MVP with economy theater.

No payments No ratings No royalty enforcement No social feed No blank-slate app generator pitch