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.
A .md file from an AI chat, full of # and **
$7.99
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.
Your first Build Kit is free with a verified email.
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.
Loading build analysis and prompts…
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.
A .md file from an AI chat, full of # and **. A browser can show it to you. emdee lets you rewrite it — in that same clean, formatted view. You don't need to switch between a reading mode and an editing mode. You edit the document while it stays clean and properly formatted, exactly as a .md document should look. Headings stay heading-sized, tables stay tables, and you type directly into the document. Want bold? Select the text and tap the button. You never type the symbols, and you never see them. Save, and it's still a plain .md file. ■ When you'd use it You saved an AI answer as .md — now you want it in your own words, not just readable AI drafted your travel plan or checklist — now the dates and details need to be yours You want to keep notes and minutes in .md, without looking up syntax as you write ■ What you can actually edit "emdee" is not a viewer — it's a true WYSIWYG Markdown editor. All of this works right in the formatted view: Headings (six levels), bold, italic, strikethrough, inline code, links Bullet lists, numbered lists, and checklists you can tick with a tap Block quotes, code blocks, horizontal rules Tables: insert with one button, and add or delete rows and columns from that same button's menu. Line breaks inside cells are supported Find and replace — Replace All comes back with a single undo It all sits in the format bar along the bottom, which rises with the keyboard so you can change formatting mid-sentence ■ Images An image in the same folder as the document you have open is drawn right there in the text. So is one in a folder below it. PNG, JPEG, GIF, WebP and SVG are drawn. So are images on the web (https://) HEIC — what an iPhone camera writes — is not drawn. Export it as JPEG and it is The first time, emdee asks permission to read that folder — one button, and it never asks again Anything it cannot draw shows its path in a frame instead The image button on the format bar puts one in. An image from outside the document's folder is copied into that folder first, and a file of the same name is never overwritten. What gets written is a relative path, so hand the images over along with the document. Exported HTML and PDF have the pictures embedded, so they travel on their own. The  in your file is not touched by any of this. ■ More features Table of contents — tap a heading to jump there. On iPad it opens as a column beside your text instead of covering it Print, and export to PDF, HTML, or plain text. Lines break on paper exactly where they break on screen, and tables never split mid-row across pages Light, dark, or follow the system Body text can follow the system text size or stay at a size you choose, and the line width is yours: fit the screen, or match A4 print ■ What you write stays a .md No proprietary format, no importing. The file you have open is the .md itself, opened in place where it lives — no copy is made. It saves back readable by GitHub, VS Code, Obsidian — anything. Even details like line breaks inside table cells are written the standard way, as an HTML br tag. Line endings (LF / CRLF / CR) and text encodings (UTF-8, UTF-16, and legacy encodings such as Shift_JIS) are preserved exactly as the file was opened. Files made on Windows keep their format intact. ■ One purchase — iPhone, iPad, and Mac The same document, on the same page layout, wherever you open it. ■ What emdee doesn't do File management belongs to the Files app, and sync belongs to iCloud Drive. There is no proprietary notes database and no cloud service. The only thing open is your .md file. Images are looked for inside the folder your document is in, and nowhere else. A reference pointing outside it (../ or an absolute path) is not drawn, and neither are HEIC, AVIF or TIFF files, or images over roughly 8 MB (24 MB per document). Anything that cannot be drawn shows its path in a frame instead. Questions and bug reports are welcome — see the support page.
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.
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.
Not assessed in a Build Kit yet.
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.