App stores
AuraScore 85/100

Civic Health Campaign App Store Positioning and Accessibility Brief

Design an accessible, compliant app store product page brief for public health mobile campaigns.

Use this template when publishing public health, crisis response, or community wellness apps. It guides teams to align store metadata, accessibility standards, and public health credibility requirements.

Template

Role: Civic Tech App Store Optimization (ASO) and Accessibility Director.

Context

  • Public health authority: {{health_authority}}
  • Initiative campaign objective: {{campaign_objective}}
  • Mobile target audience: {{target_demographics}}
  • Supported assistive features: {{assistive_features}}
  • Regional language requirements: {{supported_languages}}
  • Store product page assets: {{listing_assets}}

Task

Produce an App Store product page and accessibility optimization brief for {{health_authority}}'s civic health application to maximize accessibility, algorithmic discovery, and public trust.

Method

  1. Analyze {{campaign_objective}} to establish authoritative, non-sensational public health keyword clusters.
  2. Audit {{listing_assets}} against store guidelines regarding medical misinformation, health disclaimers, and clear attribution.
  3. Define accessibility standards for visual creative assets including color contrast ratios and readable typography for {{target_demographics}}.
  4. Structure localized store listing copy across {{supported_languages}} adhering to civic terminology standards.
  5. Detail the accessibility manifest highlighting {{assistive_features}} in the store description and metadata.
  6. Determine appropriate age ratings, medical advice disclaimers, and crisis hotline link placements.
  7. Formulate a keyword optimization strategy tailored for high-intent search terms within civic categories.

Constraints

  • MUST mandate WCAG 2.1 AA contrast compliance across all store screenshot text and preview graphics.
  • MUST NOT use sensationalized, clickbait, or unverified medical marketing claims in metadata.
  • Keep metadata recommendations compliant with platform public health app policies.
  • Include mandatory health regulatory disclaimers in the copy blueprint.

Output format

Format the output as a brief with 4 distinct sections:

  1. Strategic Keyword & Metadata Architecture (title, subtitle, keyword bank, description copy blueprint)
  2. Accessible Creative Assets Specification (screenshot guidelines, contrast standards, alt-text descriptions)
  3. Multilingual Localization Strategy (table of {{supported_languages}} metadata adaptations)
  4. Regulatory Health Disclaimers & Safety Disclosures (exact disclaimer text and store placement rules)

Self-review

  • Are the keywords appropriate for public sector trust rather than commercial growth hacking?
  • Are visual creative guidelines compliant with accessibility standards?
  • Are public health disclaimers clearly situated to prevent store policy flags?
AuraScore breakdown
85/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering8/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification14/14 · Strong

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-app-stores
public-sector-nonprofit
public-health
aso
accessibility