Simon B. StøvringYesterday evening I threw together a landing page for a side project to my other side projects:
It’s a tiny and opinionated tool for sending push notifications. No sign up. No message history. No dashboard.
I like it. Would you? 😄
brrr’s onboarding flow is virtually nonexistent because I don’t think it needs to be any more complicated than this.
brrr is so simple. Its killer feature is everything that’s not there.
If I am to release brrr, then I’ll need to come up with a pricing strategy. Even if it’s a simple app, I’ll need to ensure that I cover my costs and ideally earn just a little. Choosing a strategy is difficult, though.
Current ideas include:
- First N pushes are free, then $X for 1,000 pushes.
- First month is free, then $X/year.
- One device is free. $X/year for multiple devices.
A tip jar and one-time purchase seem risky for an app with hosting costs.
Honestly, I'm leaning towards the first month being free and then charging something like $6.99/year. No monthly option. It’s a pricing model that’s as simple as the app, and a price point where I think most people who’d use it won’t mind too much. Or so I hope.
A colleague convinced me that I needed to add an additional feature to brrr. Tapping a notification should show it in the app to prevent accidental taps and missing the notification.
Billy Adams@simonbs Just out of curiosity, how would the web-hook be invoked/triggered here?
@billyadams For the agent to send a notification? I’m actually not sure. My colleague uses it like this but I don’t know how he set it up. I suppose it could just be part of AGENTS.md that it should make a curl command once it’s done with specific tasks.