One voter, one identity, five apps. Why that matters.

The problem nobody talks about until they hit it

If you run a portfolio of mobile apps, you know the pattern. A user loves your fitness tracker. They also use your meal planner. They might install your social app later. They're engaged across multiple products.

But when feature voting happens in silos, you lose that context. User 47 requests "dark mode" in your iOS fitness app. User 2,104 requests it in your meal planner. User 9,890 in your social app. On paper, three separate requests. In reality, one engaged user telling you the same thing three times.

Most studios either build spreadsheet workarounds or ignore the friction entirely. Both cost time. Both lead to worse product decisions.

What changes when voters have one identity across your apps

We built Passport, our cross-app voter identity system, because spreadsheets shouldn't be anyone's feature-voting infrastructure. The idea is simple: one person, one email, one voter profile. They log in once. They vote across every app in your portfolio. You see them as one voter, not five.

The immediate win is clarity. You'll spot patterns you couldn't see before. That dark mode request? Now you see it came from one highly engaged user across three apps, not three separate requests. That shifts how you prioritise. It moves you from "three people want this" to "one of our most active users wants this across our entire suite."

But there's a second layer. When someone votes for a feature in App A and you ship it, they get a push notification the moment it lands. In App B too. In App C. They see that you listened. Across your whole portfolio. That's retention magic that doesn't require dark patterns or artificial engagement loops.

The numbers tell a story about who your engaged users actually are

A studio we work with had sixteen apps. They thought their most engaged segment was health-conscious professionals, so they loaded the fitness app with features aimed at that persona. A month after they activated Passport, they discovered their actual power users were different. The people voting across five, six, seven apps weren't using the fitness app at all. They were power users of the productivity and finance apps. The studio pivoted their roadmap. Within two quarters, retention in the finance tier climbed fourteen percent.

That only happens when you can see voter behaviour across your entire portfolio. Most tools can't. They're built around a single app or a single web form. You're stuck in silos.

The data also works the other way. Churn signals show up earlier. If someone was voting across four of your apps and suddenly stops, that's worth investigating. With Passport, it takes thirty seconds to spot. Without it, you won't notice until you look at the raw numbers six months later.

Why SDK matters for this to work

Here's where a lot of tools fall down. They talk about cross-portfolio features but deliver them through web forms. Sign up on our website, vote on a web page, come back next month.

We built Shpd with native SDKs for iOS and Android because voting should live inside your app, not outside it. That sounds like a UX preference. It's actually why Passport works at all.

When voting happens natively, right there in your app, friction disappears. Users don't bounce to a web page. They don't abandon mid-vote. They don't have to remember another login. The same SDK handles authentication across all your apps, so Passport isn't a separate system they have to opt into. It just works.

Studios that tried forcing web-based voting across multiple apps saw maybe twenty percent participation. Participation isn't the point if you want real signal, but low participation means you're missing your most engaged users. The iOS and Android SDKs change that math entirely.

The shifting landscape, and who actually needs this now

We started MRVL because we noticed something: mobile app studios were being left behind by tools built for SaaS companies with one product. Then late last year, another tool hiked their pricing substantially. A lot of studios started looking elsewhere.

If you have two apps, you probably don't need Passport yet. If you have five or more, and you're trying to connect feature feedback across them, it changes everything. The studios that benefit most are those with enough apps to have real portfolio effects, but not so many that they've built their own internal voting systems.

We see this most in gaming studios with multiple titles, productivity app makers, and fitness or wellness portfolios. But it applies anywhere you have a small cluster of mobile apps serving overlapping users.

A quieter kind of value: knowing when to ship, and when to hold

Last month, a studio almost built a calendar feature for their time-tracking app because it had thirty votes. Then they looked at Passport. Same voter had requested it in two other apps they owned. Thirty votes, one user persona, one underlying need. They decided to build a different feature instead, one with broader appeal across the portfolio.

That's not glamorous. It doesn't show up in press releases. But it's the kind of decision that compounds over quarters. You ship fewer things that satisfy a narrow slice and more things that move the needle across your entire user base.

Cross-app voter identity isn't about collecting more votes. It's about understanding votes you already have.