Hellos

The description states that Hellos is an iOS app where users receive notifications about nearby AI companions (Agents) located in real-world places like parks, cafés, or street corners. Users walk to these locations and interact with the Agents through live conversation.

• The app uses a compass and distance indicator to guide users.
• Each Agent has a personality and retains memory of past interactions.
• The experience is described as “real places, real walking, live conversation.”
• It was built using technologies including Swift, SwiftUI, Node.js, OpenAI APIs, PostgreSQL, Supabase, and RealityKit.

Inference The product appears to be a proof-of-concept or prototype for an AI companion system integrated with physical space and location-based interaction. It is not evidenced to have launched beyond the hackathon stage.

The project is self-described as a step toward a world where AI agents live in real-world settings, inspired by the fictional world of Summer Wars (2009). The authors claim that Hellos is an early milestone in building such a world — specifically, enabling users to walk to meet AI companions.

• The tagline: “Hellos lets AI companions live in the real world — at the park, the corner cafe, down your street.”
• The vision includes agents helping with everyday tasks (e.g., airport check-in) and enriching social interactions.
• It is positioned as a counterpoint to screen-based AI use, aiming to bring more life into users’ routines.

Inference The positioning is aspirational and conceptual. There is no evidence of actual market traction or commercial adoption beyond the hackathon submission.

The description does not clearly define a specific customer segment or ideal customer profile (ICP). It implies that the target user is someone who spends time at desks, uses AI tools like Codex, and wants to take short walks for meaningful interaction.

• Users are described as those who “sit in front of screens all day” and want more life.
• The experience is framed around a walk — suggesting users may be urban dwellers or remote workers.
• There is no mention of demographics, personas, or user behavior beyond the general use case.

Inference The ICP is not clearly defined. It appears to be a broad audience of desk-based individuals seeking real-world AI interaction.

There is no evidence in the description of a business model or pricing strategy. The project is described as a hackathon submission and does not mention monetization, subscriptions, partnerships, or any revenue-generating mechanism.

Inference No business model or pricing data is evidenced.

The project was built using technologies including:

• iOS (Swift, SwiftUI)
• Node.js
• OpenAI APIs (Codex, GPT)
• PostgreSQL, Supabase
• RealityKit for 3D rendering
• MapKit for location services
• Figma and FigJam for design

• The team used Codex as an implementer and teacher.
• The development process involved iterative testing on the street ("walk, note what feels off, fix it, walk again").
• The app is described as having a “minimum spec around one core experience.”

Inference The technical stack suggests a prototype built with modern tools for iOS and AI integration. No evidence of production-grade infrastructure or scalability.

There is no evidence of traction, revenue, customers, or adoption beyond the hackathon submission.

• The team states they are two people.
• It was submitted to a hackathon (OpenAI 2026).
• No mention of users, downloads, usage metrics, or product launches.
• No funding or investor involvement is mentioned.

Inference The project has not demonstrated any traction or maturity beyond the prototype stage.

The description does not provide information about competitors or market positioning. It references Summer Wars as inspiration but does not name or describe existing products in this space.

Inference No competitive analysis is evidenced.

• Prototype-only: The project is described as a hackathon submission with no evidence of real-world deployment.
• No traction or revenue: There is no indication of users, adoption, or monetization.
• Founder limitations: Both founders are described as non-engineers, which may raise concerns about execution capability.
• Unproven market demand: No evidence that users actually want or need this type of experience.
• Technical risks: The app relies on iOS and location-based features, which may be difficult to scale or maintain without dedicated engineering resources.

Inference The project is at a very early stage with no demonstrated commercial viability or user engagement.

1. Has the prototype been tested beyond the hackathon? What feedback did users give?
2. Are there any plans to scale beyond the current prototype, and if so, how?
3. What is the long-term vision for monetization or business model?
4. How do you plan to build a sustainable team or product beyond the two-person hackathon effort?
5. Have you considered privacy or safety implications of AI agents in public spaces?