System Requirements Document for glacial-whatsapp

1. Introduction

glacial-whatsapp is a WhatsApp status saver app. The user asked, in plain terms, for an app that lets someone keep the WhatsApp statuses they see on their own phone: "WhatsApp status saver app banao," followed by "Ok aap bana do app" — an unqualified instruction to build it. That instruction is the current commitment this document specifies.

The product intent is small, warm, and personal. A person opens WhatsApp, watches a status from someone they know, and wants to keep it or pass it on instead of losing it after 24 hours. glacial-whatsapp is the tool that makes that easy: it shows the statuses that are already on the device, lets the user look at one properly, save a copy of it onto their phone, and hand it straight to any other app or contact through the phone's own share sheet.

The audience is a general phone user — not a technical one. They are comfortable with WhatsApp, comfortable with their photo gallery, and not interested in file paths, settings screens, or accounts.

Delivery scope is deliberately narrow. The app views, saves/downloads, previews, and shares statuses. It is not a WhatsApp client, it does not publish statuses, it does not manage contacts, and it is not a WhatsApp account tool.

2. System Overview

glacial-whatsapp is a small, device-local companion app with no first-party account system and no first-party server. It reads the WhatsApp status media that already sits on the user's phone, presents it as a browsable set, lets the user preview one status at a time, and lets them save a copy down onto the device or hand it to the phone's share sheet for direct sharing onward.

Actors

• Status Saver User (active human persona, closed catalog of one): browses the statuses available on the phone, previews them, saves the ones they want, and shares them onward.
• Device media storage (non-persona): the phone's local storage where the WhatsApp status files live and where saved copies are written.
• Device share sheet and the apps or contacts behind it (external destination, non-persona): receives the handed-off status. The app does not know or manage who or what sits at the other end of that handoff.

Current accepted behavior

• View the WhatsApp statuses available on the device.
• Preview a selected status in a focused view.
• Save/download a status to the device.
• Share a status directly through the device share sheet.

Ownership and access

• All three information surfaces — Landing, Statuses, Status Details — are first-party custom pages of the app, owned by the application, and reachable without any account. There is no sign-up, no sign-in, no profile, and no differentiated permission model anywhere in the accepted scope.
• The device share sheet is provider-owned and the destination behind it is external and outside the app's control. The app's responsibility ends at handing the status off correctly.

Exclusions

• No WhatsApp account integration, no login with a WhatsApp number, no QR pairing.
• No publishing, uploading, editing, cropping, captioning, or altering of status media.
• No contact management, chat reading, message recovery, or profile viewing.
• No in-app media library, album manager, or cloud backup of saved statuses.
• No social features: no likes, comments, following, feeds, or recommendations.

2a. Product Interpretation and Delivery Boundary

glacial-whatsapp is delivered as an on-device app. It has no sign-up wall, because there is nothing in the accepted behavior that a private, resumable, per-person account would protect: the media it works with already belongs to the person holding the phone, and the saved copies land in that same person's own device storage. Every page is openly reachable from the moment the app opens.

The app's working material comes from outside itself: WhatsApp's status media must already be present on the device for glacial-whatsapp to read and display anything, and the device must grant storage access before a status can be written back to the phone. When either prerequisite is missing, the app says so plainly and offers the one action that fixes it, rather than failing silently.

Saving and sharing are completed in different places, and the app is honest about that. Saving finishes inside glacial-whatsapp: the app writes a copy into the device's own storage and confirms it. Sharing finishes outside glacial-whatsapp: the app hands the status to the phone's share sheet, and the user chooses the destination from whatever apps and contacts that sheet offers. Once the handoff happens, the outcome belongs to that other app.

Nothing beyond viewing, saving/downloading, previewing, and sharing is in current scope. No future-phase behavior has been accepted, so no future surfaces are reserved, promised, or partially built.

2c. Page Content and Component Coverage

Landing

• Purpose and access. The anonymous first impression of glacial-whatsapp. Reachable with no account and no prior state; it is what a person sees on first open. It is pure orientation — it explains the app and sends the user to their statuses.
• Information and state. What the app does (view the WhatsApp statuses on your phone, preview them, save them to your device, share them onward); who it is for (anyone who watches WhatsApp statuses and wants to keep the good ones); the honest prerequisite that the statuses have to be present on the phone for the app to show them. No personal or user-specific data is rendered.
• Primary action. A single oversized pill button that takes the user to Statuses.
• Supporting actions and content. A short three-step "how it works" strip — statuses are on your phone → open the app and pick one → save it or share it. A secondary text link that scrolls to a brief "what this app does and doesn't do" note restating the narrow scope. No account prompts, no newsletter, no permission request.
• Domain entities. None. The Landing page reads no status files and holds no status state.
• Component responsibilities. HeroIllustration (oversized waving vector character, cream backdrop, orange accent, hand-drawn flourishes); HeroHeadline and HeroSubline; PrimaryPillCta (navigates