Protocols, not Platforms
Click here to view this newsletter in a web browser
Greetings all,
In this week’s episode of Ventures, I (https://www.linkedin.com/in/wclittle) continue our Product and Code series to talk about Web3 protocol design and Ruby on Rails model/migration construction. I bring up the protocols Farcaster and Lens as examples for product managers to be aware of and learn from when approaching how to build value for the modern web. I also detail how to create a User model in Ruby on Rails, its associated “migration” file, and examples from the Rails Console how to create a user to store in the database.
Check it out: Product: Learning from Lens Protocol and Farcaster. Code: Models and Migrations
Protocols, not Platforms
Borrowed from my friend Andy’s tweet a year ago, I’m a huge fan of people developing protocols in Web3 rather than Web2 “platforms”.
A protocol is like Lens Protocol or Farcaster, where anyone can build a client/app on top of it. This is similar to the protocols behind email, and anyone can build an email app on it.
A platform is old-school Twitter, Facebook, Salesforce, etc… where they silo data and make everyone conform to their standards.
Product designers/developers, think about how you might consider turning your new project idea into a protocol, not a platform.
Have a great rest of your week!
~Will