Interactive wireframe

Same Feeds base app, with the Drop-In layer added on top. Anything Drop-In adds to the Feeds surface is marked Drop-In. Walk the ask and answer flows, swipe the in-feed card, and open the hub and archive.

Overview

Context & Motivation

Drop-In is a community question-and-answer feature for DROPS. Users ask short, condition-tagged questions as video, photo, or text-card posts; other users answer with their own short video or photo responses; and the strongest threads can surface as a swipeable Q&A card directly in the My Journey feed.

It gives people a way to get real, lived-experience answers from others further along in a similar journey — without leaving the feed, and without needing an existing following relationship with the person who answers.

What It Is

• A dedicated hub, reached from the feed switcher, for asking and answering short-form video/photo/text Q&A
• A personal archive of every thread a user has started or answered, filterable by condition
• A new card type in the My Journey feed — badged "Drop-In" — that surfaces a featured thread as a swipeable stack of question + answers

Drop-In Hub

Purpose

The hub is a separate area from the video feeds, dedicated entirely to community Q&A. It has three jobs: let someone ask a question, let someone answer an open question, and give each person an archive of their own question-and-answer history.

Entry Points

• Feed switcher — "Drop-In" appears as an option in the same dropdown menu used to switch between My Journey, Following, and HCPs, marked with a question-mark icon in the app's mint accent color
• Persistent shortcut — a "Drop-In" pill is shown in the My Journey header at all times, giving a one-tap way back into the hub without opening the feed switcher

Hub Layout

• Hero card — "Looking for answers from others?" with a primary "Drop a question" CTA
• Open Questions — a list of threads with no answers yet, with a count of how many are waiting
• Drop Archive — every thread the person has started or answered, with a total thread count

Ask a Question Screen

Trigger

Tapping "Drop a question" from the hub hero card, or the same entry point surfaced elsewhere in the app (e.g., empty states).

Flow

• Tag a topic — select the condition or topic the question is about. Options include the user's own conditions (e.g., Migraine, Crohn's) as well as broader cross-cutting topics (e.g., Anxiety, Menopause, Caregiving, Burnout, Recovery, Sobriety)
• Ask anonymously — optional toggle; when enabled, the question is posted without the user's handle visible to other users
• Choose a format:
  • Record a video — use the camera to record a short clip
  • Write it out on a card — text over a styled background
  • Take a photo — a single still frame
• Add an optional caption or question text
• Submit via "Send your question" — the button is disabled until a topic tag and a question format have been provided

After Posting

The question appears in the Open Questions list in the hub immediately. If it meets feed eligibility rules, it can additionally surface as a Drop-In card in the My Journey feed (see Feed Surfacing & Ranking, below).

Answer a Question Screen

Open Questions List

The hub surfaces every open (unanswered) question as a card showing:

• Topic/condition tag
• Who asked it (or an anonymous indicator)
• How long ago it was posted
• The question media (video thumbnail with play control, photo, or text card)
• Current answer count
• A "Drop an answer" call to action

Answer Composer

Tapping "Drop an answer" opens the answer composer, where the person records or uploads their own short video or photo response, adds an optional caption, and submits.

After Answering

The answer attaches to that question's thread. A thread with at least one answer is considered answered/complete for the purposes of the Open Questions list (it no longer appears there), but the thread remains open to receive additional answers from other users afterward.

Archive Screen

Purpose

The Drop Archive collects every thread the person has started or answered, so they can find their own questions and answers again later.

Behavior

