Skip to content

Instantly share code, notes, and snippets.

@developdaly
Last active February 11, 2026 15:39
Show Gist options
  • Select an option

  • Save developdaly/facd1716099d118590f694940da7b829 to your computer and use it in GitHub Desktop.

Select an option

Save developdaly/facd1716099d118590f694940da7b829 to your computer and use it in GitHub Desktop.

PRD: Try-Based Strategies Redesign

Project: Frankly Homescreen Content Model Redesign
Author: Product & Engineering
Date: February 10, 2026
Status: Draft for Review
Branch: feature_next_try


Executive Summary

We are redesigning the Frankly homescreen content model to introduce Strategies - grouped sets of actionable content cards that help parents practice connection skills. This replaces the current single-resource-per-category model with flexible, multi-card experiences that combine dialogue prompts, mindset shifts, and media resources into cohesive daily practices.

The new model enables:

  • Grouped learning experiences (SAY + THINK + LISTEN/WATCH cards bundled as one Strategy)
  • Social proof through real-time engagement counts ("124 others trying this today")
  • Flexible content scheduling supporting both grouped Strategies and standalone cards
  • Simplified content creation with unified ContentCard model replacing separate TextPrompt/AudioResource/VideoResource models

Goals & Objectives

Primary Goals

  1. Increase daily engagement by presenting content in actionable, bite-sized "Strategies" that feel achievable
  2. Improve content comprehension by grouping related concepts (what to say + why it matters + supporting media)
  3. Drive social motivation through peer engagement metrics visible on each Strategy
  4. Simplify content production for the content team with unified creation workflows

Success Metrics

  • Weekly Active Users: % of users who login at least once per week
  • Engagement rate: % of users who watch or listen to a video
  • Try This Engagement rate: % of users who click "TRY THIS" on at least 1 Strategy per day
  • Completion rate: % of Strategies marked complete vs. saved

User Personas & Use Cases

Primary Persona: Sticky Note Users

Scenario: Morning routine before kids wake up

  • Opens Frankly app at 6:15 AM
  • Sees "3 Strategies for Connection Today" with clear groupings
  • Reads SAY THIS phrase, internalizes THINK THIS mindset
  • Taps play on LISTEN TO THIS audio (5 min guided practice)
  • Clicks TRY THIS button to commit, sees 87 other parents also trying
  • Returns during afternoon conflict to recall the phrase

This user is likely in the thick of it. They don't have time for a 10-minute deep dive; they need the "cheat sheet." They treat the app like a digital lighthouse during a storm. Motivation: Immediate de-escalation and practical application.Behavior: They deep-link directly to the "Next Try" to find the specific "say" script. They value the "Coach in your pocket" aspect above all else.

By making the say/think accessible from the very beginning, my hope is that we are giving them value from the first seconds they open the ap

Secondary Persona: Content Creator (Internal Team)

Scenario: Scheduling content for upcoming week

  • Creates new Strategy theme: "Big Emotions Week - Day 3"
  • Selects SAY phrase: "It's okay to be angry"
  • Adds THINK card: "Feelings aren't emergencies"
  • Attaches WATCH video: "Big Emotions" (already uploaded)
  • Schedules Strategy for Tuesday Feb 10
  • Previews homescreen view before publishing

Functional Requirements

F1: Content Card Management

Priority: P0 (Blocker)

  • F1.1 System shall support five card categories: SAY THIS, THINK THIS, LISTEN TO THIS, WATCH THIS, ASK THIS
  • F1.2 Each ContentCard shall have title, content/body, duration (optional), and state (draft/published/hidden)
  • F1.3 LISTEN cards shall support audio file upload, transcript, VTT captions
  • F1.4 WATCH cards shall support video file upload, cover image, VTT captions
  • F1.5 All text content shall support English and Spanish translations
  • F1.6 ContentCards shall be reusable across multiple Strategies
  • F1.7 Admin interface shall conditionally show media upload fields based on category

F2: Strategy Management

Priority: P0 (Blocker)

  • F2.1 Strategy shall contain 3-4 ContentCards with explicit position ordering
  • F2.2 Strategy shall require at minimum: 1 SAY or THINK card, 1 LISTEN or WATCH card
  • F2.3 Strategy shall have optional theme/title field for admin reference
  • F2.4 Strategy shall support draft/published/hidden states
  • F2.5 Strategy shall be schedulable to multiple DailySchedules
  • F2.6 Admin shall preview Strategy layout before publishing

F3: Homescreen Display

Priority: P0 (Blocker)

  • F3.1 Homescreen shall display 2-3 Strategies per day from DailySchedule
  • F3.2 Each Strategy shall render cards in position order
  • F3.3 Strategy shall display "TRY THIS" button at bottom
  • F3.4 Strategy shall show real-time count: "X others trying this today"
  • F3.5 Standalone ASK cards shall render below Strategies
  • F3.6 Empty state shall redirect to Library if no content scheduled

F4: Engagement Tracking

