social-media-facebook

byHussain Bekhushi

Create a social media application like facebook, instagram, ticktook etc but add some new feature that there have not yet

LandingCreate PostFeedPost DetailsSign UpDiscoverMessages
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Social Media Application

1. Introduction

This System Requirements Document specifies a social media application in the tradition of Facebook, Instagram, and TikTok, with one defining ambition: it must add new features that other social media applications do not yet have. The product lets people create an account and a profile, publish posts with photos and short videos, follow other people, read a feed of their posts, react to and comment on posts, and send direct messages.

The audience is two overlapping groups of people: Members, who join to connect, share, and converse, and Content creators, who publish short videos and photos to build an audience and who read the reactions and comments their posts receive. The product is friendly, quick, and human in tone — not corporate — and its interface follows a warm, pixel-crafted visual language described in Sections 6 through 8.

The product is delivered as a first-party web application with application-owned identity: a public Landing page, a Sign Up page where a new person makes an account and a profile, and five protected destinations (Feed, Discover, Create Post, Post Details, Messages) available only after identity is established.

Page 1 of 26

Success Criteria

  • A new person can move from the Landing page through Sign Up to a completed profile and reach the Feed without assistance.
  • A Member can publish a post containing a photo or a short video and see it appear in the feed of people who follow them.
  • A Member can find another person in Discover, follow them, and subsequently see that person's posts in the Feed.
  • A Member can react to and comment on a post, and the post's author can observe the reaction and comment on Post Details.
  • A Member can send a direct message to another user and observe the delivered conversation.
  • The product visibly presents new social features that other social media applications do not have, on the Landing page and within the member experience.
Page 2 of 26

2. System Overview

The Social Media Application is a first-party web product composed of a React frontend, a shared FastAPI backend, and a MariaDB database. The frontend presents seven destinations: a public Landing page, a public Sign Up page, and five login-protected pages — Feed, Discover, Create Post, Post Details, and Messages. The backend owns accounts, profiles, posts and their media references, follow relationships, reactions, comments, and direct-message conversations. The database persists all of this application-owned state.

Two active human personas use the product: Member and Content creator. Both establish an account and profile through Sign Up, and both use the protected pages according to their goals. The Member's center of gravity is the Feed, Discover, and Messages; the Content creator's center of gravity is Create Post and Post Details, where published work and its reactions and comments are observed.

The product's distinguishing commitment is that it adds new features that other social media applications do not have yet. These new features are presented on the Landing page as a hard-bordered row of four square icon tiles and are available within the member experience.

Removed from scope

  • None. No concept was explicitly removed by the user.
Page 3 of 26

2a. Product Interpretation and Delivery Boundary

The product is a first-party, application-owned web application. Identity is application-owned: a person creates an account and a profile on the Sign Up page, and returning users verify that account before reaching protected work. The Landing and Sign Up pages are anonymously reachable; Feed, Discover, Create Post, Post Details, and Messages require login. A protected destination does not establish access to itself — the anonymous entry interaction lives on Landing and Sign Up.

All accepted behavior is current. No future-horizon capabilities are specified. The product does not include provider-owned surfaces, external destinations, or headless delivery; every accepted human-facing capability is owned by one of the seven first-party pages, supported by the shared backend and database.

The new features that distinguish this product from existing social media applications are delivered as part of the current member experience and are surfaced on the Landing page. They are not a separate module or a future idea.

2c. Page Content and Component Coverage

Page 4 of 26

Landing

  • Information and state: Anonymous public entry. Presents the product's purpose and its new social features. No account state is required to view.
  • Primary action: "Join now" call to action leading to Sign Up.
  • Supporting actions: Navigate to Sign Up from the hero; read the four new-feature tiles.
  • Domain entities: None persisted; presents product identity and feature descriptions.
  • Component responsibilities:
    • Oversized pixel wordmark in tomato red spanning the viewport width, set in Silkscreen at clamp(40px, 9vw, 96px).
    • Hero headline "A social feed with new moves" and subline "Post photos and short videos, follow people, comment and send messages. Try the features other apps do not have."
    • "Join now" button in a red square block at the left edge, not centered.
    • A hard-bordered row of four square icon tiles showing the new features, each drawn on a 16px pixel grid.
    • Fixed left rail of square icon buttons with ink borders at 1280px; bottom bar at 375px.
  • States: Loading (static content, no data fetch required); empty (not applicable); success (page renders fully); error (not applicable for static content); recovery (all controls remain reachable at 375px, 768px, and 1280px).
