World Cup remote director

You are a senior product engineer. Turn the product idea below into a locally runnable MVP.

## Idea

World Cup remote director
Helps fans watching multiple World Cup matches switch at the right moment and catch up on what they missed.

## Product concept

On a night when France–Morocco and Argentina–Egypt kick off at the same time, fans first select the teams and players they most fear missing. The phone then displays a large card such as, "Switch to Norway–England now: danger has just formed in front of goal," and shows how long to stay. When they return to the original match, it fills them in on what just happened in one sentence. This replaces random remote switching with a live viewing director.

## Why now (backed by facts)

On July 9, France beat Morocco 2–0 to advance to the semifinals; this World Cup expanded to 48 teams and 104 matches for the first time, while a trend snapshot shows that searches for "france vs morocco" in the United States exceeded 1 million over the past 7 days as of July 10, with growth of about 1,000%. The larger tournament and the surge of attention around key matches create a timely opening for a viewing director that gives real-time switching prompts across matches and fills in what viewers missed.

## Direction (model inference, not independently verified)

Target user: Fans following multiple World Cup matches who most fear missing key attacks or defensive moments. They open it before simultaneous kickoffs.

Minimal entry point: The first version connects only to live match data. Users select teams to follow, then receive switch prompts and a one-sentence recap when a key event occurs.

The strongest case against: The strongest case against this is that if the live event data is not fast or accurate enough, the switch recommendations will create more confusion than simply watching the scores.

These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty.

## Punching above weight (model inference)

Build shareable match-switching pages around long-tail pre-match searches such as multiple matches on the same night, team names, and "where to watch." Use a single-match free alert to drive return visits in fan groups.

## Competitors & gaps (model inference)

- FotMob: Provides scores, schedules, and personalized match alerts, but does not tell fans watching multiple matches when to switch, which match to switch to, or how long to stay.

## How it makes money (model inference)

Basic match alerts are free. Multi-match live directing and custom watch conditions are paid through a tournament pass.

## Trend background

Theme: Watching multiple matches at the 2026 World Cup
Trigger query (original English): france vs morocco
Approx. search volume: 1000000+ (approximate)
Approx. increase: +1,000% (approximate)

The trend data is a historical snapshot from the moment it was captured; volume and increase are approximate and only explain “why now.” Do not write them into product copy as precise market numbers.

## Sources

- France's powerful attack secures win against Morocco and World Cup semi-final spot (https://www.lemonde.fr/en/sports/article/2026/07/10/france-s-powerful-attack-secures-win-against-morocco-and-world-cup-semi-final-spot_6755328_9.html)
- Updated FIFA World Cup 2026™ match schedule reveals venues and kick-off times for all 104 matches (https://inside.fifa.com/organisation/media-releases/updated-world-cup-2026-match-schedule-venues-kick-off-times-104-matches)

## Deliverables

- Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery.
- Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary.
- Do not show unverified market numbers in the UI or API.
- Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge.
- If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code.
- If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype.
- When done, explain what changed, how to run it, and how to verify it.
- Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.

Helps fans watching multiple World Cup matches switch at the right moment and catch up on what they missed.

Published July 10, 2026 · 2 sources

On a night when France–Morocco and Argentina–Egypt kick off at the same time, fans first select the teams and players they most fear missing. The phone then displays a large card such as, "Switch to Norway–England now: danger has just formed in front of goal," and shows how long to stay. When they return to the original match, it fills them in on what just happened in one sentence. This replaces random remote switching with a live viewing director.

Why now

On July 9, France beat Morocco 2–0 to advance to the semifinals; this World Cup expanded to 48 teams and 104 matches for the first time, while a trend snapshot shows that searches for "france vs morocco" in the United States exceeded 1 million over the past 7 days as of July 10, with growth of about 1,000%. ^S1^S2 The larger tournament and the surge of attention around key matches create a timely opening for a viewing director that gives real-time switching prompts across matches and fills in what viewers missed.

Target user

Fans following multiple World Cup matches who most fear missing key attacks or defensive moments. They open it before simultaneous kickoffs.

Minimal entry point

The first version connects only to live match data. Users select teams to follow, then receive switch prompts and a one-sentence recap when a key event occurs.

Punching above its weight

Build shareable match-switching pages around long-tail pre-match searches such as multiple matches on the same night, team names, and "where to watch." Use a single-match free alert to drive return visits in fan groups.

Competitors & gaps

FotMob: Provides scores, schedules, and personalized match alerts, but does not tell fans watching multiple matches when to switch, which match to switch to, or how long to stay.

How it makes money

Basic match alerts are free. Multi-match live directing and custom watch conditions are paid through a tournament pass.

The case against

The strongest case against this is that if the live event data is not fast or accurate enough, the switch recommendations will create more confusion than simply watching the scores.