Not hard coding an app or an option in settings would lead to bad UX. If you’re a new user you won’t have a clue which app to choose on the in-between screen. We need to think of how to best handle this without over complicating it for the user. Sometimes you have to be opinionated in design nostr:note13ml4hwc5z4ekt2zuzmfw7ve05jm4pmucp2yxh0ykwhqszyqaznhsrz9c6a
Discussion
I completely agree. We should try to make it simple for new users and hide some of the complex settings, leaving them for professional users to explore.
I think if you provide an option in settings it’s a good start. I’ll tinker around to see how I can make this less static but not overwhelming.
Hard disagree.
Hardcoding leads to centralization and replicating the old model, it’s how innovation stops.
NIP-89 gives app icon, name, descriptions, WoT ratings and lowers the burden on developers (integrate once, not once per use case + maintain when user behaviors change)