Page 5 of 26

Sign Up

  • Information and state: Anonymous identity-access surface. Collects the information needed to make an account and a profile. No protected state is available until identity is established.
  • Primary action: Create the account and profile, then proceed to the Feed.
  • Supporting actions: Return to Landing; correct invalid input.
  • Domain entities: Account (identity credential), Profile (display identity).
  • Component responsibilities:
    • Account credential fields and profile fields, labeled in small caps above values.
    • Submit control styled as a red square block.
    • Inline validation messaging for missing or invalid input.
  • States: Loading (submission in progress); empty (blank form on first arrival); success (account and profile created, redirected to Feed); error (validation failure or submission failure with a clear message and preserved input); recovery (user corrects input and resubmits without losing entered data).
Page 6 of 26

Feed

  • Information and state: Login-protected. Shows posts from people the Member follows, in one feed. Counts of reactions and comments are displayed in Silkscreen pixel digits.
  • Primary action: Read posts and open a post's details.
  • Supporting actions: Navigate to Discover, Create Post, Messages, and Post Details; react to a post inline.
  • Domain entities: Post (photo or short video), Profile (author), Reaction, Comment (count).
  • Component responsibilities:
    • Feed cards stacked in one column at 375px and split into a 7/5 pair at 1280px, each with a 2px ink border, 0px corners, and a small pixel square bullet.
    • Author identity and post media inside square ink frames.
    • Reaction and comment counts in Silkscreen.
    • Fixed left rail of square icon buttons at 1280px; bottom bar at 375px.
  • States: Loading (feed fetching); empty (no posts from followed people, with a prompt to visit Discover); success (posts rendered); error (fetch failure with retry); recovery (retry restores the feed).
Page 7 of 26

Discover

  • Information and state: Login-protected. Presents other users to find and follow.
  • Primary action: Follow another user.
  • Supporting actions: Open a user's posts; unfollow; navigate to Feed, Create Post, Messages.
  • Domain entities: Profile, Follow relationship.
  • Component responsibilities:
    • User tiles with 2px ink borders and 0px corners.
    • Follow control styled as a red square block.
    • Pixel square bullets and small-caps labels.
  • States: Loading (user list fetching); empty (no suggestions available, with a clear message); success (users listed with follow state); error (fetch or follow failure with retry); recovery (retry or re-attempt follow).
Page 8 of 26

Create Post

  • Information and state: Login-protected. Composes a post with a photo or a short video.
  • Primary action: Publish the post.
  • Supporting actions: Attach a photo or short video; add caption text; discard the draft.
  • Domain entities: Post (media type: photo or short video; caption; author).
  • Component responsibilities:
    • Media attachment control for photo or short video.
    • Caption input.
    • Publish control styled as a red square block.
    • Preview of the attached media inside a square ink frame.
  • States: Loading (upload/publish in progress); empty (no media attached yet); success (post published and visible to followers); error (unsupported media, upload failure, or publish failure with a clear message); recovery (re-attach media or retry publish without losing the caption).
Page 9 of 26

Post Details

  • Information and state: Login-protected. Shows a single post with its reactions and comments.
  • Primary action: Add a reaction or a comment.
  • Supporting actions: Read existing reactions and comments; return to Feed.
  • Domain entities: Post, Reaction, Comment, Profile.
  • Component responsibilities:
    • Post media inside a square ink frame with 2px ink border.
    • Reaction control and comment input.
    • Reaction and comment counts in Silkscreen.
    • Comment list with small-caps author labels.
  • States: Loading (post fetching); empty (no comments yet, with an invitation to comment); success (post, reactions, and comments rendered); error (fetch or submission failure with retry); recovery (retry restores content; failed comment preserves typed text).
Page 10 of 26

Messages

  • Information and state: Login-protected. Shows direct-message conversations with other users.
  • Primary action: Send a direct message to another user.
  • Supporting actions: Select a conversation; read received messages.
  • Domain entities: Conversation, Message, Profile (participants).
  • Component responsibilities:
    • Conversation list with 2px ink borders.
    • Message thread view.
    • Message composer with send control styled as a red square block.
  • States: Loading (conversations fetching); empty (no conversations yet, with a prompt to start one); success (thread rendered and messages delivered); error (send or fetch failure with retry); recovery (retry send without losing the composed message).
