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.
Hermex is a native iPhone and iPad client for your self-hosted Hermes agent
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 Hermex: 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.
Hermex is a native iPhone and iPad client for your self-hosted Hermes agent. It connects directly to your Hermes host. Existing Hermes Web UI servers keep working as legacy. Open existing sessions, start conversations, and follow streamed responses, tools, and reasoning as they arrive. Queue, steer, or stop an active run. Review file edits as diffs, browse workspace files, send photos and files, and dictate messages. Switch between Bots and Sessions, manage Kanban boards and Cards, browse Tasks, Skills, Memory, and Usage, and choose models, Profiles, and reasoning settings. Move to Hermes brings a Web UI server’s chats, drafts, and notifications over to your Hermes host. Live Activities keep working runs visible on the Lock Screen and Dynamic Island. Optional notifications let you know when work finishes or needs your attention. The share extension stages content from other apps for you to review and send. Agent execution happens on your configured server, not on the iPhone. Your server owns your conversations, tools, and workspace. Recent sessions and messages may be cached locally for read-only offline viewing; clear that cache from Settings. There is no Hermex-hosted agent backend, tracking, or analytics service. Optional push notifications use an open-source, self-hostable relay. Message previews are encrypted on your Hermes host and decrypted on your iPhone; the relay handles device tokens, notification metadata, and ciphertext, never message text, server URLs, or Hermes server credentials. Push is off until enabled. Hermex has no in-app account creation or in-app purchases. You need your own reachable Hermes server. Not affiliated with Nous Research.
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 features compared to desktop tools.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Performance issues with large projects.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Subscription confusion among users.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Lack of collaboration tools.
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.