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.
App Overview
Eponyms
Eponyms brings a short description of about 1800 common and obscure medical eponyms (e.g., Rovsing's sign, Virchow's node) to your iPhone, iPad or iPod touch
$1.99 · In-app purchases
PRICE
$1.99
In-app purchases
BUSINESS MODEL
Paid
No overall Grossing estimate available
RATING
★ 1.0
1 ratings · Below Average
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.
Build your own version
Build Kit
Make this idea yours
A product spec, screen plans, and build steps for your coding agent.
First kit free with a verified email
Add to a Remix
Combine features and design from your favorite apps.
Kit ready. Verify your email to download it.
Generating… usually about a minute.
Make it yours Optional
What should your app do differently? Your note travels with the kit so your coding agent builds around your idea.
What's included16 files
A product spec, phased build plan, differentiation notes, and screen references.
- START_HERE
- AGENTS
- EVIDENCE
- SPEC
- BUILD_PLAN
- DIFFERENTIATION
- skills/
- screens/
Preview a sample Build Kit No email needed
Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.
Screen plan
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.
Differentiate and validate
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.
Free quick prompt For a smaller starting point
Quick prompt
Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.
// RORK SYSTEM PROMPT
Rork plan preview for Eponyms: map the core Medical 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.
Continue in Rork >
Affiliate link: CloneChart may earn a commission at no extra cost
Opportunities
AI-GENERATED OPPORTUNITY HYPOTHESES
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
Enhance content with user-generated contributions or expert curation.
Assumption to check: Limited content coverage for medical eponyms
Validate with people who use this workflow before building.
Hypothesis 2
Implement advanced search and categorization features.
Assumption to check: Difficult navigation and search functionality
Validate with people who use this workflow before building.
Hypothesis 3
Focus on a clean, modern UI/UX with user testing.
Assumption to check: Poor user interface design
Validate with people who use this workflow before building.
Hypothesis 4
Include offline mode for access to key content.
Assumption to check: Lack of offline access
Validate with people who use this workflow before building.
App evidence
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
App Store description
Eponyms brings a short description of about 1800 common and obscure medical eponyms (e.g., Rovsing's sign, Virchow's node) to your iPhone, iPad or iPod touch. A perfect tool to quickly look up the meaning of any eponym. It uses the beautiful eponym database from Andrew J. Yee (http://www.eponyms.net/). ## Features • About 1800 eponyms • Full text search • Browse by any of the 26 categories • Star eponyms to keep track of the eponyms you tend to forget or with which you want to test your students on • List of recently accessed eponyms • Quick and easy learn mode ## Learn Mode The learn mode allows you to: • swipe to the left to show a random eponym but not its title • swipe to the right to show a random eponym title but not its text • pull down to reveal the hidden info Learn mode displays eponyms from the category you're currently visiting. This means you can either learn eponyms from a given category, only the ones that you've starred or simply all of them. ## Students Look out for the free student version of Eponyms: it's identical to to this version but free for educational purposes!
Written user reviews are not shown here. Check current App Store reviews >
Screenshots
< Scroll to see more >
Build scope
Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.
Define the first version
Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.
Set boundaries
Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.
Check the hard parts
Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.
SUGGESTED BUILD STACK
React Native
Expo
Supabase
axios
react-navigation
BUILD KIT DIFFICULTY
Starter
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.