Page 11 of 26

3. Functional Requirements

FR-1 — Account and profile creation (explicit) As a new person, I should create an account and a profile so that I can participate in the social product.

  • Trigger/input: The person arrives at Sign Up from the Landing page and supplies account and profile information.
  • Observable result: An account and profile exist, and the person reaches the Feed as an authenticated Member or Content creator.
  • Access state: Anonymous on Landing and Sign Up; protected state becomes available only after identity is established.
  • Failure/recovery: Invalid or missing input is reported inline with entered data preserved; the person corrects and resubmits.
  • Continuation: The person proceeds to the Feed.

FR-2 — Returning verification (required_inference) As a returning user, I should verify my account before protected work so that my posts, follows, reactions, comments, and messages remain bound to me.

  • Trigger/input: A returning person supplies their account credentials.
  • Observable result: The person reaches protected pages with their own state restored.
  • Access state: Anonymous entry; protected pages unavailable until verification succeeds.
  • Failure/recovery: Failed verification reports a clear message and allows retry.
  • Continuation: The person continues to Feed, Discover, Create Post, Post Details, or Messages.
Page 12 of 26

FR-3 — Publish posts with photos and short videos (explicit) As a Member or Content creator, I should publish posts with photos and short videos so that others can see my content.

  • Trigger/input: The person attaches a photo or a short video on Create Post and publishes.
  • Observable result: The post exists with its media and author, and appears in the feed of people who follow the author.
  • Access state: Login required.
  • Failure/recovery: Unsupported media or upload failure is reported; the caption is preserved and the person can re-attach or retry.
  • Continuation: The person can view the post on Post Details.

FR-4 — Follow other users and read a feed (explicit) As a Member, I should follow other users and read a feed of their posts so that I stay current with people I care about.

  • Trigger/input: The person follows another user on Discover; the Feed then aggregates posts from followed users.
  • Observable result: The followed relationship exists, and the followed user's posts appear in the Feed.
  • Access state: Login required.
  • Failure/recovery: Follow or feed fetch failure is reported with retry; the follow state remains consistent.
  • Continuation: The person reads posts and opens Post Details.
Page 13 of 26

FR-5 — React to and comment on posts (explicit) As a Member or Content creator, I should react to and comment on posts so that I can respond to content.

  • Trigger/input: The person selects a reaction or submits a comment on Post Details.
  • Observable result: The reaction or comment is recorded and its count updates in Silkscreen digits.
  • Access state: Login required.
  • Failure/recovery: Submission failure is reported; typed comment text is preserved for retry.
  • Continuation: The person reads the updated thread.

FR-6 — Send direct messages (explicit) As a Member or Content creator, I should send direct messages to other users so that I can converse privately.

  • Trigger/input: The person selects a conversation or starts one and sends a message on Messages.
  • Observable result: The message is delivered to the conversation and visible to both participants.
  • Access state: Login required.
  • Failure/recovery: Send failure is reported; the composed message is preserved for retry.
  • Continuation: The person continues the conversation.
Page 14 of 26

FR-7 — New features not present in other social media applications (explicit) As a Member or Content creator, I should encounter new features that other social media applications do not have yet so that this product offers something genuinely different.

  • Trigger/input: The person views the Landing page's four new-feature tiles and uses the corresponding features within the member experience.
  • Observable result: The new features are visible and usable, and their effects are observable in the member experience.
  • Access state: Landing tiles are anonymous; in-product use requires login.
  • Failure/recovery: Feature failure is reported with retry consistent with the page's states.
  • Continuation: The person continues their social activity.

FR-8 — Observe reactions and comments on own posts (required_inference) As a Content creator, I should observe the reactions and comments my posts receive so that I know how my audience responds.

  • Trigger/input: The creator opens Post Details for a published post.
  • Observable result: The post's reactions and comments, with counts in Silkscreen digits, are visible to the author.
  • Access state: Login required.
  • Failure/recovery: Fetch failure is reported with retry.
  • Continuation: The creator returns to Create Post or the Feed.

4. User Personas

Page 15 of 26

