17 lines
1.2 KiB
Markdown
17 lines
1.2 KiB
Markdown
## Product Lens
|
|
- Is this pattern useful for real customers? Yes
|
|
- What kind of customer use case does this support?
|
|
- Product inspection: users switch between front/side/top detail viewpoints.
|
|
- Guided tours: sequenced camera jumps between key points of interest.
|
|
- Storytelling/marketing: deliberate framing changes to control narrative focus.
|
|
- Does Thob feel strong enough for this use case?
|
|
- Partial.
|
|
- From my Task 1 test, there are two ways:
|
|
- Way 1: three separate meshes/scenes with one perspective camera setup each, then toggle visibility using radio buttons. This was stable.
|
|
- Way 2: one mesh + three perspective cameras, toggling `Make Default` using radio buttons. This was unreliable (sometimes appears, then disappears after repeated toggles; sometimes works only at certain positions).
|
|
- So today, Thob is okay for workaround-based flows, but direct camera preset switching reliability is not strong enough yet.
|
|
- What would improve the experience?
|
|
- Native camera preset system with explicit position + target/focus per preset.
|
|
- Clear interaction binding: control -> target camera/preset -> action.
|
|
- Deterministic behavior under fast repeated switching.
|
|
- Better visual/debug indication of which camera is active and why. |