The notification your users have been waiting for

Why a push notification is not just a nice touch

When you're an app studio managing multiple products, feedback can feel like it disappears into a void. A founder votes for dark mode in one app. Three months pass. The feature ships. The founder never knows you listened.

That's a missed moment. A real one. Because the person who voted isn't just a data point; they're someone who cared enough to open your app and tell you what they wanted. When the feature arrives, they deserve to know.

A push notification on feature ship does something simple but profound. It closes the loop. It says: "You asked for this. We built it. Here it is." The voter opens the app, finds the feature, and feels seen. That's not marketing. That's product respect.

For studios with 5, 10, or 20 apps, this scales. You're not sending custom emails to each app's voters. The notification travels with them, right inside the app where they live daily. It costs nothing to send. It takes a second to receive. And it often converts a casual voter into a user who stays longer and opens the app more often.

The moment we learned this mattered

We didn't start with push notifications as a priority. Early users asked for the roadmap to be public, for voting to happen inside the app instead of on a web form, for cross-app voter identity so one person could vote across their entire portfolio. Fair asks. We shipped those.

Then one afternoon, a product manager from a six-app studio reached out with a specific request. Their voters were frustrated. Features were shipping, but nobody knew. Support tickets arrived: "Did you forget about this?" The PM was spending time explaining that yes, the feature was live, check your app. It was exhausting. She asked if we could notify voters the moment a feature shipped.

We added it to Scale and Portfolio plans. Within weeks, three studios told us the same thing: engagement went up. Not because the notification was pushy. Because it was earned. The voter had already invested attention in the request. The notification wasn't a surprise ad; it was a callback to a conversation that mattered.

How it works, and why the details matter

The notification lives inside your native app. It doesn't require a separate web view or third-party service. When you mark a feature as shipped in your Shpd dashboard, every voter who backed it receives a notification through the iOS or Android SDK we built into your app.

That last detail is crucial. Because we built native SDKs for Swift and Kotlin, the notification feels native. It's not a web prompt or a generic alert. It's part of the app experience. The voter taps it, and they land exactly where they need to be: the feature page, live in your product.

For studios running multiple apps, this is where Passport comes in. Your voter is the same person across all five of your apps. When they vote for a feature in app A and a feature in app B, they're tracked consistently. When features ship in both places, they get notifications in both places. It's one journey, not fragmented across separate platforms.

The Scale and Portfolio plans both include push notifications on feature ship. So does the ability to notify across your entire app portfolio at once. You're not choosing between notifying one app or another. You notify the people who asked.

The retention question nobody talks about

One of our Portfolio customers built a wellness app with a complicated feature request workflow. They had thousands of voters spread across three apps. Six months in, they noticed something. Voters who received push notifications for shipped features opened the app 23% more often in the two weeks following the notification than voters who didn't get notified.

We didn't invent that stat. They did, using their own analytics. But it pointed to something real. A push notification for a shipped feature isn't interruption. It's an invitation. It reminds the voter that the studio listens. It makes them feel like part of something.

For studios trying to understand retention, this is worth measuring. Not every metric lives in your dashboard. Some live in the moments when your users feel heard.

A note on what this isn't

Push notifications on feature ship are not bulk marketing blasts. They're not spam. They're not trying to manipulate someone into using your app. They're the opposite. They're a way of saying thank you to the people who invested their ideas in your product.

We've seen studios abuse notifications before, and it's awful. That's why we've kept this feature simple. Mark a feature as shipped. Voters get a notification. Done. You can't customize the message to be salesy or aggressive. It just works.

And if a voter doesn't want notifications, they can turn them off in your app settings like any other notification type. Respect is part of the design.