Member

  • Product context: A person who joins the Social Media Application to connect with others, share everyday photos and short videos, and converse. The Member moves fluidly between reading the Feed, finding people in Discover, publishing on Create Post, responding on Post Details, and talking in Messages.
  • Primary goal: Stay current with people they follow and participate in the social conversation.
  • Distinct accepted responsibilities: Creates an account and profile (FR-1); verifies on return (FR-2); follows other users and reads the Feed (FR-4); reacts to and comments on posts (FR-5); sends direct messages (FR-6); publishes posts with photos and short videos (FR-3); encounters the product's new features (FR-7).
  • Relevant inputs or decisions: Whom to follow, which posts to react to or comment on, what to say in a message, what media to publish.
  • Interactions with other accepted participants: Follows Content creators and other Members; reacts to and comments on their posts; sends them direct messages; sees their posts in the Feed.
  • Observable success: The Feed shows posts from followed people; reactions and comments appear with updated counts; messages are delivered; published posts reach followers.
Page 16 of 26

Content creator

  • Product context: A person who publishes short videos and photos to build an audience and who watches how that audience responds. The creator's center of gravity is Create Post and Post Details, where published work and its reception are observed.
  • Primary goal: Publish short videos and photos and understand the audience's reactions and comments.
  • Distinct accepted responsibilities: Creates an account and profile (FR-1); verifies on return (FR-2); publishes posts with photos and short videos (FR-3); observes reactions and comments on own posts (FR-8); also reacts to and comments on posts (FR-5), sends direct messages (FR-6), follows users and reads the Feed (FR-4), and encounters the product's new features (FR-7).
  • Relevant inputs or decisions: Which media to publish, what caption to write, how to respond to audience reactions and comments.
  • Interactions with other accepted participants: Publishes to followers (Members and other creators); reads their reactions and comments; exchanges direct messages.
  • Observable success: Published posts appear to followers; reactions and comments accumulate and are visible on Post Details with Silkscreen counts.

5. Core User Flows

Page 17 of 26

Flow A — A new person joins and reaches the Feed (Member and Content creator)

  1. The person arrives anonymously at Landing and reads the headline "A social feed with new moves", the subline, and the four new-feature tiles.
  2. The person selects the "Join now" red square block at the left edge.
  3. On Sign Up, the person supplies account and profile information.
  4. The person submits. On validation failure, inline messages appear and entered data is preserved; the person corrects and resubmits.
  5. On success, the account and profile exist and the person arrives at Feed as an authenticated Member or Content creator.
  6. Next step: the person explores Discover or Create Post.

Flow B — A returning user verifies and resumes (Member and Content creator)

  1. The returning person supplies account credentials at the anonymous entry.
  2. On failed verification, a clear message appears and the person retries.
  3. On success, the person reaches Feed with their own state restored.
  4. Next step: the person continues to any protected page.

Flow C — A Member finds and follows people (Member)

  1. From Feed, the Member navigates to Discover.
  2. The Member reviews user tiles and selects Follow on a person.
  3. On follow failure, an error is reported and the Member retries; the follow state remains consistent.
  4. On success, the follow relationship exists.
  5. Next step: the Member returns to Feed, where the followed person's posts now appear.
Page 18 of 26

Flow D — A Content creator publishes a post (Content creator)

  1. The creator opens Create Post.
  2. The creator attaches a photo or a short video and writes a caption.
  3. On unsupported media or upload failure, a clear message appears; the caption is preserved and the creator re-attaches or retries.
  4. The creator selects Publish.
  5. On success, the post exists with its media and author and appears in the feed of people who follow the creator.
  6. Next step: the creator opens Post Details to observe the post.

Flow E — A Member reacts to and comments on a post (Member)

  1. From Feed, the Member opens a post on Post Details.
  2. The Member selects a reaction; the reaction is recorded and its count updates in Silkscreen digits.
  3. The Member writes and submits a comment.
  4. On submission failure, a clear message appears and the typed comment is preserved for retry.
  5. On success, the comment appears in the thread with the author's small-caps label.
  6. Next step: the Member returns to Feed or continues reading.

Flow F — A Content creator observes audience response (Content creator)

  1. The creator opens Post Details for a published post.
  2. The creator reads the reactions and comments and their Silkscreen counts.
  3. On fetch failure, a clear message appears and the creator retries.
  4. Next step: the creator returns to Create Post or the Feed.
Page 19 of 26

Flow G — A Member sends a direct message (Member)

  1. The Member opens Messages.
  2. The Member selects an existing conversation or starts one with another user.
  3. The Member composes and sends a message.
  4. On send failure, a clear message appears and the composed message is preserved for retry.
  5. On success, the message is delivered and visible to both participants.
  6. Next step: the Member continues the conversation.

