BookGuide

What the company appears to be: BookGuide is a native iPhone application that enhances reading of difficult books and classics by offering contextual annotations and visual scene generation. The app allows users to select text for explanation or visualization without breaking reading flow, with features like spoiler-safe AI assistance and a personal gallery for saved illustrations.

What changed: The project evolved from an initial concept involving AI-powered reading assistance to a refined experience focused on contextual help that preserves the integrity of the reading experience. It was built as a single-person effort over a hackathon period using Swift and NestJS, with a focus on spoiler safety and user experience design.

The single most important open question: Is there evidence of user adoption or market demand beyond the author's personal use case?

• The description states that BookGuide is a native iPhone reader for difficult books and classics.
• It provides inline annotations for historical references, unfamiliar terms, or details readers might miss.
• Users can ask more questions to receive focused answers within the book.
• The flagship feature is "Visualize Scene," which turns descriptive prose into illustrations based only on that passage and prior reading context.
• Finished scenes are saved to a personal gallery and can be reopened alongside source passages.
• Both explanations and images are designed to be spoiler-safe.
• The app includes onboarding, private-library interface, reading experience, inline annotations, Ask More, scene generation, credits, and a gallery for saved illustrations.
• Backend is built with NestJS deployed on Railway; books are prepared as trusted bundles with stable paragraph IDs and precomputed annotations.

• The description states the author started BookGuide because they encountered problems while reading The Count of Monte Cristo—specifically needing historical or cultural context and struggling to visualize descriptive passages.
• It is positioned as a tool that helps readers understand difficult texts without summarizing or replacing the book itself.
• The app aims to maintain reading rhythm by providing quiet, contextual help.
• The author claims it avoids breaking reading flow, unlike traditional search methods which disrupt immersion.
• There is no evidence of prior positioning or evolution beyond this single use case.

• Not evidenced. The description does not identify specific customer segments or personas.
• The author describes their own experience but does not name target users or markets.
• No indication of whether the app targets students, book clubs, general readers, or niche audiences.

• Not evidenced. There is no mention of pricing, monetization strategy, or business model in the description.
• The project appears to be a personal development effort rather than a commercial product.
• No evidence of revenue streams, subscriptions, or paid features.

• Built with Swift (iOS) and SwiftUI for frontend; NestJS backend deployed on Railway.
• Each book is prepared as a trusted bundle with stable paragraph IDs, reading positions, and precomputed annotations.
• When asking questions, the app sends selected paragraph and current reading position to the server.
• The system filters out future paragraphs before calling GPT-5.6 to ensure spoiler safety.
• Scene generation uses a structured scene brief created by GPT-5.6, validated by the server, then passed to GPT Image 2 for illustration.
• Codex was used as an engineering and design collaborator during development.
• The app includes onboarding, private-library interface, reading experience, inline annotations, Ask More, scene generation, credits, and a gallery.

• Not evidenced. No data about user adoption, downloads, engagement, or usage metrics are provided.
• The project was built during a hackathon (OpenAI 2026) and submitted to Devpost.
• There is no evidence of product-market fit, customer feedback, or iterative improvements beyond the single author's experience.

• Not evidenced. No mention of competitors or market landscape in the description.
• The author does not reference existing tools for reading assistance or annotation.
• No indication of how BookGuide compares to other apps or services in this space.

• Single-person development: The project was built by one person, raising questions about scalability and long-term maintenance.
• Limited evidence of traction: No data on users, adoption, or market validation beyond the author’s personal use case.
• Unclear commercial viability: No pricing model or monetization strategy is evident.
• Spoiler safety mechanism complexity: While described as a key feature, the technical implementation may be challenging to replicate at scale.
• Dependency on AI models: Reliance on GPT-5.6 and GPT Image 2 introduces risks related to availability, cost, and performance.

1. What specific problems do you observe in how people currently read difficult books or classics?
2. Have you tested BookGuide with others beyond yourself? If so, what feedback did you receive?
3. How do you plan to scale the annotation and scene generation process for multiple books?
4. Is there a path toward monetization or user acquisition beyond personal use cases?
5. What are your thoughts on integrating third-party content or partnerships with publishers?