Give the idea some shape.
Our intended workflow uses Claude to turn research and constraints into a clear product brief, with decisions that can be questioned and refined.
Our development collaboratorThe work. The record. The direction.
Built with Claude.
Growing with Claude.
We’re building Orbinook around a long-term commitment to Claude. The diary is our first concrete example. Our ambition is to carry that collaboration through the next app—and the process behind it.
See the recorded contributions“We want Claude to be a continuing part of how we think through an idea, build it and make it better.”
Why Claude?
Continuity in the work.
We’re choosing a collaborator we can bring through the development process, from understanding a requirement to reconsidering an implementation after review.
Work in the actual code.
The diary history records Claude’s contribution to its initial implementation and later interface details. Those contributions have visible results in the prototype.
Bring the findings back.
We want observations, failures and review feedback to inform the next revision. Checks and human judgment stay part of the process.
This describes our development approach and intention. We have not established comparative speed, cost or productivity benchmarks.
The development recorddiary-notebook-app
Specific work.
A recorded contribution.
Two of the three commits in the reviewed diary history explicitly credit Claude, including the initial application and a later set of interface refinements.
Reviewed at 39e1637 · 8 October 2026
01
fd3941eClaude co-author creditThe first working diary.
A cross-platform diary with a deliberately simple writing interface and a customizable atmosphere.
- Where Claude contributed
- The initial Expo application, local persistence, background system and reward mechanics.
- What the user sees
- Entry creation, a journal, personal backgrounds and progress screens in the prototype.
- How it is checked
- Inspect the implemented screens and storage paths; exercise creating, saving and revisiting a sample entry.
02
2260bd5Claude co-author creditThe details that shape a daily habit.
Make writing easy to reach and make progress visible at the right moment.
- Where Claude contributed
- A floating entry action, XP animation tied to the Today view, title fitting and a playful lava-lamp interaction.
- What the user sees
- An entry button available from the tab bar, progress that catches up on return, and titles that adapt to their space.
- How it is checked
- Open the editor from different tabs, return to Today after saving, and inspect longer titles and the interaction in the app.
03
39e1637No explicit Claude creditA separate verification step.
This commit adds a layered verification gate and test files. It is part of the project’s development record and is excluded from the Claude-attributed count.
A recorded test setup is not a claim that the current application passes every check.
Context in.
Working changes out.
Claude’s evidenced role today is a development collaborator. Here is the working pattern we are carrying into our internal app-building process.
- 01 / Input
A clear brief.
Requirements, relevant source code, constraints and feedback.
- 02 / Claude
A proposed change.
Implementation, explanations and revisions to inspect.
- 03 / Verification
Checks and judgment.
Actual behavior, test results and human review inform what comes next.
Our long-term commitmentClaude API / Planned integration
The diary is a start.
We’re thinking further.
Our next step is to integrate the Claude API into App Factory. We want the context from one stage to make the next stage more useful, with evidence and review carried along.
| Stage | What goes in | Claude’s proposed role | What comes back |
|---|---|---|---|
| Research synthesis | Collected market evidence and app reviews | Identify recurring needs and summarize the evidence | A source-linked opportunity brief |
| Product definition | Selected opportunity and constraints | Develop feature proposals and critique tradeoffs | A product specification for review |
| Implementation | Approved requirements and relevant code | Propose changes and explain decisions | Working changes to inspect and test |
| Verification & revision | Test results, failures and review feedback | Diagnose issues and propose corrections | Revisions that pass independent checks |
| Later improvement | Permitted feedback and reproducible issues | Suggest fixes and product refinements | Prioritized changes for review |
The first measurable milestone
One candidate. One documented development cycle.
Keep the inputs, Claude’s proposals, human decisions, revisions and verification results together. Use what we learn to improve the process before expanding it.
Explore App Factory’s current stageA collaborator for
the chapters ahead.
We intend to deepen our use of Claude as Orbinook grows: more context, better-defined work and a stronger connection between ideas, implementation and review.
Orbinook is independent. References to Claude describe our use and plans; they do not imply an Anthropic partnership or endorsement.