Flow H — A person encounters the new features (Member and Content creator)

  1. On Landing, the person reads the four hard-bordered new-feature tiles.
  2. After joining or verifying, the person uses the corresponding new features within the member experience.
  3. On feature failure, a clear message appears with retry consistent with the page's states.
  4. Next step: the person continues their social activity.
Page 20 of 26

6. Visuals Colors and Theme

Muse and headline: Susan Kare — "Charming clarity after Susan Kare." The mood is friendly, quick, and human, not corporate.

Mode: Light mode.

Color tokens (exact hex by role):

  • Background (warm paper ground): #F3EFE4
  • Surface (cards): #FFFDF7
  • Text (ink): #1B1B1B
  • Primary (tomato red, the only hot accent, marks actions): #E2452F
  • Accent (green, marks live or new states): #2F6F5E
  • Muted (small labels only): #8A8578

Typography:

  • Headings: Silkscreen, bold weight, tight case, used for short labels and numerals.
  • Body: Work Sans at 400 and 600 for all reading text.
  • Scale: 1.333 modular — 96 / 64 / 40 / 28 / 20 / 16. Display sizes use clamp(40px, 9vw, 96px) on mobile to desktop.

Shape language: Hard 2px ink borders, square tiles, 0px corners. Filled pixel squares act as bullets and dividers.

Layout: A 12-column grid with a wide left margin. Feed cards stack in one column at 375px and split into a 7/5 pair at 1280px. Labels sit above values in small caps.

Imagery: Pixel icons and simple pictograms drawn on a 16px grid. Photos appear inside square ink frames with no soft shadows.

Page 21 of 26

Avoid: No soft drop shadows or rounded 16px cards; no blue or indigo accent on a white ground; no gradient blobs or glass panels; no Inter, Roboto, or system-ui fonts; no bouncy spring easing; no stock people photos in the hero.

7. Signature Design Concept

