GloryMap

The description states that GloryMap is an interactive map for films, TV series, and books. It enables users to:

• Search any city and explore verified filming locations and literary settings.
• Search for a specific film, series, or book within the selected city.
• Import personal libraries via Letterboxd ZIP or IMDb CSV files processed locally in the browser.
• View location cards with story context, source links, present-day photos, and AI-matched scene references.
• Build real walking routes between 3–5 locations based on distance and duration.
• Generate time-bounded tours (30, 60, or 120 minutes).
• Receive spoiler-aware AI-written guides for each stop.
• Listen to the tour using OpenAI-generated narration.
• Upload local photos and use an overlay to recreate scenes without sending images to a server.

Inference The product is described as a web-based application built with Next.js, React, Leaflet.js, and deployed on Vercel. It integrates data from Wikidata, TMDB, OpenStreetMap, and uses AI models like GPT-5.6 for research and narrative generation.

The description states that the idea came from a hackathon in Israel where the team asked: “How amazing would it be to walk through the places connected to a film, series, or book you truly love?” This framing positions GloryMap as an experience that bridges fictional storytelling and physical exploration.

Inference The positioning evolved from a personal curiosity (walking through stories) to a tool that supports both individual exploration and potentially collaborative or community-driven experiences, as suggested in the "What's next" section.

The description does not explicitly define a target customer or ideal customer profile (ICP). It implies that users are fans of films, TV series, or books who want to explore real-world locations tied to those stories.

Inference The primary user persona seems to be someone interested in pop culture, travel, and immersive experiences — likely niche enthusiasts or hobbyists rather than a broad consumer base.

There is no evidence of pricing, monetization strategy, or business model in the description. The project is described as a hackathon submission with no mention of revenue streams, subscriptions, or paid features.

Not evidenced No indication of how the product would generate income or whether it intends to be sold or offered for free.

The description states that GloryMap was built using:

• Frontend: Next.js, React
• Mapping: Leaflet.js, OpenStreetMap
• Data Sources: Wikidata, TMDB
• AI Tools: GPT-5.6, ChatGPT, Codex, OpenAI Vision, Text-to-Speech
• Deployment: Vercel
• Validation: Structured Outputs, Zod schema validation, geographic boundary checks

Inference The team used AI-native workflows extensively, including code generation, testing, and debugging via Codex. They also implemented local processing for privacy and structured output to prevent errors.

The description states that this is a hackathon project submitted to the OpenAI 2026 Build Week hackathon. It includes:

• A complete end-to-end version built in ~3 hours
• 89 automated tests
• Production builds and real-browser verification
• Support for importing personal libraries locally
• Graceful fallbacks when services fail

Not evidenced No evidence of user adoption, customer base, or usage metrics beyond the hackathon.

The description does not provide any information about competitors or similar products. It does not reference existing mapping tools, travel apps, or story-based location platforms.

Not evidenced No competitive landscape or differentiation analysis is provided.

• No traction or revenue: The product exists only as a hackathon demo with no evidence of real-world usage.
• Unverified data sources: Reliance on Wikidata, TMDB, and other external databases may lead to inconsistencies or inaccuracies.
• AI dependency: Heavy reliance on AI for content generation raises risks if models change or become unavailable.
• Limited scope: The product is described as a prototype with no indication of scalability or long-term roadmap beyond the hackathon.
• Privacy claims: While local processing is mentioned, there’s no evidence of how data is stored or managed post-import.

1. Has the product been used by anyone outside the development team?
2. Are there plans to monetize the platform? If so, what is the business model?
3. How does the team plan to scale location coverage and improve data accuracy?
4. What are the technical limitations or bottlenecks in current implementation?
5. Is there any intention to expand beyond films/TV/books into other types of content?
6. How do you intend to handle user-generated content or community contributions?