Where To?

The description states that Where To? is a single-device, pass-and-play mobile app. It allows users to:

• Set up a family roster.
• Choose nearby places (restaurants, cafés, things to do).
• Filter by minimum rating (Any, 3.5+, 4.0+, or 4.5+).
• Select one to three favorites per participant.
• Merge shared picks and generate a live bracket.
• Play Rock / Paper / Scissors matchups between representatives.
• Advance through the tournament until one place remains.

The app supports both Demo Mode (with realistic fixtures) and Live Mode (using Google Places API). It also includes features like animated reveals, random draw resolution, and direction/call sharing.

Inference The app is built for small group decision-making in physical proximity, with a focus on simplicity and fun.

The author claims that the app turns “family decision-making” into a fun, fair, and quick process, addressing the problem of low-stakes debates where the loudest voice wins.

Inference The positioning is rooted in solving a common family dynamic — not a product for large-scale or enterprise use. It emphasizes ease-of-use, engagement, and group participation.

The description states that Where To? is designed for families making group decisions about nearby places. The app is intended to be used on phones already in the possession of family members, with a pass-and-play structure where each person selects options and then plays RPS.

Inference The target customer is likely a family or small group, not an individual user or business. The ICP appears to be parents or caregivers seeking a structured way to make group decisions without conflict.

The description does not mention any pricing, monetization, or business model. It only states that the app is open-source (MIT License), and includes setup instructions and fixture data guidance.

Not evidenced No evidence of revenue streams, subscriptions, or paid features.

The project was built using:

• Expo SDK 54
• React Native
• TypeScript
• Expo Router
• React Context and Reducers
• AsyncStorage
• Expo SecureStore
• Expo Location
• Google Places API (new)
• React Native Reanimated
• Codex and GPT-5.6

The author notes that Codex and GPT-5.6 were used to accelerate development, including dependency upgrades, debugging, UI iteration, and architecture refinement.

Inference The tech stack is standard for a mobile app built with React Native and Expo. The use of AI tools suggests a developer-centric approach to rapid prototyping.

The project is described as a hackathon submission, not a product in production. It includes:

• Demo Mode enabled by default
• A public GitHub repository
• MIT License
• Setup instructions and fixture data guidance

Not evidenced No evidence of user adoption, customer base, or real-world usage beyond the author’s own testing.

The description does not mention any competitors. It is unclear whether similar apps exist in the market for group decision-making or family planning tools.

Not evidenced No competitive analysis or market positioning relative to existing solutions.

• The app is presented as a hackathon submission, not a product with traction.
• No evidence of real-world usage, user feedback, or adoption.
• No pricing, monetization, or business model described.
• The app relies on Google Places API for live mode, which may introduce dependency risks or cost concerns.
• The use of AI tools (Codex, GPT-5.6) suggests a developer-focused approach, not necessarily a scalable product.

1. What is the intended path from this hackathon prototype to a production-ready product?
2. Are there any plans for monetization or user acquisition beyond demo mode?
3. Has the app been tested with real families or users, and what feedback was received?
4. How does the team plan to scale beyond a single developer?
5. What are the technical limitations of relying on Google Places API for live functionality?