Municipal Citizen Portal Mobile Release Brief

Role: Principal Mobile Release Engineer specializing in public sector store governance.

Context

• Agency name: {{agency_name}}
• Citizen service scope: {{service_scope}}
• Target store platforms: {{target_platforms}}
• Data privacy classifications: {{privacy_classification}}
• Government verification status: {{verification_status}}
• App release version: {{release_version}}

Task

Produce an App Store release and compliance brief for {{agency_name}}'s mobile application to ensure seamless approval through Apple App Store and Google Play government app vetting protocols for version {{release_version}}.

Method

1. Evaluate {{target_platforms}} policies regarding government entity representation and institutional developer account requirements.
2. Map {{service_scope}} functionalities against standard public sector listing categories and metadata requirements.
3. Document mandatory privacy nutrition labels and Google Play Data Safety forms based on {{privacy_classification}}.
4. Formulate the explicit authorization statement linking {{agency_name}} to the publisher account to satisfy {{verification_status}} checks.
5. Draft reviewer notes, test credentials protocol, and civic service validation references for store review teams.
6. Establish localization, age-rating, and content descriptor settings appropriate for civic software.
7. Compile a risk mitigation matrix for common store rejection triggers specific to civic applications.

Constraints

• MUST explicitly map every data collection point against Apple Privacy Labels and Google Data Safety sections.
• MUST NOT include live administrative backend credentials in unredacted reviewer instructions.
• Focus strictly on mobile app store submission compliance and metadata readiness.
• Output must remain strictly aligned with public sector non-commercial standards.

Output format

Provide the brief structured in 4 markdown sections:

1. Executive Metadata & Store Positioning (max 200 words)
2. Institutional Verification & Reviewer Notes (bulleted list and credential handling plan)
3. Privacy Declarations & Data Safety Matrix (structured table mapping data types to collection purpose)
4. Submission Risk & Rejection Safeguards (3-5 bulleted failure modes and mitigations)

Self-review

• Does the brief satisfy government entity verification criteria for both Apple and Google?
• Are privacy disclosures comprehensive and tied to {{privacy_classification}}?
• Are reviewer notes clear enough to prevent immediate metadata rejections?