Most of the policies are related to App UI, more or less, since this is the problem we are currently focusing on.
Topics:
android-developer >
Core app quality >
Visual design and user interaction >
Text: The app does not redefine the expected function of a system icon (such as the Back button).
Topics:
android-developer >
Core app quality >
Visual design and user interaction >
Text: The app uses notifications only to: Indicate a change in context relating to the user personally (such as an incoming message), or Expose information/controls relating to an ongoing event (such as music playback or a phone call).
Topics:
android-developer >
Core app quality >
Visual design and user interaction >
Text: Audio does not play behind the lock screen, unless this is a core feature.
Topics:
android-developer >
Core app quality >
Visual design and user interaction >
Text: With StrictMode enabled (see StrictMode Testing, below), no red flashes (performance warnings from StrictMode) are visible when exercising the app, including during game play, animations and UI transitions, and any other part of the app.
Topics:
android-developer >
Core app quality >
Visual design and user interaction >
Text: The app supports power management features in Android 6.0+ (Doze and App Standby) properly. In the case where core functionality is disrupted by power management, only qualified apps may request an exemption.
Topics:
android-developer >
Core app quality >
Visual design and user interaction >
Text: The app uses strong, platform-provided cryptographic algorithms and does not implement custom algorithms.
Topics:
AdMob Help >
AdMob policies and restrictions >
Implementation guidance >
Banner ad guidance >
Text: banner ads should not be placed next to interactive buttons, such as a "next" button or a custom app menu bar, next to interactive content such as a text chat box or an image in an image gallery, or on a game play screen where users are continuously interacting with the app. Separating the banner ad from app interactive elements helps reduce user confusion and accidental clicks.
Topics:
AdMob Help >
AdMob policies and restrictions >
Implementation guidance >
Banner ad guidance >
Text: Ads should not be placed on a 'dead end' screen. There must be a way to exit a screen without clicking the ad (for example, a "back" or "menu" button). Otherwise, the user should be notified that the home button will exit the app.
Topics:
AdMob Help >
AdMob policies and restrictions >
Implementation guidance >
Interstitial ad guidance >
Text: Do not place interstitial ads when exiting apps
Topics:
AdMob Help >
AdMob policies and restrictions >
Implementation guidance >
Interstitial ad guidance >
Text: Ads should not be placed in applications that are running in the background of the device or outside the app environment. It should be clear to the user which application the ad is associated with or implemented on.
Topics:
AdMob Help >
AdMob policies and restrictions >
Implementation guidance >
Interstitial ad guidance >
Text: Don't surprise users with interstitial ads. Placing interstitial ads so that they suddenly appear when a user is focused on the task in hand (e.g. playing a game, filling in a form, reading content) may lead to accidental clicks and often creates a frustrating user experience. For this reason, interstitial ads should only be implemented at logical breaks in between your app's content (e.g. pages, stages or levels) to ensure that the user is prepared to engage with the ad.
Topics:
AdMob Help >
AdMob policies and restrictions >
Implementation guidance >
AdMob native ads policy compliance checklist >
Text: Include one of the following ad attributions within the ad:
- "Ad" (can be localised)
- "Advertisement" (can be localised)
- Badge that says "AD" and is at least 15 x 15px (can be localised)
Topics:
AdMob Help >
AdMob policies and restrictions >
Implementation guidance >
AdMob native ads policy compliance checklist >
Text: For app install ads
- Include the headline in the ad creative.
- Ensure that there is no truncation of text up to 25 characters.
- Include the app icon in the ad creative.
- Include a call-to-action button that users can click on to download/install the app. We will provide the text asset. You can optionally use an app download icon instead.
Topics:
AdMob Help >
AdMob policies and restrictions >
Implementation guidance >
Text: Implement ads where users are expected to be less engaged with the content of the app, such as in transition points of a reading app, or in between levels of a gaming app.
Topics:
AdMob Help >
AdMob policies and restrictions >
Implementation guidance >
Text: Incentivising users in any way to click links and/or non-AdMob ads is also prohibited
Topics:
AdMob Help >
AdMob policies and restrictions >
Implementation guidance >
Text: You should also avoid placing ads on an app screen when users do not have their attention on the screen. For example, if you have a utility app such as a torch app, ads should not be on the screen whilst the torch is in use.
Topics:
AdMob Help >
AdMob policies and restrictions >
Implementation guidance >
Text: If users navigate to and from pages with ads in an app over a short period of time, a new ad request should not be made sooner than the recommended 60 second rate.
Topics:
GDPR >
EU Consent Requirements in AdMob >
Text: Ads served by Google can be categorized as personalized or non-personalized, both requiring consent from users in the EEA.
Topics:
GDPR >
Text: When consent is being used as the legal basis for processing personal data users should have the right to withdraw their consent at any time
Topics:
material-design >
Components >
sheets-bottom >
Text: Standard bottom sheets are elevated above the main UI region so their visibility is not affected by panning or scrolling.
Topics:
material-design >
Components >
sheets-bottom >
Text: Place supporting features, such as chat, in an expanding bottom sheet. In this example, an expanding bottom sheet allows users to switch between viewing a product and contacting customer service.
Topics:
material-design >
Components >
bottom-navigation >
Text: Transition between active and inactive bottom navigation destinations using a cross-fade animation.
Topics:
material-design >
Components >
navigation-drawer >
Text: A navigation drawer sheet can open from the left side of the screen for left-to-right languages (1), or from the bottom of the screen when paired with a bottom app bar (2). Scaled down to 62.5%
Topics:
material-design >
Components >
selection-controls/#switches >
Text: Checkboxes let users select one or more options from a list. A parent checkbox allows for easy selection or deselection of all items.
Topics:
material-design >
Components >
dialogs >
Text: A “Close” button (1) is vague because it does not indicate whether changes will be saved or discarded.
Topics:
material-design >
Components >
dialogs >
Text: Don’t include dismissive actions like “Cancel” in a simple dialog. Users can tap anywhere outside the dialog to close it.
Topics:
material-design >
Components >
dialogs >
Text: Find ways to shorten app bar text, and place longer titles into the content area (1) of a full-screen dialog.
Topics:
material-design >
Components >
lists >
Text: Place a divider between rows with lots of content, such as those with three-line lists.
Topics:
material-design >
Components >
buttons >
Text: Use a contained button in a bottom sheet next to other important details.
Topics:
material-design >
Components >
buttons >
Text: A button container’s width is dynamically set to fit its text label.
Topics:
material-design >
Components >
app-bars-bottom >
Text: Inset a snackbar or toast above a bottom app bar and FAB.
Topics:
material-design >
Components >
sheets-side >
Text: Place side sheets along the left or right edge of the screen.
Topics:
material-design >
Components >
selection-controls/#checkboxes >
Text: Don't use radio buttons to toggle items on or off. Radio buttons convey that a set of items are options, and that only one can be selected at a time.
Topics:
material-design >
Components >
banners >
Text: Don’t include links in a banner message. All available actions should be represented as buttons.
Topics:
material-design >
Components >
banners >
Text: Avoid stacking multiple banners.
Topics:
material-design >
Components >
banners >
Text: Don’t use a close affordance icon as the only method of dismissing a banner. All actions should be shown as text buttons.
Topics:
material-design >
Components >
navigation-rail >
Text: Do not truncate or display an ellipsis in place of label text.
Topics:
material-design >
Components >
text-fields >
Text: Don’t design text fields to look similar to buttons, as they could be mistaken for buttons.
Topics:
material-design >
Components >
image-lists >
Text: Quilted image lists shouldn’t display text below the image container, as it disrupts the layout.
