regal-hey is a self-owned video streaming website. The product intent is to give the owner's streaming service a premium, attractive public home page that presents video content to visitors and lets them choose something to watch. The site is not a third-party service or an aggregator — it is the user's own platform, and the home page is its first impression.
The audience is twofold:
The requested experience is explicitly visual and emotional: an attractive, good-looking home page for a video streaming site. The accepted creative direction frames this as a cinematic, motion-led, content-forward surface — a cinema lobby at night — rather than a generic application landing page.
regal-hey is delivered as a first-party web application with two current pages:
Both pages are anonymously reachable (access_requirement: none). No account, sign-in, or identity establishment is part of the current scope: the accepted behavior is browsing and watching, and no accepted journey requires durable per-person state, a commitment, an entitlement, or a value transfer bound to a specific participant. The Site Owner's responsibility in the current scope is the presentation of the catalogue on the home page itself, not a separate administration surface.
Current actors:
Narrow exclusions for the current scope: no user accounts or profiles, no subscription or payment flow, no upload or content-management surface, no social features, and no third-party streaming service integration. These are not prohibited product directions — they are simply not part of the accepted current requirements.
The authoritative requirement is a self-owned video streaming site with an attractive home page that presents video content. Everything in this document serves that boundary.
Delivery ownership. Both pages are first-party custom UI owned by the application. The home page is the anonymous public entry: a visitor arrives with no prior relationship to the site and immediately sees the catalogue. The Watch page is likewise anonymously reachable — a visitor who selects a title goes straight to watching it. Because no accepted journey requires the platform to remember a specific person, bind a decision to them, or hold private state for them, no identity establishment or verification step is introduced. This keeps the entry experience frictionless, which is what an attractive streaming home page demands.
Current vs. future. Current scope is the home page presentation and the viewing destination it leads to. Content management, accounts, monetization, and personalization are outside the current boundary and are recorded only as future considerations in Section 11 — they do not appear in current pages, requirements, or acceptance.
Language. The user's working language is Hindi (Hinglish), and the accepted hero headline is Hindi ("Har raat, ek nayi kahani"). Interface copy in the hero and section eyebrows follows that voice; metadata and technical labels remain in their conventional form.
Information and state presented
Primary actions
Supporting actions
Domain entities
Component responsibilities
States
Information and state presented
Primary actions
Supporting actions
Domain entities
Component responsibilities
States
Each requirement is a distinct story point with provenance, lifecycle facts, and observable acceptance.
FR-1 — Self-owned streaming platform As the Site Owner, I should have my own video streaming website (not a third-party service) so that my catalogue is presented on a platform I own.
FR-2 — Attractive home page As the Site Owner, I should have an attractive, good-looking home page for my video streaming site so that visitors get a premium first impression of my service.
FR-3 — Present video streaming content to visitors As a Viewer, I should see the streaming catalogue presented on the home page so that I can find something appealing to watch.
FR-4 — Select and play a title As a Viewer, I should select a title from the home page and be taken to watch it so that I can start watching immediately.
FR-5 — Explore curated collections As a Viewer, I should browse curated collections on the home page so that I can discover titles grouped by theme.
FR-6 — Watch a selected title As a Viewer, I should watch the selected title on the Watch page so that I can consume the content I chose.
FR-7 — Navigate between destinations As a Viewer, I should move between the home page and the Watch page so that I can browse and watch without losing my place.
FR-8 — Present the owner's catalogue attractively As the Site Owner, I should have my catalogue presented with cinematic, content-forward presentation so that my streaming service reads as premium.
Product context. The Viewer arrives at regal-hey with no prior relationship to the site and no account. They are in an entertainment mood — a night in, looking for something to watch — and they judge the platform in the first few seconds. The home page is the entire first impression.
Primary goal. Find something appealing to watch, quickly, and start watching it without friction.
Distinct accepted responsibilities.
Relevant inputs or decisions. Which title to watch; whether to explore a collection or go straight to the featured title; whether to keep watching or return to browse.
Interactions with other accepted participants. The Viewer is the audience for the Site Owner's catalogue presentation. The Viewer's selection is what makes the owner's presentation meaningful; the Viewer never interacts with the owner directly, only with the catalogue the owner has curated.
Observable success. The Viewer finds an appealing title and is watching it within moments of landing, with no sign-in or setup step in the way.
What makes this role different. The Viewer's work is selection under low patience — the value of the home page is measured in how fast and how pleasurably a choice is made. This is a browsing-and-choosing role, not a managing or configuring one.
Product context. The Site Owner is the user who is building this streaming site themselves ("khud ka"). They own the platform and its content. Their relationship to the product is as the party responsible for how the catalogue is presented — the home page is their shopfront.
Primary goal. Have a compelling, attractive home page that represents their streaming service well and makes viewers engage with the catalogue.
Distinct accepted responsibilities.
Relevant inputs or decisions. What the catalogue contains; which title is featured; how collections are curated; how the presentation reads to a first-time visitor.
Interactions with other accepted participants. The Site Owner's presentation is consumed by the Viewer. The owner's success is observed indirectly, through the Viewer's engagement with the catalogue.
Observable success. A first-time visitor lands on the home page and immediately reads it as a premium streaming service, with the catalogue as the focal point.
What makes this role different. The Site Owner's work is presentation and representation — the concern is the quality and character of the surface the Viewer meets, not the act of watching. This is a curation-and-brand role, distinct from the Viewer's selection-and-consumption role.
Failure/recovery: if the 3D hero subject cannot initialize, the hero type block, controls, and catalogue remain fully usable and the hero degrades to a static luminous treatment. If catalogue data fails to load, the affected rail or grid shows a retry affordance while the hero stays intact.
Failure/recovery: buffering shows a progress state and resumes automatically. If the stream fails, the Watch page shows a clear failure message with a retry control; retry re-initializes playback for the same title. If it continues to fail, the Viewer returns to the home page and chooses another title. If the Viewer arrives at Watch with no title selected, a muted prompt and a return-to-home control are shown.
Failure/recovery: if the collection's titles fail to load, the entry shows a muted retry state without breaking the rest of the grid.
Failure/recovery: if poster imagery fails to load, cards fall back to a glass placeholder carrying the title name and metadata rather than a broken frame, so the presentation never degrades into a broken grid.
The creative direction is authoritative for this section. Muse: Gleb Kuznetsov. Headline idea: video as a floating holographic object — a cinema lobby at night, motion-led and content-forward.
Mode. Dark mode only.
Colour tokens (exact hex by role)
| Role | Hex | Usage |
|---|---|---|
| Background | #05060B | Deep near-black navy ground carrying the whole page |
| Surface | #0D1020 | Glass panels at 60–80% opacity |
| Text | #F2F4FF | Primary text on #05060B (~18:1 contrast) |
| Primary | #22E3FF | Electric cyan glow: focus rings, active nav, progress bars, hero rim light, hairline borders at 12% opacity |
| Accent | #FF3D8B | Magenta hot accent, used sparingly: the single Play CTA, the "LIVE" tag, one word in the headline |
| Muted | #7C86A8 | Metadata only (duration, year, genre) — never primary reading |
Body copy never sits below 4.5:1 contrast. Glass panel borders are 1px #22E3FF at 12% opacity.
Typography. Headings and body both Space Grotesk — a wide geometric techno-grotesk. Headlines at 700 weight, tight -0.02em tracking, mixed case for the big statement with one uppercase micro-label above it. Display sizes go very large: clamp(3rem, 9vw, 8.5rem) so the title behaves like a film title card. Micro-labels are uppercase 11px with +0.22em letterspacing in #22E3FF. Body is 16px/1.65. Type scale is a 1.25 modular scale: 96 / 64 / 40 / 28 / 18 / 16 / 13 / 11 (micro-label). Line lengths are capped at 62ch for synopses.
Shape language. Floating glass panels with 20–28px radii and 1px luminous edges. Thin cyan hairline strokes and radial HUD rings around the hero subject. Poster cards use a 12px radius with a soft cyan glow that appears only on focus/hover. Curves are continuous and slightly organic (superellipse-ish) — never chunky rounded-corner SaaS.
Spacing rhythm. Full-bleed dark canvas with generous vertical breathing room between bands; the hero occupies the full viewport, the trending rail bleeds off both edges, and the featured band runs full-bleed. Section eyebrows use the HUD micro-label treatment to create a consistent instrument-panel rhythm.
Imagery style. One crafted real-time 3D subject in the hero — a faceted glass prism/torus that refracts cyan and magenta light, standing in for "the stream". Everything else is content imagery: poster art and stills treated as luminous objects on the dark ground, with subtle chromatic rim light and a faint scanline overlay. No stock people smiling at laptops, no flat clip art, no abstract gradient blobs.
Explicitly avoided. Blue/indigo (#2563EB, #4F46E5, #6366F1) on white; centred headline + subtext + blue button + gradient blob heroes; Inter, Roboto, Arial, Helvetica, Open Sans, Lato, Poppins or system-ui for headings or body; grids of identical hover-lift white cards; gradient blobs or soft pastel washes; flat clip-art or stock photography of people smiling at screens; bouncy/springy easing or playful confetti motion; more than one 3D subject competing with the hero prism.
The floating holographic stream. The public entry is a full-viewport #05060B void. On the right, a single faceted glass prism floats above a faint cyan radial HUD ring, slowly orbiting with a magenta light sweep passing through it — the only 3D subject, deliberately oversized, bleeding past the right viewport edge. On the left, an uppercase cyan micro-label "NOW STREAMING", then the Space Grotesk headline at clamp(3rem, 9vw, 8.5rem) reading "Har raat, ek nayi kahani" with the final word in #FF3D8B, then a one-line muted synopsis and two controls: a solid #FF3D8B Play pill and a ghost
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!