Thesis 1: A new design pattern for Web 3 native consumer apps

Every generation of apps has introduced a new design pattern that creates new business models. While in Web 2 and legacy finance, design patterns have largely been constrained to offer a uniform experience for different use cases, in Web 3 the nascent design space and composability allow different design patterns to be used for different use cases.

Examples:

• Twitter offers the same content interface for all Twitter communities and content types. Businesses advertising on the platform can only embed links to articles and websites and cannot offer customized experiences to customers to interact with their offerings.

• Amazon offers the same type of presentation of product for all merchandise sold on Amazon's marketplace. Buyers can only learn about a product the way Amazon prescribed, regardless if it's a collectible or a piece of clothing.

However, we believe Web 3 consumer-facing apps can offer context-specific experiences for each individual use case. Imagine:

• Trading: A user is viewing a trader's post on their latest investment, the post has buy and sell buttons directly attached to the content;

• Collectibles: A user is showcasing a recent collectible they just purchased for collecting, a price history chart is directly attached to the picture of the collectible;

• NFT creator community: A creator is talking about how amazing their community is and is encouraging people to join, a "Join" button shows directly under the post for people who are qualified to join based on an on-chain verifiable ownership of the NFT.

We can expand the use cases to anything that involves an experience, be it a purchase, an investment, or a social experience (virtual or IRL).

We believe the advantage of Web 3 lies in the immense composability of the software that can power the immense contextualization of the UIUX that provides highly customized experiences for users. This is an experience customization upgraded by orders of magnitude that no Web 2 applications can achieve. Theoretically, there should be no limit as to which experiences can be supported as long as there's a corresponding primitive that supports it.

To dive deeper into why and how experiences are powered natively in Web 3 in the backend, take a look at our second thesis: Building new primitives to power new experiences.