Priority: P0 (Blocker)

  • F4.1 TRY THIS button shall create UserActivity record (name: "strategy.intention")
  • F4.2 Button shall disable and show checkmark after click
  • F4.3 Social proof count shall update optimistically on click
  • F4.4 Count shall query distinct users who clicked their intention to Strategy today

F5: Content Scheduling

Priority: P1 (High)

  • F5.1 DailySchedule shall support scheduling multiple Strategies with position ordering
  • F5.2 DailySchedule shall support scheduling standalone ContentCards (ASK category)
  • F5.3 Scheduled content shall filter by tags per existing pattern
  • F5.4 Admin shall preview full day's homescreen before publishing
  • F5.5 System shall support scheduling same Strategy to multiple dates

User Interface Specifications

Homescreen Layout (Mobile)

┌─────────────────────────────────────┐
│ [Frankly Logo]                      │
├─────────────────────────────────────┤
│ Tuesday, Feb 10 • 3 Strategies for  │
│ Connection Today                    │
├─────────────────────────────────────┤
│ ┌─────────────────────────────────┐ │
│ │ SAY THIS                        │ │
│ │ ┌─────────────────────────────┐ │ │
│ │ │ I'm here when you're ready. │ │ │
│ │ └─────────────────────────────┘ │ │
│ │                                 │ │
│ │ THINK THIS                      │ │
│ │ │ Calm is contagious.           │ │
│ │                                 │ │
│ │ LISTEN TO THIS                  │ │
│ │ Take a Pause      [Transcript]  │ │
│ │ [▶ ━━━━━━━━ 0:00/7:05]          │ │
│ │                                 │ │
│ │        [TRY THIS]               │ │
│ │ 124 others trying this today    │ │
│ └─────────────────────────────────┘ │
│ ┌─────────────────────────────────┐ │
│ │ SAY THIS                        │ │
│ │ ┌─────────────────────────────┐ │ │
│ │ │ It's ok to be angry.        │ │ │
│ │ └─────────────────────────────┘ │ │
│ │                                 │ │
│ │ THINK THIS                      │ │
│ │ │ Feelings aren't emergencies.  │ │
│ │                                 │ │
│ │ WATCH THIS                      │ │
│ │ Take a Pause      [Transcript]  │ │
| | ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■| |
| | ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■| |
| | ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■| |
| | ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■| |
| | ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■| |
| | ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■| |
| | ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■| |
│ │                                 │ │
│ │        [TRY THIS]               │ │
│ │ 74 others trying this today     │ │
│ └─────────────────────────────────┘ │
│                                     │
│ ┌─────────────────────────────────┐ │
│ │ ASK THIS                        │ │
│ │ What's something that made      │ │
│ │ you smile today?                │ │
│ └─────────────────────────────────┘ │
└─────────────────────────────────────┘

Acceptance Criteria

Customer-Facing

  • User sees 2-3 grouped Strategy cards on homescreen for today's date
  • Each Strategy shows SAY + THINK + LISTEN/WATCH in correct order
  • TRY THIS button disables and shows checkmark after click
  • Social proof count displays and updates optimistically
  • Standalone ASK cards render below Strategies
  • Audio player works in LISTEN cards with CC/transcript toggle
  • Video player works in WATCH cards with CC toggle
  • Spanish translations display when locale set to es
  • Empty state redirects to Library when no content scheduled
  • Layout matches prototype on iPhone 14 Pro viewport

Admin-Facing

  • Admin can create ContentCard with category selection
  • Media upload fields show/hide based on category
  • Admin can create Strategy and associate 3-4 ContentCards
  • Strategy creation validates minimum card requirements
  • Admin can schedule Strategies to DailySchedule with position ordering
  • Admin can schedule standalone ASK cards
  • Preview shows accurate homescreen rendering
  • Draft Strategies do not appear on homescreen
  • Published Strategies appear immediately on scheduled date

Appendix

Related Documents

Glossary

  • Strategy: Grouped set of 3-4 ContentCards forming one actionable practice
  • ContentCard: Single piece of content (text prompt or media) with category designation
  • DailySchedule: System for scheduling content to appear on specific dates
  • Product Label: Tag to filter content (ex. child, teen)
  • Social Proof: Display of peer engagement ("X others trying this")
@candisgrover-hub
Copy link

I reviewed and discussed in Slack with Patrick the following success metrics:

  1. Shared Language/Understanding (Say/Think) Impressions: Viewing a card on either their home or next try screen  (1x/week)
  2. Shared Strategy Intentions: % of Strategies marked "next try"/# of resources played (for now, even if they don't mark a try as "I've got this"
  3. Process Progress: Logging tries/Marking a Next Try
  4. Advocacy: Sharing a resource OR QOTD

Patrick suggested: Weekly Active User KPI seems like the north star ... users that have logged in at least once a week.

Only concern was about strategy management to be able to have the journey video persist rather than be scheduled by date as the audio and conversation starters are. I'm working with Content to determine that this is a requirement. Patrick said the safest path forward is keep the old and add the new: "Today | Today (new) | Next Try | Library" so that we can see them all together then pick what works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment