This is great debate and it sparks a reflection that must absolutely take place: I’ve been jokingly adding a #fixthenipsystem hashtag since yesterday’s turmoil between Damus and Amethyst. Mind you, I do not know what I am talking about because I have not experienced the NIP system (not contributed to any NIP). So bear with me and forgive me for my outsider’s opinions.
You on the contrary, are bringing potential realistic solutions to the table which should be brought to @fiatjaf imo.
IMO, given the increasing number of users, more and more normies are on those *major clients* now. They don’t know the dev world, they don’t care about the early state of the network. They want to express themselves, bring value, they want their client to work.
If things change too much under their feet, they will compare it to the blue bird crap happening right now and think it’s no better.
Their UX is key to continued adoption. There needs to be some change management considerations and techniques brought into the development lifecycle of those clients.
Lead developers of major clients would benefit from surrounding themselves with UX skilled people. That’s independent, but also intricated with the NIP system: the NIP system should also think about UX if it does not already.