The moment your voters find out their feature shipped
A studio manager pinged us last month with a simple question: 'Can we tell voters the second their request goes live?' She'd been running Shpd for three weeks across two iOS apps, and her voters weren't finding out about shipped features. They'd just... stumble upon them. That friction sat with us, so we built it into the native SDK.
Why a web notification tab isn't enough
Most feedback tools treat notifications like an afterthought. You vote on something, months pass, and when it ships the tool sends an email. Maybe. You don't open it. Or you do, three weeks later, and click through to a web page you never visit anyway.
But mobile app users live in their apps. If you run a photo editing app or a fitness tracker, your users spend their time there, not hunting for emails. When we built Shpd's native iOS and Android SDKs, we realised early on that the notification had to live where voters actually are: inside your app.
So when a feature ships, Shpd sends a push notification through your app's native notification system. Not a web link. Not an email. A real, credible, in-app notification that lands on the home screen.
How it actually works in your SDK
The mechanics are straightforward once the plumbing is in place. You integrate our Swift Package (iOS) or Kotlin library (Android) into your app. You've already tagged features in Shpd's voting board. When you mark one as shipped, the platform sends a push through our SDK to every voter who voted on it.
That's it. The voter sees a notification. They tap it. They see the feature live in the app. No funnel drop-off. No abandoned emails.
We route this through your own push credential (the certificate or key you provide us). So you own the relationship. We're just the trigger. This matters especially if you manage multiple apps under one Passport identity. One voter across your five-app portfolio gets notified about the right feature in the right app.
The cross-app identity piece changes the game
Here's where most feature voting tools break down: a studio with three apps has to manage three separate voter lists. A user who voted in App A doesn't exist in App B's system. So when something ships in App B, the tools don't know to notify the voters from App A who also voted on it.
Shpd's Passport solves this. One voter identity spans your entire portfolio. If someone votes on a feature in your first app, their profile travels with them to your second and third apps. When you ship a feature, Shpd knows who voted across all your apps and sends the right notification to the right person in the right app.
A studio running five apps told us this alone cut their voter churn in half. Voters felt seen. Their vote mattered across the whole studio, not just in one corner.
What we learned from launch week
We rolled push notifications out to Scale tier customers first (that's the £49/month or £468/year plan if you're tracking). Within days we saw something unexpected: voters weren't just opening the notifications. They were leaving comments on shipped features inside the app. 'Love this update.' 'Can't wait to use it.' Genuine conversation.
That feedback loop is worth something. Your product team gets real-time sentiment the moment something goes out. You're not guessing whether a feature landed well. You're watching voters react to it in the platform.
One founder said, 'It's like our voters are finally in the room when we ship.' That's the goal.
When this matters most
Push notifications on ship matter most if you've been stuck on the Canny platform and felt the weight of their December 2025 pricing change. Or if you're running two to fifteen apps and losing track of voter conversations across them. Or if your users are pulling feedback from multiple feature boards and you need them to feel like a single, coherent voting experience.
Small studios (Solo plan, one app) don't need this. But anyone on Studio tier and up (five apps, unlimited voters) will recognise the tension it solves.
The notification arrives. Your voter installs the update. They see their idea made it. And they remember why they voted in the first place: because someone was actually listening.
Does your current feedback tool tell you the moment someone acts on what your users asked for? Or are they still finding out by accident?