3 ms·
It's a pretty common pattern. When you're small, you have no users, and need to start gathering network effects. So you champion and implement protocols that
by dsp1234 11y ago
It's a pretty common pattern.
When you're small, you have no users, and need to start gathering network effects. So you champion and implement protocols that allow you to interoperate with other networks. You start to eat other companies lunches as you provide a better product.
As you get larger, that same interoperability starts to become a liability as other networks start eating in to your userbase. So you cut out interoperability and start building a walled garden.
- debaserab2 11y agoThat's one thing that I worry about, though. The superior product experience is coming from new centralized services such as Slack and Discord. It's not coming from those building something decentralized.
- vinnyp 11y agoUX always wins. Build a great "open" UX and you have a chance to gain traction. A bottoms up approach where we put the protocol first instead of experience is the "Architect Astronaut" way of looking at solving this problem and should be avoided - http://www.joelonsoftware.com/articles/fog0000000018.html http://www.joelonsoftware.com/articles/fog0000000018.html