Skip to main content

WearOS App Pages Standardization Plan

Overview​

This document defines the standardized structure and content guidelines for all WearOS app pages. The goal is to create consistent, user-focused pages that prioritize readability, scannability, and decision-making flow.

Page Structure Template​

Frontmatter (Standard)​

---
title: "[App Name]"
description: "[App] for WearOS with [key features] - [compelling benefit/statistic]"
---

Header & Introduction​

  • H1: App name only
  • Intro paragraph: 1-2 sentences explaining what the app does and its main WearOS benefit
  • Download link: **Download**: [Play Store](URL)  
  • Horizontal divider: ---

Core Section Order (Standardized)​

  1. ### WearOS App Features (Always first - what users want to know immediately)
  2. ### WearOS Compatibility (Second - can I use this?)
  3. ### Getting Started (Third - how do I use it?)
  4. ### [App-Specific Features] (Variable sections based on app complexity)
  5. ### Why Choose [App] for WearOS (Always last - decision reinforcement)

Content Structure Guidelines​

Section Formatting​

  • H3 only for main sections (###)
  • Bold subsection headers on same line as description: **Feature Name** - Description continues...
  • Bullet points for features/lists with bold labels: - **Feature**: Description
  • Paragraph text for explanatory content and context

Bullet Point vs Paragraph Rules​

  • Use bullets for: Features, specifications, steps, comparisons, lists
  • Use paragraphs for: Context, explanations, storytelling, complex descriptions
  • Mix appropriately: 60% bullets, 40% paragraphs for scannability

Divider Usage​

  • Always after download link
  • Only between major logical sections (not within sections)
  • Never more than 3 dividers per page

Required Sections (All Apps)​

WearOS App Features​

  • 2-4 bold subsections highlighting main capabilities
  • Focus on WearOS-specific benefits
  • Use compelling, benefit-focused language

WearOS Compatibility​

  • Technical Details subsection with:
    • WearOS Version number
    • Download size (specific to watch models when available)
    • Android requirements
    • Compatible devices list
    • Special requirements (GPS, NFC, Premium, etc.)

Getting Started​

  • 4-6 numbered steps for setup/first use
  • Focus on WearOS-specific setup
  • Include tile/complication setup when applicable

Why Choose [App] for WearOS​

  • 3 subsections: Market Leadership, WearOS Advantages, [App-Specific Strength]
  • Include download statistics when impressive (1M+)
  • Highlight unique WearOS benefits
  • End with compelling summary paragraph

Optional Sections (App-Dependent)​

Complex Apps (7+ sections)​

  • Feature-specific sections between Getting Started and Why Choose
  • Examples: Spotify Connect, Premium Features, Social Features, etc.

Simple Apps (5 sections)​

  • Stick to core 4 sections only
  • Combine related features into core sections

Writing Style Standards​

Tone & Voice​

  • Professional but accessible
  • Focus on benefits over features
  • Use "you" and "your" for engagement
  • Emphasize convenience and wrist-based interaction

Technical Information​

  • Always include version numbers, file sizes, requirements
  • Use specific device names (Galaxy Watch Ultra, Pixel Watch)
  • Include subscription costs when relevant
  • Mention special hardware requirements (NFC, GPS)

Content Length​

  • Simple apps: 800-1200 words
  • Complex apps: 1200-2000 words
  • Bullet points: 8-12 words ideal, 15 max
  • Paragraphs: 2-4 sentences, focus on scannability

Implementation Checklist​

Page Structure ✓​

  • Correct frontmatter format
  • H1 with app name only
  • 1-2 sentence intro paragraph
  • Download link with proper formatting
  • Horizontal divider after download
  • Sections in correct order
  • H3 headings only for main sections

Content Quality ✓​

  • WearOS-focused benefits throughout
  • Technical details complete and accurate
  • Getting Started section with 4-6 steps
  • Why Choose section with 3 subsections
  • Proper bullet point formatting
  • Mix of bullets and paragraphs (60/40)
  • Professional but accessible tone

Technical Accuracy ✓​

  • Version numbers current
  • Download sizes accurate
  • Device compatibility verified
  • Special requirements noted
  • Download link functional

Success Metrics​

  • Consistency: All pages follow identical structure
  • Scannability: Users can quickly find key information
  • Decision Support: Clear path from discovery to download
  • Mobile Optimization: Readable on small screens
  • Technical Accuracy: Up-to-date compatibility information

Maintenance​

This standardization should be applied to:

  • All existing WearOS app pages (11 total)
  • Any new app pages added to the site
  • Regular reviews for technical accuracy updates
  • Consistency checks during content updates

This plan ensures a user-centered, scannable format that prioritizes the information users need most while maintaining technical accuracy and compelling content.

Last updated on