The notification that changed everything

What happens when voting becomes personal

Most feature-voting tools live in the shadows of your product. Your users log in, click a button, and vanish back into your app. They cast a vote and hear nothing until they remember to check the voting board again. Which they don't.

The Berlin maker's user was different. She'd voted for something inside the app itself, using Shpd's native iOS SDK. There was no separate page to visit, no external login, no friction. The vote was just... there. Part of the experience.

Then something remarkable happened. When the feature shipped three weeks later, the user's phone lit up. A push notification, personalized, instant. Not a broadcast announcement. Not a generic "new features available" message. This one was for her. This feature was hers.

That's when the Berlin maker messaged me. She said her user replied asking if they could become a beta tester for the next feature, and whether there was a way to vote on more ideas. The user was no longer a passive consumer of features. She'd become invested in the roadmap itself.

Why native matters when your studio is sprawling

Here's the thing about running multiple apps. Each one has its own community, its own feedback loop, its own sense of ownership. You've got a calendar app, a note-taking app, a habit tracker, maybe a music player. Different users, different problems, different needs.

But the voting tools most studios inherit are web-first. They ask your users to leave the app, open a browser, log in again, and vote on some external board. The friction is enormous. Your users don't bother. Your feedback stays thin.

When we built Shpd, we made a deliberate choice. The voting had to live inside your app, using the same native code your users already trusted. We created a Swift Package for iOS and a Kotlin library for Android. Not a web view bolted onto your native screens. Real native components. Real speed.

That choice cascaded into something bigger. If you run five apps, your users don't need five separate voting accounts. Shpd's Passport system means a single voter can participate across every app you've built. One identity, multiple apps, one community. A user votes for a feature in your calendar app, then votes again in your note app, and the system knows it's the same person. That matters for analytics. It matters for retention. It matters for building a studio culture around feedback.

The moment we realised we were building for the right people

December last year, Canny raised prices substantially. A lot of studios got angry. Some were already frustrated. Their voting boards felt like web forms from 2015. They wanted something faster, something built for mobile, something that didn't treat the App Store like a payment processing afterthought.

What struck me was how many of those studios were small. Two or three apps at first, then five, then ten. They weren't enterprises. They were makers who'd built something real, shipped it, and wanted their users to help shape what came next. They wanted honesty in their unit economics. Not In-App Purchase markups. Not per-seat pricing that looked reasonable until you actually multiplied it out.

We price in pounds, bill through Stripe, and keep the math transparent. A studio with five apps pays £19 a month. A studio with twenty apps pays the same, because we built Shpd for studios that grow. Not for studios that stay small on purpose.

One maker told us the relief of switching from Canny was less about the price and more about the fact that our push notifications worked inside her app ecosystem. Her users actually saw when their features shipped. They didn't have to remember to check an external board. The feedback loop closed.

Building roadmaps that people actually trust

There's a moment in every studio's life when a user asks: "What are you building next?" Most founders panic because they either know the answer and don't want to commit publicly, or they have no idea and don't want to say so.

A public roadmap, indexed by search engines, forces you to be honest. It also forces you to listen. When your users can see what's coming, and they can vote, they don't just consume features. They co-author them. They anticipate them. They stay longer.

The Berlin maker's second message came two weeks after the first. She wasn't asking us for help with Shpd. She was telling other makers about it. Not in a testimonial she'd agreed to, not because we asked. She was recommending it because her product felt different. Her users felt heard. Her roadmap felt real.

She mentioned the comment threads, how users could discuss the features they were voting on. She mentioned the analytics dashboard, where she could see which features were getting traction across all five of her apps. But mostly she talked about the notification. That one moment when the user knew her vote mattered.

What happens when the tool disappears

The best products feel invisible. Your users don't think about the feature-voting platform. They think about voting. They think about being heard. The notification lands, their feature is there, and they feel like they shaped something real.

That's what we're aiming for with Shpd. Not a tool you manage and maintain and struggle with in board meetings. A system that your users use inside your app, that sends notifications, that builds anticipation, that closes the feedback loop.

The Berlin maker never became a case study in our marketing. She didn't write a testimonial or agree to an interview. She just kept shipping features, kept notifying her users, and kept growing the ecosystem of apps she'd built. And that, to me, is the point. Shpd did its job so well that no one talked about Shpd.