Notifications should be easy.
We’re building Notifiable so any developer can add, send, schedule, and manage notifications without the usual complexity.
Simple to start. Easy to use. Built for everyone.
Join the waitlist → https://t.co/UBh2QI8nwd
#React#ReactNative#Flutter #JavaScript #TypeScript #MobileDev #WebDev #Developers #IndieHackers #BuildInPublic
Your code can be secure. Your server can still be vulnerable.
Java4Shell (CVE-2026-114938) could let attackers execute code without logging in.
The flaw isn't in your code. It's in the Java runtime.
Check your versions. Patch affected builds
#CyberSecurity#java4shell
Security scanners find vulnerabilities. But who finds the flaws they don't know how to look for?
We're experimenting with Rook 0.1.1 ♜ our first step toward launching a world-class autonomous AI Security Officer.
StaySecure. ♜
#CyberSecurity#AI#AppSec#BuildInPublic
Your first users gave you more than their email addresses.
They gave you the benefit of the doubt.
They never asked which doors you’d left unlocked.
They assumed you’d checked.
Somewhere, someone might be checking for them.
it's time to have a rook ♜
#CybersecurityNews #BuildInPublic
You shipped. Closed your laptop. Your next move could wait until morning.
Theirs couldn’t.
You woke to a message: “Why is my data for sale?”
You thought you were still building.
Someone else had seen checkmate.
You will be the next ♜
#CybersecurityNews#CybersecurityStocks #Hacking #builder #BuildInPublic #StaySecure
Fun signup tip: don't make users find their inbox
Our verify-email page used to have a big "I've verified my email" button
The problem is people pressed it a median 7.5 seconds after landing, before opening any email. It read as "Continue."
We deleted it. The page already polls, so now it says so and gives one button: "Open Gmail" or "Open Outlook."
Consumer domains are a lookup table & company domains are the trick: check the MX record when you send the email
> https://t.co/hW2WcV227f → gmail
> *.mail.protection.outlook.com → outlook
> anything else → no button
> etc....
300ms cap, runs while the email sends, costs the user nothing.
Lately, I've been building a small mobile game for my indie studio, Lazy Rabbit 🐰
This is probably my 6th game built with React Native, and I keep running into the same struggle: building reusable, arcade-style UI components.
Buttons, cards, modals, animations… all from scratch.
Thinking of turning these into an open-source React Native UI package for game devs.
Worth shipping?
A tiny independent games studio I started in 2026.
We’re here to make games that are playful, a little weird, and actually fun to think about.
Small games. Big curiosity.
Our first game is on the way.
https://t.co/L1SuB7dPXd
Spent the last 48 hours shipping a lot at Notifiable.
New SDKs, easier integrations, and one-prompt setup with your AI agent.
But we're building something bigger than notifications: engagement infrastructure that helps users build habits around your app.
You build the app. Your agent keeps users engaged.
https://t.co/UBh2QI7PGF
We just changed how pricing works at @notifiable_ .
Why? Because developers shouldn't have to pay for capacity they don't need or jump between plans as their apps grow.
So we made pricing usage-based and flexible.
→ Start free with 5,000 notifications.
→ Choose the volume that fits your app.
→ Scale up as your users grow.
→ Need more than 1M? Let's talk.
Our goal is simple: make notification infrastructure accessible to indie developers, startups, and growing teams.
You focus on building. We'll handle the notifications.
https://t.co/MPHaGv5xb9
Spent the weekend making it easier to bring users back to your app.
Notifiable now has MCP + agent onboarding.
One prompt in Claude Code or Cursor to set up notifications and draft lifecycle workflows.
You build the app. We help users come back.
https://t.co/5tMrGxzcfB or hit https://t.co/Sphj6F7fJz
Your AI agent helped you ship the app. Then your first users signed up.
What brings them back?
We built Notifiable so your agent can send notifications, build segments, and automate follow-ups through MCP.
You keep building. Give users a reason to return.
https://t.co/NGGK4CnmZC
We started building Notifiable because sending a push notification shouldn’t mean building an entire notification backend.
Today, developers can integrate, send, schedule, segment, and automate notifications from one platform.
Built for developers and AI agents.
We’re just getting started.
https://t.co/5tMrGxzcfB
Today, we're launching Notifiable.
Notification infrastructure for developers and AI agents.
Integrate, send, schedule, and automate push notifications without building the infrastructure yourself.
Build your app. We'll handle the notifications.
https://t.co/DBJnYaB0Yu
We've been building something behind the scenes. Today, we're launching Notifiable.
Push notifications shouldn't take days to integrate or require building an entire backend just to bring users back.
So we built a better way.
One infrastructure to integrate, send, schedule, segment, and automate notifications across your apps.
Built for developers. Designed for AI agents. Ready for the next generation of apps.
Less infrastructure. More shipping. Better engagement.
The future of notifications starts here.
→ https://t.co/UBh2QI7PGF
We're just getting started. ⚡
That’s exactly the question developers should be asking.
A trial-ending notification alone won’t magically improve D7 retention. It’s about sending the right message, to the right user, at the right moment.
That’s what we’re building with Notifiable: making lifecycle engagement easy to automate, then measure what actually brings users back.
Building an app has never been easier.
With AI and vibe coding, you can turn an idea into a working app in hours.
But what happens after someone installs it?
How do you bring users back? Remind them their trial is ending? Re-engage inactive users? Send the right notification at the right moment?
Suddenly, you're building an entire notification infrastructure instead of focusing on your product.
That's why we're building Notifiable.
One SDK to connect your app. A few clicks to create automated notification workflows. No need to build your own scheduling, segmentation, or delivery systems.
From your first push to automated user engagement.
- We're launching publicly this week.
Starting today, you can request early access before the public launch, try Notifiable with your own app, and share your feedback directly with us.
We're building this for developers, and your feedback will help shape what comes next.
Get early access → https://t.co/5tMrGxzcfB
Exactly. Acquisition gets users through the door, but retention is what builds a real product.
And retention doesn’t stop at onboarding. It’s about keeping users engaged, bringing them back at the right moment, and continuously delivering value.
That’s one of the reasons we’re building Notifiable.
Great point. Security is something we're taking seriously at Notifiable.
We're using a rotating gateway architecture to protect credentials and manage token access. Sensitive API keys should never be exposed in client-side code.
The goal is to make push notifications simple to integrate without compromising security, even for vibe-coded apps.