The editorial argues the compliance calculus is well-understood: platforms like Salesforce and Stripe concluded that maintaining a separate California code path costs more than shipping the strictest ruleset globally. This bill is the UX-pattern version of that same convergence story, and consumer apps will likely strip infinite scroll and autoplay for all users rather than build California-specific flows.
Turning off infinite scroll is trivially a feature flag — the hard problem is knowing which users are minors. Once the statute puts liability on the platform for getting age wrong, self-declared signup age becomes legally worthless, forcing platforms into government-ID verification or similarly invasive alternatives that create their own privacy problems.
The submitted SFGate article positions Meta as the obvious target, reflecting the common political framing of teen-safety legislation as an anti-Facebook/Instagram measure. The 126-point score and 215 comments suggest strong resonance with the framing that Big Social is the intended defendant here.
The editorial pushes back on the Meta-only framing, noting the statutory language is generic and applies to any platform serving algorithmically-ranked feeds to California minors. That means the compliance burden lands on every consumer app with a feed, not just the named villains.
A California bill working its way through Sacramento would require social platforms to strip infinite scroll, autoplay, and late-night push notifications from any account belonging to a user under 18. The SFGate report frames it around Meta as the obvious target, but the statutory language is generic — it applies to any platform that serves algorithmically-ranked feeds to minors in California.
The specific prohibitions are the ones a product manager would recognize on sight: automatic loading of new content when the user reaches the bottom of a feed, autoplaying video without an affirmative tap, and any push notification sent between 10pm and 6am local time to a known-minor account. Platforms would also be required to default minor accounts to private, disable algorithmic recommendation of accounts they don't follow, and provide parental controls with usage-time reporting.
The teeth are in the enforcement model: the bill puts the burden of knowing a user's age on the platform, not on the user's honest self-declaration at signup. That's the part that turns a teen-safety bill into an infrastructure mandate for every consumer app.
California has done this before, and the pattern is well-understood. CCPA became the de facto US privacy baseline because Salesforce, Stripe, and every mid-sized SaaS shop concluded that maintaining a separate California code path was more expensive than shipping the strictest ruleset globally. GDPR forced the same convergence in 2018. This bill is the UX-pattern version of that story, and the compliance calculus will look identical.
The interesting technical question isn't 'can you turn off infinite scroll' — of course you can, it's a feature flag. The interesting question is how do you know who's a minor. Self-declared age at signup is legally worthless once a state statute puts liability on the platform for getting it wrong. That leaves three real options: government-ID verification (privacy nightmare, conversion killer), inference from behavioral signals (regulatorily untested, ethically loaded), or third-party age-assurance vendors like Yoti or Incode (adds vendor risk and a per-check cost that scales with DAU).
The UK's Online Safety Act already forced this decision on Pornhub, Reddit, and Wikipedia in July 2025 — Wikipedia is currently in court arguing that mandatory age verification would break the site's operational model. California's version is narrower in scope but broader in reach, because it targets the design patterns rather than the content. A knitting forum with an infinite-scroll feed and any minor users would technically be in scope.
The industry response so far has been the familiar split. NetChoice — the trade group representing Meta, Google, and X — is preparing a First Amendment challenge on the theory that recommendation algorithms are protected editorial speech, an argument the Supreme Court partially endorsed in *Moody v. NetChoice* (2024). Common Sense Media and the state AG's office are pointing to the mounting internal-research disclosures from Meta and TikTok showing the platforms knew these patterns produced measurable harm in minor cohorts.
What's genuinely new here is that the bill regulates *interaction patterns* rather than *content*, which sidesteps the First Amendment terrain the platforms have been winning on. You can argue that a recommendation is speech. It's much harder to argue that automatically loading the next batch of recommendations without a user gesture is speech.
If you ship a consumer web or mobile product that could plausibly have California minor users, three things move onto your roadmap the day this becomes law.
First, age assurance as a platform primitive. Not a signup checkbox — an actual signal you can gate feature rollouts on. If you're building anything with a feed, this is the same architectural discipline as building a permissions system: assume from day one that some users will have restricted feature sets and some won't, and design the client and server so the restrictions are enforceable server-side rather than hidden behind a client-side toggle. Rolling this in retroactively is where the eight-figure remediation budgets come from.
Second, feed pagination gets a legal dimension. The technical work to replace infinite scroll with paginated 'load more' is trivial — one afternoon for most stacks. The product work to convince a growth team to ship it to any cohort is not. Expect the design conversation to shift from 'infinite scroll increases session length by 23%' to 'infinite scroll on minor accounts is a per-violation civil penalty,' and budget the A/B test accordingly. The engineers who've already built dual-mode feeds for the UK OSA compliance push have a head start.
Third, push notification scheduling needs a timezone-aware quiet-hours layer for a subset of accounts. This is boring, but it's the kind of boring that eats a sprint if the notification service was built assuming a single global send policy. If your notification service already supports per-user quiet hours (Braze, OneSignal, Customer.io all do), you're fine. If you rolled your own on top of APNs and FCM, you have work to do.
The broader shift is that consumer product surfaces are becoming regulated the way financial and health surfaces already are — with per-jurisdiction feature matrices, mandatory audit logs, and a compliance sign-off in the release pipeline. Frontend engineers who spent the last decade optimizing conversion funnels are about to spend the next decade documenting why each pattern is or isn't in scope of some state statute.
The bill's near-term fate is uncertain — California has passed several similar measures (AB 2273, the Age-Appropriate Design Code Act) that were promptly enjoined on First Amendment grounds, and NetChoice will run the same play here. But the direction of travel is unambiguous: the UK, EU, Australia, and roughly a dozen US states are converging on the same regulatory pattern of treating engagement-maximizing UX as a harm vector for minors. Engineers building consumer products should plan for a future where infinite scroll, autoplay, and unrestricted push notifications become opt-in adult features rather than defaults, and where age assurance is a platform-level requirement rather than a nice-to-have. The teams that build this into their architecture proactively will ship faster than the ones patching it in under a consent decree.
We can all agree that the internet was great and now it is less great, but the second someone articulates a very, very simple rule, the "well ackchyually" crew comes out of the woodwork.Infinite scroll is very obviously unnecessary. It is very obviously intended to keep people on an app lo
Instead of trying to whack a mole on all addictive mechanisms, just ban the business model driving all of them: targeted advertising.
I've heard a lot of negative talk about Californian politicians, but compared to how the discussion is going on in Norway about the same issue, this is great. It's very refreshing to see politicians actually understand the problem at hand instead of just throwing age checks at it.For refer
It should just be universally required to give an option to disable addictive features. Should prevent age verification, and giving users optionality is always a good thing (for them).
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
Curious as to where the line between “addictive feature” and "good UX" is. Is deliberate pagination actual impedance to use or merely an annoyance that's been weeded out with modern UX design?When does a feature that simply makes your product easier to use cross into a territory that