Inside the studio / App FactoryAn internal workflow in development

From a small idea
to something
worth keeping.

Orbinook’s wider ambition is a repeatable way to discover a useful app idea, develop it with Claude and check the result. App Factory is the internal structure we are building around that process.

Follow the process
The principle

Keep the evidence
with the idea.

Each candidate gets its own case: research, decisions, specifications, revisions and checks. Reusable agent definitions sit alongside that work, so the method can improve without mixing one app’s evidence with another’s.

AN APP CASE

One idea.
Its own notebook.

  • 01 Research & sources
  • 02 Product decisions
  • 03 Specifications & revisions
  • 04 Checks & review
Planned case structure
The intended lifecycleCurrent foundations → future stages
01
Agent initialized

Find a need worth exploring.

App Factory’s market/niche discovery agent is defined and initialized. It is designed to discover and rank mobile-app opportunities and prepare a structured handoff.

An initialized agent does not establish a validated market or a completed discovery run.

02
Scaffolded / Planned

Turn evidence into a product brief.

Competitor and review research, opportunity synthesis, feature design and critique are subsequent stages. The intended Claude integration would help summarize evidence, explore tradeoffs and refine the brief.

03
Scaffolded / Planned

Build with context.

Carry an approved specification into implementation planning and code changes. We want Claude to work from a clear brief, relevant source code and the decisions already made.

04
Research & prototype work

Make the checks explicit.

The supporting iOS workflow repository explores development loops and verification. The diary also has committed verification tooling. Our direction is to combine automated checks with human inspection of the actual app.

05
Future placeholder

Learn from what happens next.

Post-launch feedback and maintenance agents are reserved as future work. The proposed loop would turn permitted feedback and reproducible issues into changes to review.

Claude in the process

A continuing
collaboration.

The commitment is to keep bringing Claude useful context—and to keep checking the result.

Our diary already has recorded Claude contributions. The next step is a Claude API integration for the internal workflow, with clear inputs, structured outputs and verification between stages.

Read the detailed Claude roadmap

Three repositories.
One direction.

The product, the reusable workflow and the engineering research each have a different role in Orbinook.

The product

diary-notebook-app

The working diary prototype: entries, folders, backgrounds, local storage and rewards.

See the prototype
The process

app-factory

Reusable roles, prompts, schemas and case organization. Discovery comes first; later stages remain scaffolded.

Reviewed at 53883b8
The research

ios-loop-workflow

Planning and notes on app-development loops, state and verification. Engineering research in progress.

Reviewed at 1128708

These are private development repositories. Their names and reviewed revisions establish the context for the work described here.

Next milestone

One candidate.
A visible trail of decisions.

Take one app idea through a documented Claude-assisted cycle. Keep the source material, proposals, reviews, revisions and checks together.

That is the next development milestone. App Factory is an internal workflow in progress, and the diary is the first product featured by the studio.