It was 4am yesterday and my brain was dead. Looking back at the conversation, we (you and me and other devs) should definitely work together. But we need to have a rough consensus about what it means to be working together. NIP discussion, codebase etc.

But even before any of these material outputs, we need to figure out what each client dev is trying to do at the first place.

We need to figure out the product difference and similarity among clients. Sometimes, one client, Blowater for instance, might just have very different design goals.

But I can't be certain because we never discussed our design goal, product goal and potentially business goals.

Therefore, 2 suggestions:

1. We should definitely have an in-depth disussion in Tokyo.

2. We should (or mostly I shoud) engage in more public discussions about product designs.

Regarding feature richness, you are right. The current state of Blowater's GM is poor and it's intentional.

The core design is extensible enough to implement many useful and interesting or even weird features on top of it. But in terms of user experience research, I would like to be conservative and only let users to do minimal features at first. Once we have a solid foundation, we will be more confident to implement more features, progressively.

And I firmly believe that Release Small & Release Fast is a superior approach than a longer up-front design circle.