[bisq-network/roles] Growth Team Lead (#100)

[m52go]

@pazza83 thanks for the compliments. Bisq has many exceptional people contributing to it...my post is not meant to take anything away from any of them. I've had a wonderful time working with everyone.

But I think segmenting an API and daemon as mere development aspects is naive. 

Without an API, the project is forced to grow insularly. As mentioned above, this cuts the project off from integrations, which could not only quickly increase overall traction but also boost overall exposure to whole new markets. Crucially, it also hinders community and contributor growth, since the only way to contribute to Bisq is to work on its big core code base (forced big+intimidating ramp-up time, forced Java, forced conventions...instead of hacking around on something new with full freedom). 

If we disregard the on-chain protocol for a moment, Bisq is incredible software that delivers a solid use-case for hundreds of people every day. The issue is that it's meant to be more of a protocol than a product. For a product stewarded by a traditional company, it would make sense to raise a big round of funding at this point to plow into marketing to drive growth to drive development. But for a protocol, raising funding and doing traditional marketing isn't usually appropriate (or even possible), so integrations are needed. This is how protocols thrive.

I haven't come up with any other ideas for order-of-magnitude growth. I don't doubt that Bisq can grow 10x in its current form, but it will take >10x the effort and >10x the time to do it this way.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/roles/issues/100#issuecomment-974657416
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211120/1853661f/attachment.htm>