The Super App Trap
Why trying to be everything usually means being nothing
Every wallet wants to be a super app now.
Start with sending and receiving. Add swaps. Add a browser. Add NFT display. Add staking. Add a social feed. Add messaging. Add fiat onramps. Add a card. Add points. Add quests.
Twelve months later you have forty features and no clarity about what you actually are.
The super app vision is seductive. One app to rule them all. Users never leave. You capture every transaction, every interaction, every moment of attention. The ultimate moat.
In practice it usually creates bloated products that lose to focused competitors on every front.
The WeChat fantasy
Crypto founders love pointing to WeChat. One app for everything. Payments, messaging, social, commerce, services, government interactions. A billion users who never need to leave the ecosystem.
The reference comes up in every pitch deck for wallet infrastructure. We’re building the WeChat of crypto. The super app for web3. The everything interface.
What they miss is context.
WeChat grew into a super app over a decade in a market with specific conditions. Mobile-first population encountering smartphones for the first time. Limited app ecosystem competing for attention. Payment infrastructure that was fragmented before WeChat unified it. Government dynamics that consolidated rather than distributed power.
WeChat didn’t start as a super app. It started as a messaging product. It was the best messaging product in China. From that foundation of daily habit and trust, it expanded carefully into adjacent services. Each expansion made sense given the last.
Crypto has none of these conditions. Users have infinite apps available. Switching costs are close to zero. Wallets are interoperable by design. Your users can take their assets and history to any competitor instantly. The moat you think you’re building doesn’t exist.
But teams keep trying anyway. Because the fantasy is so appealing that it overrides clear thinking about whether it applies.
The focus advantage
Phantom got popular because it was the best Solana wallet. That’s it. One chain, done well. Clean interface. Fast transactions. Reliable when it mattered.
While others were building feature empires, Phantom just made the core experience feel good. They understood that in the early Solana ecosystem, people needed a wallet that worked. Not a wallet that did everything. A wallet that did the essential thing excellently.
Rainbow built a reputation on aesthetics and simplicity. They weren’t trying to do everything. They were trying to be the wallet you actually enjoyed opening. The one that made your NFTs look beautiful. The one that felt like it was designed by people who cared about design.
These products grew because they were excellent at something specific. Users knew exactly what they were getting. The positioning was clear. The promise was clear. The delivery matched the promise.
Compare that to wallets where you open the app and face a grid of icons like a phone home screen. Swap. Bridge. Buy. Earn. Browse. Collect. Stake. Lend. The interface screams “we do everything” which really communicates “we have no idea what we’re best at.”
When you stand for everything you stand for nothing. Users can’t remember what you do. They can’t recommend you clearly to friends. You become generic infrastructure instead of a product with meaning.
The cost of features
Every feature has costs beyond engineering time.
Interface cost. More features means more navigation, more screens, more choices for users to make. Cognitive load increases. The core experience gets buried under options most people don’t use.
Attention cost. Your team has finite focus. Every feature you maintain is attention not spent on your core value proposition. The thing that actually differentiates you gets less love because you’re busy keeping twelve other things running.
Quality cost. You’re now competing on multiple fronts with teams who think about nothing else. Your swap feature competes with Uniswap. Your NFT display competes with dedicated galleries. Your staking competes with protocols built entirely around staking. You’re choosing to be mediocre at ten things instead of excellent at one.
Positioning cost. What do you tell people you do. If the answer takes thirty seconds, you’ve already lost. Clear positioning requires sacrifice. It requires choosing what you’re not.
Support cost. More features means more ways things can break. More edge cases. More user confusion. More tickets. More documentation. The complexity compounds.
Most teams only count the engineering cost. They ship the feature, it works, they move on. The other costs accumulate silently until the product feels bloated and the team feels stretched and nobody can articulate why growth has stalled.
When expansion makes sense
This isn’t an argument against ever adding features. Products should evolve. The question is how.
Expansion makes sense when it serves your core users’ natural next need. Phantom adding swaps made sense. If you’re holding tokens, you’ll want to trade them. The use case is directly adjacent. The trust transfers naturally.
Expansion makes sense when you have a genuine advantage. If your existing infrastructure or relationships or expertise makes you better positioned than alternatives, that’s a real reason to expand. Not just the ability to build it. The ability to be best at it.
Expansion makes sense when it reinforces your positioning rather than diluting it. Rainbow adding better NFT features reinforced their identity as the aesthetic-focused wallet. It made the core proposition stronger.
Expansion doesn’t make sense when it’s driven by competitor feature lists. They added staking so we need staking. That’s not strategy. That’s anxiety.
Expansion doesn’t make sense when it serves a different user than your core user. If your best users are DeFi traders and you add features for NFT collectors, you’re splitting your focus across audiences with different needs. Neither group gets the product they deserve.
Expansion doesn’t make sense when the honest answer to “would someone choose us for this” is no. If you’re just adding table stakes features that everyone has, you’re spending resources to stay in place.
The honest audit
Look at your product right now. List every feature.
For each one ask: if this was a standalone product, would it win?
Be honest. Not “is it acceptable” or “do some users like it.” Would it win against focused competition. Would someone choose you specifically for this capability.
Most super app features fail this test. They exist because they’re easy to add, because competitors have them, because the roadmap needed items, because someone on the team wanted to build it.
That’s not product strategy. That’s feature accumulation.
The features that fail the test are candidates for removal. Or at minimum, for deprioritization. Stop improving them. Let them exist but don’t invest further.
The features that pass the test are your actual product. Double down on them. Make them extraordinary. Let them define what you are.
The path forward
The super app that actually works is the one that earns each expansion.
Core product is excellent. Users love it. They trust you. You understand them deeply. From that foundation, you expand into something adjacent where your existing strengths apply. Each layer built on the last. Each addition making the whole stronger.
The super app that fails is the one that expands because expanding feels like progress. Feature lists growing while user love stays flat. Roadmaps filled with items that look good in investor updates but don’t compound into anything defensible.
Most super app attempts are the second kind. They’re not building toward something. They’re just building.
One thing done exceptionally well beats ten things done adequately. Users will forgive missing features. They won’t forgive mediocre execution of the features you have.
That’s not a crypto insight. It’s just true. Always has been.
The trap isn’t wanting to be a super app someday. The trap is trying to be one before you’ve earned it.
Thank you :)
If your project needs design, brand, product, strategy, and leadership,
let’s talk. Work with me: hi@dragoon [dot] xyz | Follow: 0xDragoon