The public entry is a full-width warm paper ground (#F3EFE4) holding one oversized pixel wordmark in tomato red (#E2452F) set in Silkscreen and spanning the viewport width at clamp(40px, 9vw, 96px). Below it, the hero headline "A social feed with new moves" and subline sit in ink (#1B1B1B) on the paper ground. A hard-bordered row of four square icon tiles — each drawn on a 16px pixel grid, each with a 2px ink border and 0px corners — shows the new features. The "Join now" call to action sits in a red square block at the left edge, not centered, so the eye lands on the wordmark first and the action second. Every card on the page carries a 2px ink border, 0px corners, and a small pixel square as its bullet. Navigation is a fixed left rail of square icon buttons with ink borders at 1280px and a bottom bar at 375px. All readable text and controls stay whole inside the viewport and their containers at 375px, 768px, and 1280px.

Page 22 of 26

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat

Landing Hero Motion Brief

  • Focal subject: The oversized Silkscreen pixel wordmark in tomato red, with the four hard-bordered new-feature icon tiles beneath it.
  • Input → transformation → outcome thesis: As the visitor hovers an icon tile, the pixel icon blinks and slides in discrete frame-by-frame micro steps, revealing the new feature's label; the wordmark and "Join now" block remain still. The outcome is a clear, friendly read of the product's new features without motion that distracts from the call to action.
  • Motion vocabulary: Frame-by-frame micro steps only; icons blink and slide on hover; no easing curves and no parallax.
  • Composed first frame: Warm paper ground, oversized tomato-red pixel wordmark spanning the viewport, headline and subline in ink, four square icon tiles in a hard-bordered row, and the red "Join now" square block at the left edge.
  • Reduced-motion state: With prefers-reduced-motion, the icon tiles present a static arrangement with labels visible and no blink or slide; all tiles and the "Join now" control remain fully readable and reachable.
Page 23 of 26

9. Non-Functional Requirements

  • NFR-1 — Application-owned identity and session continuity (required_inference): Accounts, profiles, follows, posts, reactions, comments, and messages must remain bound to the correct person across sessions. Rationale: accepted journeys create durable relationships, commitments, and value for other participants.
  • NFR-2 — Durable persistence (explicit via Planning Scope): All application-owned state (accounts, profiles, posts and media references, follows, reactions, comments, conversations, messages) persists in MariaDB.
  • NFR-3 — Media handling (explicit): Posts support photos and short videos; unsupported media is rejected with a clear message and preserved caption.
  • NFR-4 — Readable text and controls at every viewport (explicit via creative direction): Headlines, wordmarks, labels, numbers, card text, and controls stay entirely inside the viewport and their containers at 375px, 768px, and 1280px, wrapping or scaling to fit; no other element covers them.
  • NFR-5 — Reduced-motion usability (explicit via creative direction): With prefers-reduced-motion, a usable static arrangement is provided; every item can be brought fully into view.
  • NFR-6 — Distinctive new features (explicit): The product must add new features that other social media applications do not have yet; these are surfaced on Landing and available in the member experience.
Page 24 of 26

10. Tech Stack

  • Frontend: React application UI.
  • Backend: Shared FastAPI process for application APIs and domain modules (accounts, profiles, posts, follows, reactions, comments, messages, new features).
  • Database: MariaDB for application-owned persistent data.
  • Infrastructure: Docker/docker-compose with the provisioned services: backend (FastAPI), database (MariaDB), frontend (React). No additional services are required for the accepted workflows.

11. Assumptions and Constraints

  • A-1 (assumption): The product is a web application delivered through the provisioned React frontend, FastAPI backend, and MariaDB database.
  • A-2 (assumption): Identity is application-owned; Sign Up establishes the account and profile, and returning users verify before protected work.
  • A-3 (constraint, explicit): The product must add new features that other social media applications do not have yet.
  • A-4 (constraint, explicit): The visual language follows the Susan Kare creative direction — warm paper ground, tomato-red primary, Silkscreen headings, Work Sans body, 2px ink borders, 0px corners, pixel icons on a 16px grid, frame-by-frame micro motion, no parallax.
  • A-5 (constraint, explicit): The generic indigo/blue-on-white SaaS template is forbidden.
  • A-6 (assumption): No future-horizon capabilities are specified; all accepted behavior is current.
Page 25 of 26

12. Glossary

  • Member: An active human persona who joins, follows, reads the Feed, reacts, comments, publishes, and messages.
  • Content creator: An active human persona who publishes short videos and photos to build an audience and observes reactions and comments on their posts.
  • Feed: The login-protected page showing posts from people the Member follows.
  • Discover: The login-protected page for finding and following other users.
  • Create Post: The login-protected page for publishing a post with a photo or a short video.
  • Post Details: The login-protected page showing a single post with its reactions and comments.
  • Messages: The login-protected page for direct-message conversations.
  • Sign Up: The anonymous page where a new person makes an account and a profile.
  • Landing: The anonymous public entry page presenting the product and its new features.
  • New features: The product capabilities that other social media applications do not have yet, surfaced on Landing and available in the member experience.
  • Reaction: A recorded response to a post, counted in Silkscreen digits.
  • Follow: A relationship in which a Member subscribes to another user's posts, which then appear in the Feed.
Page 26 of 26
Live
Landing design preview
Landing: Read new-feature tiles
Sign Up: 1. Enter account and profile details
Sign Up: 2. Correct invalid input
Feed: 1. Read followed posts
Feed: 2. Retry failed feed fetch
Create Post: 3. Attach photo or video
Create Post: 4. Write caption and publish
Create Post: 5. Re-attach media and retry
Post Details: 6. Open published post
Post Details: 7. Read reactions and comments
Post Details: 8. Retry failed fetch
Post Details: 9. Select a reaction
Post Details: 10. Submit a comment
Post Details: 11. Retry preserved comment
Discover: 12. Follow another user
Discover: 13. Retry failed follow
Messages: 1. Send direct message
Messages: 2. Retry preserved message
Feed: Use new features
Live
Landing design preview
Landing: Read new-feature tiles
Sign Up: 1. Enter account and profile details
Sign Up: 2. Correct invalid input
Feed: 1. Read followed posts
Feed: 2. Retry failed feed fetch
Create Post: 3. Attach photo or video
Create Post: 4. Write caption and publish
Create Post: 5. Re-attach media and retry
Post Details: 6. Open published post
Post Details: 7. Read reactions and comments
Post Details: 8. Retry failed fetch
Post Details: 9. Select a reaction
Post Details: 10. Submit a comment
Post Details: 11. Retry preserved comment
Discover: 12. Follow another user
Discover: 13. Retry failed follow
Messages: 1. Send direct message
Messages: 2. Retry preserved message
Feed: Use new features