1) Problem We Are Solving

Construction teams lose time finding the right plan file when projects contain many PDFs/images and inconsistent naming.

Current pain points:

  • Plan files are scattered across folders and project handoffs.
  • Teams often remember "what they need" (for example, balcony plan) but not the exact file name.
  • On-site usage needs fast lookup without heavy enterprise tooling.

Business impact:

  • Slower field decisions.
  • Higher risk of opening the wrong plan.
  • Productivity loss in PM, engineering, and site supervision workflows.

2) Current Product (As Built)

Blueprint Navigator is now a project-first, frontend-only plan finder with routed pages and local persistence.

Current UX flow

  1. App starts on Dashboard (/):
    • Shows current projects.
    • Provides global plan search across all projects.
    • Includes voice input for search.
  2. User can go to Create Project (/projects/new):
    • Creates a named project.
  3. User lands in Project Upload Workspace (/projects/:projectId/upload):
    • Uploads PNG/PDF files into that project.
    • Can rename each uploaded file (default is original filename).
    • Opens files/pages in the viewer.

Search behavior (current)

  • Global search can parse commands like:
    • give me plans for balcony
    • give me plans for project tower-a balcony
  • If query matches multiple projects and no project is specified:
    • App asks a follow-up clarification and lists matching projects.
  • If project is specified:
    • App narrows results to that project and opens the relevant plan.

Voice behavior (current)

  • Voice transcript is captured via browser speech recognition.
  • Transcript is routed through the same query parser/search flow as typed input.

3) Technical Reality

Architecture:

  • Frontend-only React + Vite app.
  • Local persistence with IndexedDB (Dexie).
  • No backend/API server for app data.

Data model:

  • projects table (project identity and timestamps).
  • drawings table (file metadata, project link, blob storage).
  • pages table (page-level extracted text/index entries).

AI usage:

  • OpenAI model is used for query intent parsing (VITE_OPENAI_API_KEY, VITE_OPENAI_MODEL).
  • Fallback heuristic parser exists when API key is missing or request fails.

Important security note:

  • Because this is frontend-only, OpenAI API key is exposed in browser runtime.

4) Value Proposition (Current)

What the product currently delivers:

  • Fast plan lookup from a single dashboard across projects.
  • Project-based organization with dedicated upload spaces.
  • Simple natural-language queries (typed and voice).
  • Local-first storage for easy demo/deployment without backend setup.

5) Current Limitations

  • No team collaboration or multi-user auth yet.
  • No secure backend proxy for OpenAI key management.
  • No OCR pipeline for deep visual text extraction from scanned images (search is strongest when file names/metadata are meaningful).
  • Browser voice support depends on environment and permissions.

6) Business Direction (Practical Next Steps)

Phase A: Stabilize current product

  • Harden routed UX and validation.
  • Improve project disambiguation UX.
  • Add quality checks and reliability tests for search/voice flows.

Phase B: Production-readiness

  • Add backend token proxy for OpenAI (remove exposed key risk).
  • Add user/account/project permissions.
  • Add audit/logging and project activity history.

Phase C: Advanced plan intelligence

  • OCR + visual extraction for scanned/image-only plans.
  • Better ranking and project-specific search filters.
  • Optional integrations (document systems/BIM workflows).

7) Success Metrics To Track

  • Time-to-first-correct-plan from dashboard query.
  • % of queries resolved without manual browsing.
  • Voice query success rate vs typed query success rate.
  • Active projects per week.
  • Repeat usage after first project import.

8) Summary

Blueprint Navigator has evolved from a simple PDF finder into a project-centered plan search tool with routed pages, cross-project query handling, and voice-enabled lookup. The core value is now clear: quickly find and open the right plan inside the right project with minimal operational overhead.

Built With

Share this project:

Updates