Turn a product idea into an app you can keep building.
First Draft is designing a guided workshop for people who can describe what they want but do not want to become framework experts. The goal is to leave with a working Foundation—and a clear path to continue with your own AI or any developer.
Pilot dates, duration, registration, and pricing have not been announced.
Who it is for
Product knowledge matters more than framework knowledge.
The workshop is being designed around facilitated participants, including former students, product managers, operators, founders, and domain experts with a concrete application idea.
You can describe the work
You understand the people, information, permissions, and outcomes involved—even if you do not know the technical vocabulary.
You want help making decisions
The facilitator helps surface assumptions and turn product intent into an inspectable Foundation Plan.
You plan to keep going
This is for an idea worth extending after the workshop, not a disposable mockup that stops at the first demo.
You want an ordinary escape hatch
When the generated foundation runs out, your own agent or a developer should be able to continue in normal application code.
Target outcome
More than a prototype, less than a finished company.
The intended workshop outcome is a coherent first Foundation: useful enough to try, conventional enough to inspect, and ready for the owner’s next agent-assisted change. This remains a development target rather than a public guarantee.
A working web app
A deployed application with the basic domain model, screens, authentication, and selected workflows wired together.
A native app you can inspect
Interact with an unsigned Simulator build produced from the actual generated iOS project, using local Xcode Simulator or, for the no-Mac pilot path, Revyl in the browser. Physical-phone installation is a separate lane.
An ownership package
Repository, approved Foundation Plan, tests, Compilation Record, deployment instructions, and owner-controlled accounts rather than a platform-only project.
Demonstrated continuation
Close First Draft, open the app with your coding agent, and make a small change outside the generated surface.
Workshop plan
The app emerges from decisions, not a single giant prompt.
Facilitation is part of this first delivery experiment, not the long-run product architecture. It creates room to test assumptions, compare alternatives, and expose what self-service must eventually handle.
-
1
Frame the product
Choose a bounded first version, name the people it serves, and identify what would make the workshop result useful.
-
2
Model the domain
Work through records, relationships, ownership, permissions, states, important operations, screens, and notifications.
-
3
Review the design
Inspect and approve the Foundation Plan after correcting its assumptions. Review Rails as the disclosed workshop target and inspect its material realization choices.
-
4
Compile and exercise
Generate the conventional Foundation, run it, seed it with representative data, and try the important journeys.
-
5
Take it over
Move into the owner-controlled repository and make a post-compilation change with the participant’s chosen agent.
The no-Mac participant test
The native path has to work on ordinary workshop equipment.
The workshop is being designed around a participant with a Windows laptop and no paid Apple Developer membership—not around a room full of mobile engineers.
For that participant, Revyl browser-Simulator preview is the selected default. It runs an unsigned Simulator build produced from the actual generated iOS project, but it is not an iPhone installation and does not prove real push, hardware behavior, signing, or App Store distribution. The participant keeps the project source and a path to those owner-controlled lanes if they later enroll with Apple; continued access to the Revyl session is not part of the generated project.
Workshop questions
Practical details
Pilot registration is not open yet.
This section will become the workshop interest form once the pilot format, dates, and follow-up process are ready. For now, the honest call to action is to check back as development progresses.