Paid early access for mobile teams

Every mobile pull request,
running in your browser.

Every supported pull request gets a link to the running app. Reviewers tap through it in the browser, and your coding agents drive the same build.

  • Paid early access, not a free trial
  • Simulators and emulators, not physical devices
  • Compatibility review first
  • Previews sleep between reviews

Ticking a task on Today doesn’t stick. Fix it and check it on iOS and Android before you open the PR.

  • pocketbench open preview · iOS
  • pocketbench tap “Review the itinerary” · relaunch
  • pocketbench repeat on Android

Fixed in TaskRow.tsx. The task stays done on both platforms; PR #42 has the previews and screenshots.

iPhone 16 · iOS 188c21f4a
9:41

Daylight

Today

TodayUpcoming
  • Review the itinerary
  • Book the train
  • Pack the essentials
  • Call the hotel
TodayUpcomingLists
Pixel 8 · Android 158c21f4a
9:41

Today

TodayUpcoming
  • Review the itineraryDone
  • Book the trainToday
  • Pack the essentialsToday
  • Call the hotelToday
+

Mark tasks done from Today #42

Openclaude wants to merge 1 commit into main

pocketbenchbotcommented 2 minutes ago

Preview ready for 8c21f4a

iOS SimulatoriPhone 16 · iOS 18Open preview
Android EmulatorPixel 8 · Android 15Open preview
Example with a sample app. Claude is the coding agent here.

The code moved forward. The review should, too.

For mobile product teams of 10–75 people with 3–10 regular mobile contributors.

  1. Give the branch a place to run.

    A stable pull-request link follows the latest commit. Immutable commit links preserve exactly what was reviewed.

  2. Let people and agents tap in.

    PMs, designers and QA review in a browser. Your own agents and CI drive the same build through the API, CLI and MCP.

  3. Bring the evidence back to the PR.

    Screenshots, recordings and test results carry the commit they came from. Pass, fail and unable-to-verify stay distinct.

pocketbench.io/daylight/pr/42Sample app
From commit to running app to reviewable evidence

A plan for your next review bottleneck.

Monthly pricing for founding customers. No free plan and no free trial.

Founding price

Developer

For individual mobile builders

$49/month

  • 1 named user · 1 active environment
  • Up to 3 repositories
  • 7-day evidence retention
  • Community support

Most teams start here

Team

For teams reviewing in parallel

$249/month

  • Unlimited members · 3 active environments
  • Up to 10 repositories
  • Aligned iOS + Android review
  • GitHub checks, comments + approvals
  • 30-day evidence retention
  • Shared support channel

Founding price

Agency

For specialist mobile agencies

$749/month

  • Unlimited internal members · 10 active environments
  • Up to 25 client workspaces
  • Planned client boundaries + guest links
  • Client-level usage reporting
  • 90-day evidence retention
  • Priority onboarding + support

Every plan includes stable pull-request and immutable commit links, browser review, iOS and Android access, and the API, CLI and MCP.

Get mobile PR previews

Leave your work email and the plan you want. A few questions about your team help us prepare the technical-fit call.

PocketBench is in paid early access and is not yet generally available.

Founding customers are onboarded manually. Billing begins only after your first agreed environment is running and your app passes compatibility review. Nothing is charged on this page.

Choose a plan

No payment details needed. No free trial.

Questions

Can I sign up and start today?

Not self-serve. PocketBench is in paid early access: founding teams are onboarded by hand, after a compatibility review and a signed founding order, and billing starts only once your first environment is running.

Is it a fit for our team?

It fits mobile teams on React Native with native modules or bare Expo, especially with native rebuilds, parallel branches, agent-driven UI flows or non-developer reviewers. If Expo OTA links already cover your reviews, you may not need it.

What doesn’t it do?

It doesn’t test on physical devices or hardware-dependent flows, write or fix code, run model inference or deploy to the App Store. PocketBench is not a coding agent: your tests and your reviewers decide whether a change is correct.

Does the monthly price include device time?

Runtime allowances, hosted-build pricing and overage rates are published, with spending caps, before any usage billing starts. Concurrency is not an included allowance, and there is no annual plan.

Can I connect a repository now?

Not yet. Please don’t send source, credentials, signing assets, tokens or customer data. Tenant isolation, scoped credentials and spending controls are planned requirements that must be in place before we accept any customer code.

What happens after I request access?

We review your plan and answers by hand, and a technical-fit conversation is the next step. Nothing is activated or charged automatically.