jcdenton.cast
@jc
Never dedicate your business to a platform without expecting them to clone you. Apple is the most famous example of a frenemy, and there are countless examples of this playing out in Silicon Valley. Build the platforms, not the apps.
6 replies
0 recast
15 reactions
Nicholas Charriere
@pushix
I don’t like the “build the platform” mantra. It’s what leads everyone in crypto to build protocols instead of use cases. I prefer “build something with real value, keep delivering more value”. This is another way of looking at what apples doing, as a side note.
1 reply
0 recast
3 reactions
jcdenton.cast
@jc
Apple prefers owning the end to end stack. So for crypto, a product-driven protocol is close to Apple's approach of software-driven hardware.
1 reply
0 recast
1 reaction
Nicholas Charriere
@pushix
+1 as long as you build the product also. for apple: true but remember that being full stack when they started made a lot more sense. If it was easy for Meta to go full stack w hardware from scratch they would do it --> its hard if you don't start there, and its harder as time goes by to start there.
1 reply
0 recast
0 reaction
Evan Hudson
@evan-hudson
I’ve been thinking about this for dMRV sensors as well. My intuition is that hackers/DIY makers will build the early versions and then big tech conglomerates will move in and standardize/scale. (Note: this is only one of many possible timelines)
1 reply
0 recast
0 reaction
ukstv
@
The intuition is widely accepted AFAIK: toy -> repeated solution -> product -> commodity. See https://youtu.be/5AgCLanGSak for example
1 reply
0 recast
1 reaction
Evan Hudson
@evan-hudson
Very interesting presentation. This Wardley fellow seems to know his stuff. I like @ 33:33 when he points out that the design process is a conversation, and that ‘one of the designers is the machine.’ When designing community or nature-based solutions, how do we ensure that community and nature are designers, too?
0 reply
0 recast
1 reaction
