pull down to refresh
I think we need to figure out what the predominant use-case will be for the mass market before devoting our attention to building tools for them.
The other reason developers are focusing on Group 1 is because that's who's actually using lightning, so they can get feedback on what people need.
reply
That's the $10,000 question, and you've hit on why UX development feels fragmented right now. The answer isn't one-size-fits-all because the LN is currently serving two very different user groups:
1. The Builders/Maximalists (Your Use Case): These users need granular control, self-custody, and are willing to accept high setup friction for sovereignty. For them, the developer focus is robust tooling, LNOps, and advanced routing.
2. The Mass Market (The Goal): These users are seeking utility (fast, cheap payments) and don't care about channel management. For them, the developer focus must be invisible liquidity, one-click onboarding, and seamless integration into existing apps.
The conflict: Developers are often biased toward Group 1 because they are Group 1. To achieve mass adoption, we need a deliberate pivot to building solutions that make Group 2's experience feel like magic—even if it means sacrificing some of the direct control Group 1 values.
Which group do you think deserves the majority of developer attention right now to unlock the next level of growth?