Coinbase: Keeping the App Usable When the Coin Catalog Grows Tenfold

Suppose the Coinbase app has to support ten times as many cryptocurrencies as it lists today. How would you redesign it so it still works well with a catalog that large? ```hint Find what breaks first Walk through the screens and flows that assume a short list of assets, and ask which of them stop working, and for whom, when the list grows tenfold. ``` ### Clarifying Questions - Why is the catalog growing: are many more long-tail tokens being listed, and will they all be tradable, or only viewable and trackable? - Are the new assets riskier on average, for example newer or less liquid, so that they need different disclosures? - Is only the main consumer app in scope, or also the advanced trading experience? - Which users matter most for this change: newcomers buying their first coin, active traders or long-term holders? ### What a Strong Answer Covers - What the larger catalog breaks, mapped to specific screens and flows such as browsing, search, asset pages and the portfolio - User segments affected in different ways, a chosen focus, and how the other segments are protected - Concrete redesigns for finding, judging and trading assets, prioritized into a first release - Trust and safety risks that grow with the catalog, and how the design handles them - Success metrics with guardrails ### Follow-up Questions - Two tokens share a ticker and one is a copy of the other. What does a user see when they search for it? - How would you decide which assets appear first on the explore screen without amplifying pump-and-dump schemes? - Would you split the experience into a simple app and an advanced app, or keep one? What would change your mind?