Uber Eyes

The description states that Uber Eyes is an AI-assisted remote-presence prototype. It is designed as a two-sided system:

• A Remote Walker physically walks in public space and provides a first-person view.
• A Viewer participates remotely through a browser or device, sending limited guided requests (e.g., pause, continue, translate).
• An AI Safety Layer mediates the interaction with features like privacy protection, route boundaries, walk-only verification, vehicle detection, sign translation, and session feedback.

The prototype uses prerecorded footage from Ginza, Tokyo, to simulate a live session. It does not include real-time streaming infrastructure or production-grade backend systems.

Inference The product is described as a proof-of-concept, not a commercial offering. It was built in 2 days for a hackathon and lacks any evidence of monetization, user base, or operational systems.

The description states that Uber Eyes began with the question: “What if someone who cannot go could still participate through another person’s eyes?”

It positions itself as:

• A new form of guided remote presence
• Not a livestreaming platform, VR experience, surveillance product, or system for human remote control
• A human-autonomy-preserving system where the Walker retains control over their own movement and boundaries

The author claims that the AI’s role is not to replace humans but to protect the space between two people, mediating presence, safety, and context.

Inference The positioning is focused on accessibility, human autonomy, and ethical remote presence. However, there is no evidence of market validation or traction to support whether this positioning resonates with users or customers.

The description states that the system is designed for people who cannot physically reach places due to:

• Mobility issues
• Illness
• Age
• Long-term care
• Cost
• Distance
• Time
• Visa restrictions

It also mentions potential use cases in education, long-term care, museums, and cultural access.

The Remote Walker is described as someone who can walk in public space and carry a first-person view — not necessarily a paid professional yet.

Inference The ICP appears to be people with physical limitations or barriers to travel. However, no evidence of actual customer segments, personas, or early adopters is provided.

The description does not state any pricing model, monetization strategy, or business model. It describes the system as a prototype and does not mention:

• Fees for viewers
• Compensation for walkers
• Marketplace or platform fees
• Subscription plans
• Revenue streams

Inference No evidence of a defined business model exists in the description.

The prototype was built with:

• React
• TypeScript
• Vite
• CSS
• GitHub
• Codex (for scaffolding and implementation)
• AIVIS (for concept design, copywriting, architecture)

It uses:

• Prerecorded video
• Local React state
• No backend, payment, or account systems

The project was completed in approximately two days during a hackathon.

Inference The technical stack is basic and not production-grade. The prototype does not include real-time streaming or scalable infrastructure, which may be required for future versions.

The description states that Uber Eyes is a prototype built for OpenAI Build Week, with no evidence of:

• Revenue
• Customers
• Users
• Product-market fit
• Commercial traction
• Production deployment
• Real-time functionality

It was built in two days and uses prerecorded footage.

Inference The project is at an early prototype stage. No maturity or traction signals are evident.

The description does not mention any competitors. It states that Uber Eyes is not positioned as a livestreaming platform, VR experience, surveillance product, or remote control system, but it does not define how it differs from existing solutions in the market.

Inference No competitive analysis or positioning against other products is provided.

• Prototype-only: The project is described as a hackathon prototype with no evidence of commercial viability or scalability.
• No monetization model: There is no indication of how the product would generate revenue.
• Unproven market need: No evidence of customer demand, user testing, or early adoption.
• Ethical and legal concerns: The concept of remote presence raises questions about safety, privacy, and consent that are not addressed in detail.
• No real-time infrastructure: The use of prerecorded video may limit the perceived value of the product.

Inference The project is highly speculative with no evidence of traction or commercial readiness.

1. What is the actual market need for this type of remote presence system?
2. How do you plan to validate demand from both Walkers and Viewers?
3. What are your plans for monetization, compensation for Walkers, and platform fees?
4. How will you scale beyond a hackathon prototype?
5. What are the legal and ethical implications of remote presence in public spaces?
6. Have you tested the concept with real users or potential customers?
7. What is the path to production-grade infrastructure and real-time streaming?