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.
OpenClient brings the deepest native iPhone and iPad integration available for OpenCode to your own self-hosted server.
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 OpenClient for OpenCode: 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
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: User interface can be cluttered and hard to navigate.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Limited customization options for users.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Lack of offline functionality.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Inadequate help and support resources.
Validate with people who use this workflow before building.
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
OpenClient brings the deepest native iPhone and iPad integration available for OpenCode to your own self-hosted server. Keep coding sessions within reach when you are away from your desk. Browse projects, resume chats, review tool activity, answer permission and question prompts, and follow ongoing work from a fast native interface built around the way iOS and iPadOS actually work. OpenClient is designed for developers who already run OpenCode and want more than a remote chat window. It is a mobile command center for active agent work, long-running tasks, quick follow-ups, and remote check-ins. Core OpenCode features: - Connect to your own self-hosted OpenCode server - Save recent servers and reconnect quickly - Browse projects, workspaces, and session history - Open existing sessions or start new ones - Continue chat conversations from iPhone or iPad - Stream assistant responses and tool activity live - Review reasoning, messages, command output, and file references - Send text prompts and attach supported files from iOS - Sketch ideas, UI notes, and architecture diagrams with the built-in Excalidraw drawing board - Dictate prompts by voice when typing is not convenient - Use commands, agent mentions, model choices, and session options when available from your server - Track session-local todos while work is in progress - Respond to permission requests without returning to your computer - Answer multiple-choice and custom question prompts in a first-party UI - View and manage MCP server status when supported by your OpenCode setup - Inspect project files and source-control context from the app iOS and iPadOS integrations: - Native SwiftUI interface optimized for iPhone and iPad - Multi-column iPad layout for projects, sessions, and chat - Live Activities for following active sessions from the Lock Screen and Dynamic Island - Home Screen widgets for recent and pinned sessions - Shortcut and control widgets for faster access to common OpenClient actions - Secure Keychain storage for saved server passwords - App-group sharing for widget snapshots without storing your server password in widget data - Native file picker support for adding compatible attachments - Local Excalidraw-powered sketch attachments exported directly into chat - Voice dictation-friendly composer controls - Deep links from widgets back into the right server, project, and session Privacy and self-hosting: OpenClient is built for private, self-hosted use. You choose which OpenCode server it connects to, and your session data stays tied to your own OpenCode setup. Server credentials are stored securely on device, and OpenClient does not provide or proxy an OpenCode backend. Terms of Use (EULA): https://www.apple.com/legal/internet-services/itunes/dev/stdeula/
Written user reviews are not shown here. Check current App Store reviews >
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.