Maybe #Nostr devs need to take a week or two off from coding completely and just use the apps they’re building nonstop, take notes, and ask users for feedback. And then spend a week using each other’s apps, and do the same. I bet a lot of problems would get solved that way.
Discussion
Disagree about the stop coding part, but agree with everything else, and a lot of that does already happen. It’s more that there’s more work to do than there is dev time to address the feedback reasonably quickly.
I understand that. But what if the dev cycles were lengthened a bit to all for more R&D between releases? Or do you think it won’t matter because there will still be too many tasks to prioritize?
Short release cycles are the best for reducing issues and gathering user feedback quickly. https://en.wikipedia.org/wiki/Continuous_delivery
🤝
There are more things than can be worked on by team, given dev capacity of full time Will, plus part time Terry and rest of #damusdevs.
1% better each build/day.
I think the go see other client part is super important, for example, profile editors lead end users to have vastly different expectations for the same meta data fields.
Time is often the constraint! Can only do so much in a day.
do devs use each other's apps? would be good thinking
Or you can have a dedicated tester and clear user guidance