Key Takeaways
- Australia recently imposed a ban preventing under-16s from accessing a select "top 10" social media applications.
- Snap CEO Evan Spiegel highlighted severe implementation challenges, arguing the ban's narrow scope creates massive loopholes.
- Spiegel explained that young users can easily bypass the restrictions by migrating to "clone services" or any of the “millions of apps in the app store” not covered by the regulation.
- This specific instance illustrates the difficulty of regulating rapidly evolving digital behaviors at the individual app level.
- For builders, it's a stark reminder that user demand and technical availability will often find ways around prescriptive, limited controls.
The Futility of Narrow Regulation
John Collison kicked off the conversation by asking Snap CEO Evan Spiegel about Australia's recent move to “blanket ban under 16s from the top 10 or some number like that social media apps.” It sounds like a decisive policy, a clear line drawn in the sand. But Spiegel quickly punctured that illusion, stating plainly, “I think there are a lot of challenges with the way that the ban was implemented.”
His core critique? The ban's scope is too narrow. It targets a handful of high-profile apps, assuming that controlling the big players will control the behavior. Spiegel notes that the regulation “only applies to a small number of apps.” This isn't just an oversight; it's a fundamental misunderstanding of the digital ecosystem. In a world with "millions of apps in the app store," banning ten is like bailing out a sinking boat with a teacup. The water still rushes in.
The "Clone Service" Problem
Spiegel then laid out the practical consequence for young users. If a teenager wants to keep using services similar to Snapchat, he explained, they don't hit a dead end. “You can just use a clone service that isn't under... doesn't fall under” the ban. Collison picked up on this, asking if “just a bunch of direct clones popped up basically.” Spiegel didn't confirm exact numbers but pointed to the sheer volume of “plenty of alternative millions of apps in the app store.”
This highlights a brutal reality for regulators: user demand, when unmet by official channels, will often create its own. If a service is desired, especially by a demographic known for its tech savviness, the market will provide it. This isn't a moral judgment, just an observation on how digital ecosystems operate under pressure. Banning a name doesn't ban a function or a need.
A Hard Lesson for Builders
For founders in their 20s and 30s, this isn't just a political debate; it's a masterclass in market dynamics and the limits of control. If you're building a product in a space that might attract regulatory scrutiny, or even just thinking about how users interact with your own rules, this offers a sharp lesson. Spiegel’s point about applying a ban "at the app level" underscores that targeting specific entities rather than the underlying patterns or technologies is often ineffective.
Consider a scenario where your platform implements a strict content policy. If that policy is too narrow, users will simply find — or build — an alternative. If you're building a marketplace, and you try to ban specific types of transactions, expect users to innovate around those bans if the demand is strong enough. The "millions of apps" principle applies to user-generated solutions, alternative communication channels, or even just cleverly disguised workarounds within your own system.
What to Do With This
Next week, map out the "regulatory surface area" of your own product or service. Ask: If a regulator or even just an internal policy team tried to restrict a core function of what you're building, how many immediate, obvious workarounds exist? Instead of just thinking about compliance, strategize for circumvention. Anticipate how users — and competitors — will respond to friction. Then, design your product or policy with those vectors in mind, building for resilience rather than relying on brittle, easily bypassed "app-level" controls.