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.
Features:
$0.99 · 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 IconShop 2023: 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: Expensive subscription
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Missing features
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Poor performance
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.
Features: * Support the SF Symbols, customized text, png or other bitmaps and svg vector maps. * Quickly export a single image, Xcode Image Set package, Xcode AppIcon Set package, and drag it to Xcode to use it. * The iCloudKit stores icon files, which can be shared between different devices. * Multiple layers can be combined into new icons by importing simple icons. * You can move, scale, rotate, delete layers, adjust colors, and so on. * An icon store is being developed, and you can share icon files in the future. * Support multiple platforms: macOS, iOS, watchOS. ========================= When developing an app, there is a very troublesome problem: icon file. I won't expand on this problem if it is too much headache. It depends on the number of users of SF Symbols, Font Awesome and Icon Font. Now there are more and more open source icon libraries available, which are very good, but not good enough. As a program ape, I think the step of importing icons into Xcode Assets is very, very troublesome. Although I know that some of these functions can be realized by using Sketch templates and export settings, I want to make this process more stupid. So in 2021, I made a software called "IconShop", which can use the icon file exported from SF Symbols on the old version system that does not support SF Symbols. Because the maintenance of the MacOS project based on Storyboard is very painful, the update is very slow. Finally, I decided to rewrite one with the latest SwiftUI technology, which is now called "IconShop 2023". Since the new version uses the latest official API of Apple, it can only support the latest version of the system this year. The good news is that MacOS, iOS and WatchOS can now be supported at the same time. How happy it is to think of continuing to work for the boss while on holiday! ========================== Privacy Policy https://iconshop.aben.io/privacy-policy/ Terms of Service https://iconshop.aben.io/terms/
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.