App Overview

brrr • send push notifications icon

brrr • send push notifications

Simon B. Støvring · Developer Tools

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

PRICE
Free
In-app purchases
BUSINESS MODEL
Freemium
No overall Grossing estimate available
RATING
4.5
15 ratings · Top 15%

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.

What's included17 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.

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.

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

> SELECT BUILD PLATFORM:

Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.

// RORK SYSTEM PROMPT
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.

Continue in Rork copies the full prompt to your clipboard first, then opens Rork in a new tab.

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

Implement a better organization system for notifications.

Assumption to check: Users often find it hard to manage multiple notifications.

Validate with people who use this workflow before building.

Hypothesis 2

Simplify the user flow for in-app purchases.

Assumption to check: In-app purchase processes can be confusing.

Validate with people who use this workflow before building.

Hypothesis 3

Provide more customization features for notifications.

Assumption to check: Limited customization options for notifications.

Validate with people who use this workflow before building.

Hypothesis 4

Introduce feedback options to improve user experience.

Assumption to check: Lack of user feedback mechanisms.

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

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 >

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
Zustand
@react-native-async-storage/async-storage
react-native-paper
@react-native-community/datetimepicker
BUILD KIT DIFFICULTY
Intermediate

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.