Feature spec
Goal: Send a clear invoice after finishing a job.
- Add a client, line items, a due date, and payment instructions.
- Preview the total before exporting a PDF.
- Keep an editable draft if export fails.
Access Git repositories on the go
Free · In-app purchases
Evidence scope: No current overall US chart position is available. Category-chart positions shown in discovery are a separate scope. Revenue is a directional model estimate, not verified earnings.
A product spec, screen plans, and build steps for your coding agent.
First kit free with a verified email
Combine features and design from your favorite apps.
Kit ready. Verify your email to download it.
Generating… usually about a minute.
What should your app do differently? Your note travels with the kit so your coding agent builds around your idea.
A product spec, phased build plan, differentiation notes, and screen references.
Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.
Goal: Send a clear invoice after finishing a job.
Invoice editor: Client at the top, editable line items in the middle, total and preview action at the bottom.
States: Empty draft, validation errors beside each field, exporting, and a retry action that preserves the draft.
Hypothesis: Contractors need faster repeat invoices more than more templates.
First experiment: Test duplicating a previous job with five contractors. Watch where they hesitate before expanding the feature set.
The full kit adds a phased build plan, evidence notes, tool prompts, and implementation guidance. It is a plan for your coding agent, not a finished app.
Usage: Mechanics are fair game; never reuse the original name, branding, assets, or verbatim copy.
JavaScript is required to complete mailbox verification.
Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.
Rork plan preview for Git client - Working Copy: map the core Developer Tools workflow, choose the smallest differentiated feature set, define the data and monetization boundaries, then prototype the riskiest user journey first.
Preview ready. Verify your email to reveal and copy the full prompt.
JavaScript is required to complete mailbox verification. Return to this prompt preview.
Affiliate link: CloneChart may earn a commission at no extra cost
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
Access Git repositories on the go. Clone, edit, commit and push while allowing other apps access to repositories. Git is a important part of our work-life and iOS can take part in this. The ability to commit even when offline has added utility on a device that moves in and out of network coverage. Cloning repositories gets you a local copy on your iOS device with commits for all branches. You can browse the content from within the app and make changes. Other applications supporting the Files app, WebDAV or x-callback-url has access to these files. Changes made can be committed and the commits can in turn be pushed back to the remote. The idea of doing significant programming on iOS might seem far fetched when you are used to a large screen, a physical keyboard and a full IDE. But just as it turned out that not every email is serious prose, then not everything that goes on in Git is significant programming. Sometimes you just want to update a TODO file or make adjustments to your Jekyll site. Sometimes you just need to add a file the designer sent after hours. If you ever make reminders about small things to do with the code-base, then you should give Working Copy a try. You will spend less time moving stuff around and you will get much better commit messages when you write them for fixes that are still fresh in your mind. You won't be leaving your computer behind any time soon, but sometimes it is faster to just fix things with the device in your hand. When you do need to perform real work on iOS, Working Copy is a powerful tool. Editor has syntax highlighting for more than 50 programming languages and a built-in color picker. Preview images, Markdown and HTML files with a Javascript console pointing to errors in your code. Create new branches and merge or rebase them back, with a brilliant merge-tool for handling conflicts. If you need to automate your work there are Working Copy actions in the Shortcuts app for most operations. Even if you never edit a line of code on iOS, Working Copy is a great companion for reviewing and discussing code. Repositories are cross indexed and with powerful fuzzy search you can quickly jump from a symbol to the declaration or reverse from the declaration to all usages. A graph of your commits lets you zoom out for a overview of the commit tree or zoom in for specifics about each commit, with speed and beauty you won’t find in desktop Git applications. Review the changes your files have gone through with a diff viewer that is great for text and images. There is even hex-dump mode for that obscure occasion. Working Copy is a free download but you need to unlock pro features such as the ability to push commits and manage more than 5 repositories. There is no venture capital, large company or ads funding development and your support through in-app purchase directly sustains development. Try out pro features with a 10 day free trial. When you pay to unlock you get permanent access to all pro features at the time of purchase as well as any added the next year. When 12 months have passed you keep all existing pro features but any new ones introduced are locked until you renew your unlock.
Written user reviews are not shown here. Check current App Store reviews >
These are generated suggestions, not verified review quotations. Check current App Store reviews and speak with users before treating a possible gap as a requirement.
Hypothesis 1
Assumption to check: Complex setup for new users.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Limited customization options for repositories.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Performance issues with large repositories.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: No integrated code reviews or collaboration features.
Validate with people who use this workflow before building.
Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.
Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.
Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.
Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.
From the Build Kit assessment.
A reliable timeline needs an agreed scope and a technical check. Ask your agent to estimate the phases in BUILD_PLAN.md after that review.