Closed Bug 1576419 Opened 6 years ago Closed 6 years ago

Google Play Needs All Apps to Declare a Target Audience by September 1st

Categories

(Release Engineering :: Release Requests, task)

Product:
Release Engineering
Component:
Release Requests
Platform:
All
Android
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: colee, Unassigned)

Details

Google Play is requiring all app developers on the Google Play Store to declare a target audience by September 1st. It's not clear what happens if we miss this deadline, but I'd prefer not to find out.

Per Michael Feldmann in legal, we should answer their two questions that our target audience for our browsers is ages 13-18+ and that our app store entries are NOT designed to appeal to children. I went to go ahead and perform this step myself, but I get the message, "An unexpected error occurred. Please try again later. (7)". I believe someone in release management with permission to edit our store entries needs to answer this survey for each of our products on the store individually and that this work should be done soon in case errors are encountered which may require support from Google.

Questions should be directed to Michael Feldmann, Loren Austin, or me.

Flags: needinfo?(rkothari)

To clarify, this is NOT the content rating. It's a new question that Google asks us.

The screen is at: Store Presence -> App content -> Target audience and content -> START

I have done this for Fenix so far. Planning to do the same for all our apps a bit later today.

I have done App content rating for the following apps:

  • Fennec
  • Focus
  • Fennec Beta
  • Firefox Lite
  • Lockwise
  • Fennec Nightly
  • FxR
  • Klar
  • Firefox Send
  • Firefox Send Beta

Please let me know if there are any that I missed. Should I be doing the same thing for org.mozilla.stumbler, org.mozilla.testpilot.notes, org.mozilla.reference.browser?

Flags: needinfo?(rkothari)

Hey Ritu - thanks for taking care of these.

I think we want to do the same thing for Reference Browser and Firefox ScreenshotGo.

I'm not familiar with "stumbler" and testpilotnotes", but if they aren't publicly listed then we shouldn't need to declare the intended audience.

Flags: needinfo?(rkothari)

This was already set for notes, stumbler and reference browser. I've now done the same for ScreenshotGo.

Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(rkothari)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.