don't boil the ocean. scope your problem out. web3 is so early it's tempting to build out the whole ecosystem instead of one product. 

there are so many interconnected bits that your idea may have dependencies on other ideas. it would be a mistake to build the full interconnected web of ideas. don't boil the ocean.

running experiments; writing https://kori.ooo

if your idea has too many dependencies, it may be that you are too early. in an emerging industry, there is a natural order to which products materialise. it likely took YouTube to exist before Twitch could.

pacing the evolution of your product to achieve it's final form when the ecosystem is ready for it is key. even more important is the need to have product-market fit at every stage prior to this final form.

𝓓𝓲𝓼𝓽𝓲𝓷𝓰𝓾𝓲𝓼𝓱𝓮𝓭 Engineer at C̶o̶i̶n̶b̶a̶s̶e̶ Yahoo. Yes

Building Design Systems and frontend tools at your favorite internet company like it’s 1999.

aw thanks @jklb.eth 

really i'm talking to myself: web3 must go to mobile, therefore we need mobile dapps, which needs a dapp store, which itself needs a web3 OS. been finding myself trying to do it all