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.
Ever wondered how advertisers recognize you across apps and websites? It usually comes down to fingerprinting: small, ordinary details about your device, combined until the mix is rare enough to point back to you.
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 Loupe: What Apps Can See: 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: Limited app visibility on data access
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Users find it hard to revoke permissions
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Overwhelming technical jargon
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: In-app purchase confusion
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.
Ever wondered how advertisers recognize you across apps and websites? It usually comes down to fingerprinting: small, ordinary details about your device, combined until the mix is rare enough to point back to you. Loupe lets you see those details yourself. It reads the same public iOS APIs that third-party apps use, showing you the raw data and explaining why it matters. WHAT YOU CAN EXPLORE Trackers don't need your name, email, or location to recognize you. Your region, languages, settings, storage, and sensors create a pattern distinctive enough to follow you online. Loupe puts these readings in one place so you can see exactly what you're sharing. THREE LEVELS OF ACCESS Loupe sorts every reading by how much access it takes: - Passive: readable by any app with no prompt at all, from your time zone and keyboard languages to your battery and storage. - Needs permission: readings that trigger an iOS prompt, like location, contacts, photos, and motion. - Advanced: side channels that public APIs allow, like checking which apps you have installed, graphics checks in a hidden browser, and a record that survives reinstalling the app. NOTHING LEAVES YOUR IPHONE Loupe reads everything on your device and keeps it there. Nothing is uploaded, synced, or shared unless you export it yourself. There are no accounts and no analytics. A FEW THINGS YOU CAN LOOK AT - The region, languages, and settings that hint at where you live and travel - Your screen, graphics, storage, and battery details - The name on a paired accessory, which often gives away your own name - Which popular apps you have installed, worked out without any permission - The exact second your device was set up or last erased Loupe is built by Mysk, a security research team. It exposes the tracking surface of your iPhone, so you can decide what to do about it.
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.