EchoWorld: Turn Photos Into Spatial Worlds

The description states that EchoWorld is a native iPhone app with two workflows:

1. Create World: Starts with a place photograph or 2D map. It prepares a spatial generation prompt, creates a World Labs environment, anchors a portal to the real floor, and lets users enter the result in augmented reality.
2. Restyle Room: Starts with a photograph of the user's current room. The user chooses a style, GPT Image 2 creates a redesign while preserving the room's permanent architecture, and World Labs turns the approved direction into a spatial world that can be experienced at human scale.

Both workflows include deterministic, on-device demos created from real API outputs so judges can experience the complete product without waiting for generation or spending credits.

Evidence Self-reported by author. No independent verification.

The description states that EchoWorld began with one question: "what if a flat image could become somewhere you could revisit, inspect, and move through?"

It also claims:

• Photos are good at preserving how a place looked from one position, but not how it felt to be surrounded by it.
• The same limitation appears in interior design: a beautiful concept image can still leave you guessing about scale, circulation, and whether the room will feel right in real life.

The project positions itself as solving limitations of static images and 2D design concepts through AR and AI.

Evidence Self-reported claims. No evidence of market validation or customer feedback.

Not evidenced.

The description does not identify specific target customers, personas, or ideal customer profiles (ICPs). It describes general use cases but does not name who would buy or use this product.

Not evidenced.

There is no mention of pricing models, monetization strategies, or business model assumptions in the provided description.

The app is built in Swift and SwiftUI for iOS. GPT-5.6 runs behind the interface as a structured prompt orchestrator: it translates the source image, map, style choice, and user direction into controlled instructions for GPT Image 2 and World Labs. GPT-5.6 does not render the image or the world itself.

GPT Image 2 produces the redesigned-room image. World Labs Marble 1.1 generates panoramic imagery, a mobile collider GLB, and an SPZ Gaussian-splat asset.

ARKit supplies the phone's changing six-degree-of-freedom pose, while native Metal and MetalSplatter render up to roughly 500,000 splats. SceneKit and GLTFKit2 handle portal placement and the invisible spatial anchor.

Generated assets are cached locally so interrupted workflows can resume.

Codex was used as a development partner across the build, helping with architecture, client implementation, diagnostics, integration of Metal splat renderer, calibration, refinement, and demo assembly.

Evidence Self-reported technical details. No evidence of production deployment or performance metrics.

Not evidenced.

There is no mention of revenue, customers, user adoption, or any traction indicators beyond the hackathon submission. The project is described as a prototype or demo.

Not evidenced.

The description does not reference existing competitors or market positioning relative to other AR/3D design tools or AI-powered spatial applications.

1. No commercial traction: This is a hackathon submission with no evidence of revenue, customers, or adoption.
2. Unverified claims: All statements are self-reported and unverified; there is no independent validation of the product’s functionality or market demand.
3. Limited scope: The app is described as a native iOS app with on-device demos, suggesting it may not scale beyond this environment.
4. Dependency on external APIs: Heavy reliance on GPT-5.6, World Labs, and other third-party services introduces risk if those APIs change or become unavailable.

1. What is the actual business model behind EchoWorld? Is there a plan to monetize this beyond the hackathon?
2. Have you tested the product with real users outside of the development team?
3. How do you intend to scale beyond iOS and native ARKit support?
4. Are there any plans for backend infrastructure or data storage?
5. What is your path to market, and how do you plan to reach potential customers?