daniel on Nostr: Been watching this almost daily. From a product management POV it's part of the ...
Been watching this almost daily. From a product management POV it's part of the immense task of finding product market fit which means a mix of savvy UX and inclusive pluralist appeal to a wide variety of people. Janky alphas and betas can't sustain much recurring use.
The tech-centered protocol culture here has a huge capacity for this as long product and design craft also come on board to take on wider user needs and requirements for distributed web cooperation, to support deep pluralistic inclusive experience, and increase overall cultural diversity.
It's still early days. All this launch data so far in this chart, the rate of growth, offers validation that there's a there-there to further cultivate. But full-on community-centered product strategy and design are required, in addition to foresight in how the engineering of the architecture can support wider needs. Any good product so much more than the technical architecture, the tech side of things is maybe 20% of the solution fit... you need research, product strategy, design, marketing, community engagement, etc.
Just like Mosaic was the client app to demo HTTP viability and validate it, it wasn't until Netscape that we got a better product-market fit for HTTP to cross the chasm. So many products fail because they get stuck within this early adopter geek side of the chasm, and fail to connect with 90% of the potential users.
The tech-centered protocol culture here has a huge capacity for this as long product and design craft also come on board to take on wider user needs and requirements for distributed web cooperation, to support deep pluralistic inclusive experience, and increase overall cultural diversity.
It's still early days. All this launch data so far in this chart, the rate of growth, offers validation that there's a there-there to further cultivate. But full-on community-centered product strategy and design are required, in addition to foresight in how the engineering of the architecture can support wider needs. Any good product so much more than the technical architecture, the tech side of things is maybe 20% of the solution fit... you need research, product strategy, design, marketing, community engagement, etc.
Just like Mosaic was the client app to demo HTTP viability and validate it, it wasn't until Netscape that we got a better product-market fit for HTTP to cross the chasm. So many products fail because they get stuck within this early adopter geek side of the chasm, and fail to connect with 90% of the potential users.