Product Design: Real-Time Street-Level Imagery in Google Maps
Assume Google Maps can refresh street-level imagery in near real time across selected covered areas, with latency on the order of seconds to a minute. Design a product that uses this capability responsibly.
Constraints & Assumptions
-
Coverage is partial at launch, so the product must make freshness and availability clear.
-
Privacy, safety, abuse prevention, and driver distraction are core constraints.
-
Do not assume unrestricted live video everywhere; design a narrow MVP that creates clear user value.
-
Use existing Maps context such as navigation, places, routes, incidents, and last-mile guidance where useful.
Clarifying Questions to Ask
-
What imagery sources are available: fixed cameras, vehicles, partners, public agencies, or user opt-in uploads?
-
Is the product for consumers, delivery drivers, ride-hail, businesses, city operations, or emergency response?
-
What latency and resolution are acceptable?
-
Which regions, sensitive locations, or use cases are excluded for policy reasons?
Part 1 - Users and Jobs To Be Done
Define target users and their jobs to be done.
What This Part Should Cover
-
Drivers, commuters, delivery workers, ride-hail drivers, pedestrians, cyclists, event-goers, businesses, and city operations where relevant.
-
Last-mile problems such as curb availability, closures, hazards, crowding, access, and pickup or drop-off uncertainty.
-
Why existing Maps data is insufficient for these moments.
Part 2 - Value Proposition and Use Cases
Explain the product value and key use cases.
What This Part Should Cover
-
Clear user benefit such as fresher confidence, safer routing, fewer failed pickups, or better access decisions.
-
A small set of high-value use cases rather than a generic live-camera layer.
-
How the product fits naturally into Maps without overwhelming users.
Part 3 - MVP and Experience
Outline a narrow MVP, user experience, and technical components.
What This Part Should Cover
-
Pilot geography, freshness indicators, live layer behavior, navigation cards, last-100-meter assist, and reporting or confirmation.
-
Ingestion, privacy filtering, scene understanding, tile delivery, freshness metadata, and rate limiting.
-
Driving-mode restrictions and graceful fallback when coverage is stale or unavailable.
Part 4 - Metrics, Privacy, and Safety
Define success metrics and address privacy, abuse, safety, and policy concerns.
What This Part Should Cover
-
Metrics for last-mile errors, pickup wait time, ETA accuracy, hazard confirmation, coverage, freshness, quality, and trust.
-
Privacy safeguards such as face and plate blurring, delay buffers, retention limits, sensitive-zone suppression, and abuse detection.
-
Guardrails for driver distraction, stalking, sensitive events, and regulatory compliance.
What a Strong Answer Covers
-
A compelling product built around real user pain, not live imagery for its own sake.
-
Practical MVP scoping and measurable success.
-
Serious privacy and safety design.
-
Trade-offs between freshness, utility, risk, and coverage.
Follow-up Questions
-
Which user segment should launch first?
-
How would you prevent stalking or surveillance misuse?
-
How fresh does the image need to be for the use case?
-
What would you do if privacy false negatives are discovered?
-
How would this integrate with route recommendations?