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.
SSHHIP is a focused iPhone and iPad terminal client for developers who keep real work running on their own machines.
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 SSHHIP - Modern SSH Client: 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.
SSHHIP is a focused iPhone and iPad terminal client for developers who keep real work running on their own machines. Add your Mac mini, workstation, or homelab host, connect with Automatic or direct SSH, and jump back into the tmux or herdr session you already use. SSHHIP is built for the small moments when you need to check a build, guide a coding agent, restart a process, or send one careful command while away from your desk. SSHHIP keeps the workflow familiar: - Save hosts you own or administer. - Connect directly, without a SSHHIP account or hosted relay. - Choose Automatic, direct SSH, or Mosh per host; Automatic uses Mosh when available and falls back to SSH. - Use Automatic authentication for Tailscale SSH or other hosts that accept keyless SSH, import an unencrypted or passphrase-encrypted OpenSSH Ed25519 or ECDSA private key, or generate a non-exportable Secure Enclave P-256 key. - Attach to existing tmux or herdr sessions with one tap. - Use the CommandDial for saved command snippets, common keys, sticky arrow D-pad navigation, directional pane focus in tmux or herdr, paste, selection, voice, keyboard control, and contextual multiplexer actions, with a resting-puck tap fallback to an organized full command menu where frequently used commands can be pinned. - Send a clipboard image or selected photos to your connected host over SFTP and insert their remote paths. - Optionally sync saved-host metadata across your Apple devices through your private iCloud database. - Keep imported credentials in the iOS Keychain and hardware-backed keys in the Secure Enclave. - Use a polished dark interface designed for terminal work. SSHHIP is local-first by design. There is no SSHHIP backend, no cloud vault, no analytics SDK, no advertising, and no tracking. Command snippets and command-menu pins stay on your device. Your host list also stays on your device unless you turn on saved-host iCloud sync. When enabled, saved-host metadata syncs through your private iCloud database; passwords, imported private keys, passphrases, and Secure Enclave key references still stay out of CloudKit. Automatic hosts can connect without a saved password when the SSH server allows it. Passwords and imported private keys that you save stay in Keychain. Secure Enclave private keys are non-exportable and never leave the hardware. Terminal traffic goes between your iOS device and the hosts you configure over SSH. When you choose Send Image, each selected image goes directly from your iOS device to that connected host over SFTP, and SSHHIP inserts the remote path into your terminal input line. SSHHIP is a one-time purchase. Every feature is free for one month, then you can buy the lifetime unlock once to keep using SSH, multiplexer shortcuts, themes, saved hosts, and client-side features. SSHHIP is narrow on purpose: a calm, native way to get back to your own terminal.
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: Limited customization options for connections
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: No ability to save multiple passwords
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Lack of advanced SSH options
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: No offline capabilities
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.