The Veil

The Veil is an augmented reality (AR) ghost-hunting game for iPhone, built as a hackathon project by one developer, Tilo Delau. The app uses ARKit, RealityKit, and Metal to render spectral anomalies and ghosts in the real world. It includes features like a spectral scanner, animated companion, and ghost manifestation. The project is self-reported as an MVP demonstrating core gameplay mechanics.

The author states that the game aims to make the real world "haunted" for casual, spontaneous play with friends. It leverages GPT-5.6 and Codex to accelerate development, particularly in rendering and experimentation.

The description states that The Veil is an AR ghost-hunting game for iPhone. It uses:

• ARKit
• RealityKit
• Swift
• SwiftUI
• Metal shaders
• GPT-5.6
• Codex

Features include:

• Spectral scanner
• Animated Ecto companion
• Spectral anomaly detection
• Custom RealityKit rendering
• Essence collection
• Ghost manifestation

The author describes it as a "mobile AR game" where users can "open up your phone at any time and engage with it."

Inference The product is an experimental, single-developer AR game prototype. It is not evidenced to have reached market or user adoption.

The description states that the inspiration for The Veil was to create a casual, spontaneous game for friends to play together. The author describes it as a way to "make real life a bit entertaining" and treat the world as a "game world."

The positioning is self-reported: it is an AR ghost-hunting game where users interact with paranormal activity in their environment.

Inference The project is positioned as a casual, social AR game. It is not evidenced to have evolved from any prior product or market positioning.

The author states that the goal was to create a game for "friends casually and spontaneously." There is no further segmentation of customer type or persona described.

Not evidenced No evidence of target customer demographics, usage patterns, or specific user needs beyond casual play.

There is no evidence in the description of any business model or pricing strategy. The project is described as a hackathon MVP with no mention of monetization, subscriptions, or sales.

Inference No commercial model is evident from the description.

The project was built using:

• Swift
• SwiftUI
• ARKit
• RealityKit
• Metal
• GPT-5.6
• Codex

The author notes that:

• Codex accelerated development, particularly in rendering and shader iteration.
• The biggest technical challenge was generating 3D models for ghosts.
• A custom rendering pipeline was built using layered entities, Metal shaders, geometry deformation, emission, and transparency.

Inference The project is technically ambitious for a single developer. It shows early-stage experimentation with AR rendering and AI-assisted development.

The description states that this is a hackathon MVP, not a product in the market. It includes:

• A prototype
• Core gameplay loop
• No evidence of revenue, users, or adoption

Not evidenced No traction data, user metrics, or commercial milestones.

There is no mention of competitors or market context in the description. The author does not reference existing AR games, ghost-hunting apps, or similar products.

Not evidenced No competitive analysis or positioning relative to other players.

• Single developer: The project is built by one person (Tilo Delau), which raises questions about scalability and long-term maintenance.
• Hackathon MVP: The product is described as a prototype, not a finished product. No evidence of market readiness or commercial viability.
• Technical complexity: The author notes significant technical challenges in rendering ghosts and building custom pipelines, suggesting high development risk.
• No monetization strategy: There is no evidence of any business model or pricing approach.

Inference The project is at an early stage with no demonstrated path to market traction or revenue.

1. What is the plan for transitioning from this hackathon MVP to a product that can be monetized?
2. Are there any plans for user acquisition, community building, or marketing?
3. How does the team intend to scale beyond one developer?
4. What are the technical and artistic challenges that remain unresolved?
5. Is there any interest in partnerships or distribution channels?