google play has a deadline on may 27 that's going to wipe a long tail of indie apps off the store, and the framing of the policy is doing most of the damage. it reads "news and magazine apps must complete a self-declaration in play console" — which sounds like it only applies to the new york times. it doesn't.
if your app pulls articles from a feed, aggregates content from publishers, summarizes news with an llm, or surfaces editorial content of any kind, you are probably "in scope" by google's definition. the deadline is 19 days from today, and apps that miss it get removed.
What Google actually means by "news and magazine"#
the in-scope category is broader than the obvious one. google's own examples include rss readers, news aggregators, podcast apps with editorial content, blog readers, and any app whose primary value is delivering articles, opinion, journalism, or magazine-style content — including ai-summarized versions of someone else's reporting.
if your app sits there and you haven't filed, the enforcement isn't a warning email. it's a takedown.
The self-declaration itself is fast#
the form is in play console under app content → news app declaration. you confirm whether your app produces original journalism, aggregates third-party content, or both, and you provide a publisher contact. ten minutes if you have the inputs ready.
what trips people up is what's behind the declaration:
- if you aggregate third-party content, google wants a link to your content licensing or attribution policy. "we just use the rss feed" is not a licensing position; it's a future cease-and-desist.
- if you produce original content, google wants editorial standards documented somewhere on your site. a one-pager about your editorial process is the minimum.
- if your app uses ai to summarize or rewrite published articles, google's policy around generative content means you need a disclosure that the summaries are ai-generated. the summarized version still counts as "your" editorial output, which means standards apply.
Why this is going to hit indie devs hardest#
big publishers saw this in april and started compliance work. indie devs see the email, decide it doesn't apply because they "don't have a magazine," and skip it. then the takedown lands and they're declaring on a removed listing, which is a slower process than declaring on a live one.
the higher-risk category is the new wave of ai news-summarization apps that shipped in q1 and q2. most aggregate from third-party sources, run the content through an llm, and surface the rewritten version. that puts them squarely in scope and most have no editorial process documented anywhere.
if you built any of the following in the last six months, file the declaration this week:
- an rss reader with summarization
- a "news for [topic]" app powered by a generative model
- a publisher dashboard or aggregator
- a podcast app that surfaces transcripts or written summaries
- a finance, sports, or politics tracker that pulls articles
The Stora angle#
stora's compliance engine flags indie apps in our pipeline that look like they fall into google's expanded news category and surface the declaration as a pre-submission step. it's the same pattern as the privacy manifest checks we run for ios — most rejections are not because the developer disagrees with the policy, but because they didn't realize the policy applied to them. catching it before submission is cheaper than recovering from a takedown.
if you're building anything that touches editorial content for android, file the declaration this week. the deadline doesn't get extended a third time.