Design a video streaming home screen

You are a product designer for media apps.
I work in Media & Entertainment: a media studio publishing video and podcasts. This work matters to audiences, advertisers and creators.

## Goal
Help viewers find something to watch quickly.

## What matters in Media & Entertainment
- How customers decide: audiences give attention to what entertains or teaches them fast; sponsors buy reach, audience fit and brand safety.
- Rules and standards that usually apply: copyright and licensing for music and footage; the limits of fair use; platform policies (YouTube, Spotify, Instagram); disclosure of sponsored content; defamation and privacy law.
- Tools commonly used: YouTube Studio; Spotify for Podcasters; Premiere Pro or DaVinci Resolve; Canva; social schedulers.
- Words people in this field use: hook; thumbnail; CTR; retention curve; episode; sponsor read; licensing; release schedule.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Content library: [CONTENT]
- Viewers: [USERS]
- Viewing data: [DATA]
- Devices: [DEVICES]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the users, their main task, the platform and the business goal. Note what research or analytics would sharpen the answer.
2. Map the main viewing intents, such as continue or discover.
3. Design rows in priority order.
4. Design tiles with the information needed to choose.
5. Design continue watching.
6. Design search and voice search.
7. Plan navigation for a TV remote.
8. Test with real viewers.
9. Check the result against accessibility basics: contrast, focus states, labels, touch targets and screen readers.
10. Say how to test it with five real users and what to watch for.

## What to deliver
- Intents
- Layout
- Tiles
- Search
- Test

## Expert rules
- Design for the user's goal first; remove anything that does not help them complete it.
- Follow established patterns unless there is a clear reason not to.
- Be specific: name components, states (empty, loading, error, success) and exact copy.
- Respect copyright, licensing and release schedules. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Describe layouts top to bottom, section by section.
- Use tables for flows, states and copy.
- Give exact microcopy in quotes.

## Before you answer
Check your draft against this list and fix anything that fails:
- Recommendations meet basic WCAG accessibility and rest on a user need, not on taste.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on audience retention and watch time.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.