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.
Trigger notifications from anything that can send an HTTP request: agents, scripts, automations, CI jobs, servers, smart home setups, or personal tools.
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 brrr • send push notifications: 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: Users often find it hard to manage multiple notifications.
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: In-app purchase processes can be confusing.
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Limited customization options for notifications.
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Lack of user feedback mechanisms.
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.
Trigger notifications from anything that can send an HTTP request: agents, scripts, automations, CI jobs, servers, smart home setups, or personal tools. No dashboard. No account setup. No unnecessary complexity. Just a small webhook that works. With brrr, you can: • Send notifications to all your devices or a single device • Trigger notifications from agents, scripts, and automations • Break through mute and Focus mode with critical notifications • Open links directly from notifications • Attach images to notifications • Keep an on-device notification history • Decide when notifications appear using Focus filters GREAT FOR AGENTS brrr is useful for agents and automations. Have an agent notify you when it is waiting for input, when a task finishes, when a run fails, when a deploy completes, or when something needs your attention immediately. FOCUS FRIENDLY brrr integrates with Focus filters so you can decide which notifications are allowed in different contexts. For example, allow work notifications during Work Focus while muting everything else. PRIVATE BY DESIGN Webhook secrets are generated on-device, and data stays tied to your iCloud account. brrr stores only what is required to verify webhook requests and deliver notifications through Apple Push Notification Service. Notification contents are not stored on the backend, and on-device history stays on your device. WHO IT’S FOR If you want a big dashboard packed with options and complexity, this probably is not for you. If you want a clean, fast way to make your devices go brrr, you will feel at home. Terms of Use https://www.apple.com/legal/internet-services/itunes/dev/stdeula/
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.