The thing with EULAs in Android apps is that I always click decline. I tend to assume that if an app is including a EULA they're asking permission to do somethi

The thing with EULAs in Android apps is that I always click decline. I tend to assume that if an app is including a EULA they're asking permission to do something egregious so I just uninstall the app because I don't have the time or inclination to actually read the EULA. (Yes, I actually read, or at least skim them when it matters!) Anyway, the guidelines seem fairly easy to meet and pretty inconsequential: > Tell users about your ads—Create a simple, complete disclosure that tells users how your app uses ads, where the ads are shown, and how they can manage ad options. Take common-sense steps to make the disclosure as clear as possible. Do this in the app description on Google Play. > Make sure users know—Present your ads disclosure is an easy-to-see location, rather than hiding it where users are not likely to find it. Do this in the app description also. > Ask for consent (opt-in) at launch—Where possible, include your ads disclosure in the app description as well as in an Ads Terms, End User License Agreement (EULA), or similar document. Display the terms at first launch and ask for the user's consent before continuing to the app. This is optional; don't do it. Any modal dialog that asks for permission to do something is UX friction and EULAs are offputting because they're not the norm on Android. -- The submission title is misleading but I think Google has intended to mislead developers into doing stuff they don't need to do.