• Threads are grouped/filterable by condition, so a user can view just their Crohn's threads, their migraine answers, or everything across conditions
• Each entry previews the original question alongside its answers, shown as indented, reply-style rows crediting each answerer ("@you" for the viewer's own posts)
• Tapping into a thread shows the full question, an answer count, and every answer in order with author handle, time posted, and media
• "Drop an answer" remains available from the full thread view — archived threads can still receive new answers
• Unanswered questions remain in the Open Questions list (not the archive) until someone responds

Drop-In Card in My Journey Feed

Purpose

A featured Drop-In thread can appear as a card in the My Journey feed, letting someone drop into an ongoing conversation and quickly browse multiple perspectives on the same question without leaving the feed.

Placement

The Drop-In card appears as the first item in the My Journey feed, mixed in above the normal video posts. It inherits the same feed chrome (condition chips, feed switcher) as any other My Journey content.

Anatomy

• A small "Drop-In" badge marks the card as community Q&A rather than a regular video post
• The first slide shows the question and an initial answer
• Swiping right reveals additional answers, one at a time, like turning cards in a deck
• A row of dots indicates which answer is currently showing
• A "Swipe →" affordance is shown to prompt the interaction

Feed Surfacing & Ranking TBD

Which thread gets featured as the My Journey Drop-In card, and how often a new one is surfaced, is not yet defined. Candidate signals to evaluate:

• Condition match to the viewer's selected condition(s)
• Minimum answer count threshold before a thread is eligible to feature
• Recency of the question and/or its most recent answer
• Engagement on existing answers (views, reactions)
• Cadence — how often a Drop-In card appears per session, and whether it's the same thread for every viewer or personalized per user

Moderation & Safety

Drop-In involves open community contributions and anonymous posting, so it needs its own moderation controls:

• Users can flag a question or an answer for review
• Anonymous posting hides the asker's handle from other users but is retained internally for moderation and accountability
• HC moderators can remove a question or an individual answer that violates community guidelines

Edge Cases

Success Metrics

Interactive wireframe

Same Feeds base app, with the Same layer on top. What Same adds is marked Same. Tap the Same button on the rail to see the active state, count, and toast, then follow it into the chat, the people list, and the activity surface. Tap it again to undo.

1. Feature Summary

Same is a feed-level social action that allows a user to say:

"This exact experience happened to me too."

In the prototype, Same appears directly in the vertical video feed as a right-side action button, alongside other familiar engagement actions:

• Creator profile / follow
• Like
• Same
• Comment
• Save
• Share

The Same icon is visually represented as three overlapping circles, with a numeric count below it showing how many users have marked that video as Same.

When a user taps Same, the app should capture a high-intent lived-experience signal, associate the user with that video, and connect them to a chat/community of other users who marked Same on the same video.

2. Product Goal

The goal of Same is to convert emotional recognition in the feed into meaningful community connection.

Same should help users move from passive resonance:

"I relate to this."

to active connection:

"Other people have been through this exact thing too, and I can talk to them."

3. Primary User Problem

Users watching condition-related videos often see content that closely mirrors their own lived experience. Existing actions like Like, Save, Comment, or Share do not clearly communicate:

• "This happened to me too."
• "I want to see who else experienced this."
• "I want to join a conversation around this specific shared moment."

Same fills that gap.

4. Prototype-Based UX Context

The prototype shows Same living inside the main vertical video experience.

Feed layout observed

The video feed includes:

• Full-screen vertical video
• Feed selector at the top, such as Following, My Journey, or HCPs
• Right-side engagement rail
• Bottom navigation with Home, Discover, central create button, Activity, and Profile

Same placement

Same appears on the right-side action rail:

• Profile / follow control
• Like button
• Same button
• Comment button
• Save button
• Share button

This means Same should be treated as a first-class engagement action, equivalent in importance to Like or Comment.

5. Core User Story

As a user watching a video, I want to tap Same when the video describes something that happened to me too, so that I can save that shared experience, see that others felt the same, and join a conversation with people who understand it.

6. Example Scenario

A user is scrolling the feed and sees a video from a creator describing:

"MS at 28. Crying in my car, then back to the meeting."

The user had that same experience recently.

The user taps the Same icon.

After tapping Same:

• The Same icon changes to an active state.
• The Same count increments.
• The video is added to the user's Same activity.
• The user is invited into, or given access to, a chat connected to that video.
• The user can see other people who also tapped Same.
• The user may follow those people or participate in the shared conversation.

7. Functional Requirements

8. MVP Scope

The MVP should include:

• Same icon in the right-side video action rail.
• Same count beneath the icon.
• Active/inactive Same state.
• Ability to tap and untap Same.
• Same event capture.
• Same activity surface.
• Same chat association.
• Same chat invitation or entry point.
• Basic Same notifications.
• Basic analytics.
• Basic privacy and moderation handling.

9. Out of Scope for MVP

The following should be considered post-MVP unless specifically prioritized:

• Same-based feed ranking.
• Same-based recommendation model.
• Public Same user lists without privacy controls.
• Creator analytics dashboard for Same.
• Braze lifecycle campaigns.
• Advanced Same clustering across multiple videos.
• Same communities that exist independently of a video.
• A/B testing multiple Same labels.
• Anonymous Same mode.

10. UX Requirements

Same Button

The Same icon should remain visually consistent with the prototype:

• White icon on video
• Numeric count underneath
• Positioned between Like and Comment
• Uses the three-overlapping-circles visual language

Tap Feedback

When a user taps Same, the UI should provide immediate confirmation.

Potential feedback:

• Icon animates or fills
• Count increments
• Small toast appears
• Optional bottom sheet appears with chat invitation

Recommended toast:

Same Chat Entry

The user should not be forcibly removed from the feed after tapping Same.

Recommended behavior:

• User taps Same.
• Confirmation appears.
• User can keep scrolling.
• User can optionally open the Same chat immediately.
• User can find the Same chat later in Activity/Same.

Same Activity Empty State

If a user has not tapped Same yet:

11. Privacy Requirements

Same is sensitive because it may imply a user has experienced a health-related or personal situation.

Requirements

• Do not expose a user as having tapped Same unless visibility rules allow it.
• Do not show Same participation to blocked users.
• Respect private profiles.
• Allow users to leave Same chats.
• Consider whether Same should default to private participation until the user posts in chat.
• Make it clear if joining a Same chat makes the user visible to others.

12. Moderation Requirements

Same chats should inherit existing chat/community moderation tools.

Requirements

Users should be able to:

• Report a message.
• Report a user.
• Block a user.
• Leave a chat.
• Mute notifications.
• Hide or remove themselves from a Same community.

Admins/community managers should be able to:

• Review reported Same chats.
• Remove unsafe messages.
• Disable a Same chat if needed.
• Handle deleted or moderated source videos.

13. Analytics Requirements

Track the following events:

• same_icon_viewed
• same_tapped
• same_removed
• same_count_incremented
• same_chat_prompt_viewed
• same_chat_joined
• same_chat_opened
• same_chat_message_sent
• same_activity_opened
• same_user_followed
• same_notification_sent
• same_notification_opened

14. Success Metrics

Primary metrics:

• Same taps per video view
• Same tap rate by feed type
• Same chat join rate
• Same chat participation rate
• Return rate after tapping Same
• Follow rate from Same-related discovery
• Retention lift among users who tap Same versus users who only like/save/comment

Secondary metrics:

• Average Same count per video
• Percentage of videos with at least one Same
• Same notifications opened
• Same chats with at least one message
• Same chats with repeat engagement
• Videos with high Same-to-like ratio

15. Open Questions

• Does tapping Same automatically add the user to the chat, or does it only invite them?
• Is Same participation visible to other users by default?
• Should users be able to tap Same privately?
• Should the Same count be public on all videos?
• What happens if a user removes Same after joining the chat?
• Should Same chats be created after the first Same tap or after a minimum threshold?
• Should creators be notified when users tap Same?
• Should Same influence feed personalization in MVP?
• Should Same be available on HCP content, patient content, Drop-In content, or all content?
• What should the active Same icon look like?
• Should the label "Same" appear anywhere in the UI, or is the icon-only treatment enough?
• Should Same activity live inside Activity, or should there be a dedicated Same tab?

16. Recommendation

Treat Same as a feed-native engagement action first and a community activation feature second.

The prototype makes Same feel like a core social behavior, not a separate feature buried elsewhere. The MVP should preserve that simplicity:

User sees video → taps Same → count updates → video is saved to Same → user can join a conversation with others who experienced it too.

That is the cleanest product spine for the feature.