Subscription streaming storefront
Plans, devices, and catalog claims lived in reseller chats. We shipped a bilingual storefront that sells the subscription and explains device coverage before support has to.
The situation & problem
An IPTV product needed a public commercial surface: plans, device compatibility, catalog scale, and an Arabic / English switch.
The operational constraints
The sales page had to carry large catalog numbers and a device matrix without collapsing into a single long landing scroll.
Architectural tradeoffs & what was refused
A one-page sales letter with no plan object. An app-store listing with no owned checkout narrative.
What I built & shipped
Plan pages, device coverage, bilingual information architecture, support narrative, and subscribe / learn-more paths.
Architecture & stack
TypeScript, Next.js storefront, bilingual routing. Plan objects in the page layer instead of a chat price list.
Result & measurable impact
Prospects can compare plans and devices without waiting for a reseller reply.
Next iterations & roadmap
Bind plan SKUs to the provisioning system so the storefront is the source of truth.
System surfaces & interface captures
Hover and click any record to open the full-resolution pixel inspector with zoom lens and 1:1 precision.
Have a similar constraint?
Tell me where your current operational system or product is breaking.