PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
Omnistu Global - Everything ConnectedStart a project
Omnistu logoOmnistu
Feature scope - proposed scope

Prime Video Clone Features: The Multi-Model OTT Storefront in Full

This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.

Build scopeConfirm servicesDefine the features and exclusions
Delivery planAgree milestonesNo fixed launch duration implied
Source rightsWritten termsCheck licences and handover
OperationsTest before launchAgree acceptance and support
01 / Scope areas

Scope areas for this kind of build

The areas below are condensed from our earlier product specification for this category. They describe proposed scope we can build for you, not a finished product for sale, and no live system is implied. The exact list is agreed in writing for your project before any build starts.

02 / Feature Set by Role

Feature Set by Role

A viewer can subscribe, rent a new release, buy a boxset and watch a free ad-supported title in the same session, and the ledger accounts for all four correctly. Partners and operators each get their own console.

Viewer

  • Catalogue, playback, profiles and discovery, across Android, iOS and the browser.
  • Email, social and OTP sign-in with QR handoff to television
  • Household profiles with separate history, recommendations and kids maturity filtering
  • Hero banners, trending, new release and leaving-soon rails, genre and cast browsing

Content partner

  • Third-party catalogue listed alongside your own, settled on measured viewing.
  • Content submission with visible approval status
  • Title-level performance reporting on their own catalogue only
  • Watch-minute logging per title, measured rather than estimated

Operator

  • A multi-model service is meaningfully harder to operate than a single-plan one, which is why the console carries as much weight as the viewer app.
  • Catalogue management with pricing set per monetization model
  • Weekly, monthly and annual plans with catalogue and device limits
  • Rental windows configured per title or globally, with scheduled expiry
03 / How It Works

How It Works, End to End

On a single-plan service the journey is short: subscribe or leave. On a storefront it branches, and every branch is a different way to be paid. Here is the whole path.

Email, social and OTP sign-in with QR handoff to television. Multiple profiles per household account, each with separate watch history and recommendations, and kids profiles filtered by maturity rating rather than by a setting a child can toggle.

Discover something to watch

  • Hero banners and merchandised rows, trending, new release and leaving-soon rails, and genre, cast and crew browsing across films, series, seasons, episodes, trailers, extras and priced boxsets, alongside a live channel line-up.

Choose how to pay for it

  • The same title can sit in a plan tier, be rented at one price, be bought outright at another, or open on an ad-supported tier - and which of those are offered can differ by territory. This is the branch a single-plan service does not have.

The entitlement engine resolves

  • On every play request the engine decides which right applies, in order, server-side. A viewer holding both a plan entitlement and a rental never sees a conflict, and territory rules are enforced here rather than by hiding a title in the interface.

Watch, and be measured

  • Adaptive quality, subtitles, multiple audio tracks and 360 VR-ready playback, with watchlist and Continue Watching synced across devices per profile. Viewing is logged in watch minutes at title level, which is what makes partner settlement a measurement rather than an estimate.

Settle with partners and creators of supply

  • Each partner's share is calculated against their agreed terms from those watch minutes. Statements and payout requests run through the partner console, approval is operator-gated and attributable, and partners see only their own numbers.
04 / Why these

Every Feature Earns Its Place

A feature list tells you what exists. This tells you what each one is worth to an OTT operator, and what it costs you not to have it.

05 / Boundaries we state

Boundaries we state in writing for your build

Two of these matter more than anything else on the page, and both come up in the first serious licensing conversation. We would rather flag them before purchase than after.

06 / See exactly what you

See exactly what you are getting - before you commit

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Amazon Prime Video.

Amazon Prime Video Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to Amazon Prime Video, and how clients search for it.

07 / More pages

More pages on this build

Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Amazon Prime Video.
Amazon Prime Video Clone is used descriptively. It is how the software industry refers to building a platform with functionality similar to Amazon Prime Video, and how clients search for it.

08 / Next step

Discuss your scope by message

Tell us what you want to launch and where. We reply by email with a scoped proposal - no calls required, no phone numbers collected.

PREVIEW ONLY - nothing you enter is submitted to or stored by Omnistu. The compose button tries to copy your scope text and open your own email app; if the copy does not work, the text appears below the button so you can copy it yourself. Nothing is sent until you press send in your own email app.
Email the team instead