Projector Space

Note: This analysis is based entirely on the self-reported description provided by the author. No independent verification, traction data, revenue figures, customer names, or third-party sources are available.

The description states that Projector Space is a host-neutral Three.js runtime for projecting real HTML video across host-selected 3D geometry. It manages:

• HTML video elements and VideoTexture;
• Projector camera and projector-space mapping;
• Shader overlays for registered receivers;
• Playback state and media status;
• Receiver refresh and subtree detachment;
• Transactional construction and best-effort disposal.

It also supports:

• Independent projector pose from receiver selection;
• Media replacement without restarting playback;
• Receiver rebuilds without session interruption.

The author notes that the package was extracted from an existing application (Garden Planner) and validated in a standalone sandbox. It is described as a reusable, public API entry point.

Inference: The product appears to be a low-level runtime library for handling projective video rendering in 3D environments using Three.js. It is not a complete application but a component intended for integration into other tools or platforms.

The author claims that Projector Space addresses limitations in existing examples of projective texturing, which often stop at shader demos or single-plane projections. The goal was to build something usable inside real Three.js applications with reliable playback and lifecycle control.

The positioning evolves from:

1. A hackathon prototype within an existing editor (Garden Planner),
2. To a reusable package, extracted from that context,
3. To a public API sandbox, validated externally.

Claim: The product is positioned as a tool for developers working with 3D environments and HTML video projection, aiming to solve lifecycle complexity in projective media workflows.

The description does not identify specific customer segments or personas. However, it implies that the target audience includes:

• Developers using Three.js;
• Users of 3D editors or visualization tools;
• Teams building interactive 3D experiences involving video projection.

It is unclear whether there are any known users beyond the author’s own development environment and sandbox.

Not evidenced: No explicit customer list, user interviews, or market segmentation data.

There is no evidence of a business model or pricing structure in the description. The project is presented as a pre-release package, distributed via its public repository.

Claim: The author intends to publish it on npm after a release review, but no commercialization strategy or monetization plan is described.

The implementation followed three stages:

1. Application-scale integration inside Garden Planner;
2. Boundary extraction into a reusable package (three-projective-media);
3. Independent validation in a standalone sandbox.

Key technical features include:

• Support for muted public playback and autoplay restrictions;
• Persistent projector pose and receiver policy;
• Transactional construction and idempotent cleanup;
• Public API sandbox with multiple video sources;
• CI, tests, GitHub Pages deployment, and documentation.

Inference: The author has built a robust, modular system that separates product behavior from reusable runtime concerns. This suggests an engineering approach focused on correctness and portability.

The project is described as:

• A pre-release package;
• Built during a hackathon (Devpost submission);
• Integrated into a reference application called Nocturne Garden;
• Published with tests, CI, and documentation.

There is no evidence of:

• External adoption or usage;
• Revenue or monetization;
• Customer base or user feedback;
• Product-market fit indicators.

Absence of evidence: No traction data, customer numbers, or product usage metrics are provided.

The description does not mention competitors or similar tools. It focuses on the novelty of solving lifecycle issues in projective video rendering within 3D environments using Three.js.

Not evidenced: No competitive landscape, market analysis, or comparison to existing solutions.

1. No external adoption – The package is only used internally and in a sandbox; no evidence of real-world usage.
2. Pre-release status – Not yet published on npm or widely available.
3. Single-founder project – Only one team member (Bartek Bąk) is mentioned.
4. Limited maturity – Built during a hackathon, with no indication of long-term maintenance or roadmap beyond initial features.
5. Unclear commercial viability – No pricing, monetization, or business model described.

Red flag: The lack of external validation or traction raises questions about product-market fit and scalability.

1. What is the current level of adoption or interest from developers using this package?
2. Are there any plans to open-source or publish this on npm, and what are the timelines?
3. How does this package compare to other 3D media projection libraries in terms of performance and compatibility?
4. Has the author considered how this might scale across different platforms or browsers?
5. What is the long-term vision for the project beyond its current scope?