The Importance of Composable Wallets for Users and Developers

Understand the history of Ethereum wallets, what Access Legos are, and the implications of both on the future of dapp development and usability.

I’ve talked about product composability of decentralized applications (dapps) before, but with a fairly simplified diagram of the tech stack:

In reality, there are two layers I skipped (wallets and SDKs) and some added complexity with multi-chain (layer) dapps:

In this article, I will talk about why this extra complexity will lead to a large focus on how composable wallets will matter more and more to both users and developers. Usually, wallets come to mind in the last mile of development when the team decides to embed as many wallet connections as possible (assuming this is a single team tackling both the frontend and smart contract layers of a product). And this is fine since right now most dapps are fairly simple in user interaction (i.e., approve + deposit, bid/buy, or swap). There isn’t much to manage or compose pre/post-interaction.