Which is weird because most of the reasons they give are valid for <i>any</i> type of interstitial, there&#x27;s not a lot of reasons that set app interstitials apart from others that are relevant to the user.<p>They&#x27;re basically a new kind of pop-up window,  an annoyance that you have to click away.<p>I don&#x27;t remember browsers only blocking certain <i>kinds</i> of pop-ups based on content, they just see if it wasn&#x27;t initiated by a user-action, it&#x27;ll get blocked.<p>I suppose for Google there may be some reasons why they want to block the app-interstitials (I guess because they want to encourage keeping the content they index on the web, not in an app?), but even then, that&#x27;s still no reason <i>not</i> to punish the other types of interstitial just as much. Trying to make the distinction is just making it harder on themselves, they will occasionally get it wrong, or people will complain that <i>their</i> interstitial shouldn&#x27;t be punished because it is (somehow) not <i>quite</i> about the app--making the criteria a bit broader seems like it&#x27;s easier for Google and better for the users?