One voter, five apps, one voice

The problem nobody talks about until they have six apps

Most app studios start with one product. The feedback workflow is simple. Users vote. You ship. Everyone's happy. Then you launch a second app. The third one follows. By the time you're managing five or six, you're drowning in fragmentation.

Each app has its own voting board. Each one collects feedback separately. A user voting on your fitness app and your meditation app are, from your perspective, two different people with two different opinions. You can't see patterns across your portfolio. You can't tell if a requested feature would serve ten people across your ecosystem or just three in one app.

We built Passport because this problem matters. A lot.

How Passport actually works

When you integrate Shpd's iOS or Android SDK into your apps, each user gets a unique voter identity. If that same person installs a second app from your studio that also has Shpd built in, Passport automatically links their votes across both apps. No login. No redirect to a web page. No friction.

The mechanics are straightforward: when someone votes on your navigation redesign in app one, and then three weeks later votes on the same feature request in app two, Shpd knows it's the same person. Your dashboard shows you that this voter cares about navigation across your entire portfolio, not just one product.

It's the inverse of what most feedback tools do. They force you to route users out of your app, through a web form, and back again. Passport lives inside your native app, where your users already are.

What changes when you can see across apps

The moment you unify voter identity, your roadmap thinking shifts. You stop prioritising features in isolation. Instead, you ask: 'Which requests are gaining momentum across multiple apps? Where are we seeing repeated feature gaps?'

A studio with a weather app and a runner's app noticed that location permissions kept surfacing in both. Without Passport, it looked like two separate problems. With it, they saw a single user behaviour pattern. They shipped a shared location-handling framework that improved their entire ecosystem.

You also see which users are power voters. Someone voting across four of your apps signals serious engagement. When they comment on a feature request, it carries different weight than someone voting once, in one app. Your team naturally gravitates towards the features that matter to your most invested users.

The push notifications help too. When a feature ships, voters get notified inside the app they voted from. But because Passport knows their identity across apps, you can also surface that shipping news in their other apps, deepening engagement across your portfolio.

Why this matters more for studios than for single-app companies

If you're running one app, Passport feels like a nice-to-have. You're making decisions based on a single feedback stream. The value is incremental.

If you're running five apps, Passport becomes operational. It's the difference between managing feedback by hunch and managing it by pattern. The data you get from cross-app voter identity directly shapes which features you ship and when.

We built Shpd for studios, not single products. That's why the native SDKs matter. That's why Passport exists. A founder running multiple iOS and Android apps needs their users inside the product, voting natively, and their votes connected. Anything else is just a web form with a different coat of paint.

The technical detail that matters

Passport isn't a hack. It's built into Shpd from the ground up, part of the core architecture. When you integrate the Swift Package into your iOS app and the Kotlin library into your Android app, Passport works automatically. No configuration. No API token wrangling. No extra billing.

The studios moving away from other platforms tell us this is a relief. They've spent months building webhook plumbing just to sync user data across tools. With Shpd, it's included. Push notifications work too. The moment a feature ships, your voters know, inside the app they love.