docs: week 3 personal summary doc
This commit is contained in:
parent
a1402e3b4f
commit
32f6b08db1
@ -1,56 +1,46 @@
|
|||||||
# Ansh — Week 2 Summary
|
# Ansh — Week 3 Summary
|
||||||
|
|
||||||
## Tasks Completed
|
## Tasks Completed
|
||||||
- Task 1:
|
- Task 1: Camera preset consistency audit.
|
||||||
- Task 2:
|
- Vanilla three.js: reliable camera preset switching and stable target/focus.
|
||||||
- Task 3:
|
- R3F: reliable and predictable with state-driven camera controller.
|
||||||
- Task 4:
|
- Thob: partially reliable. Direct multi-camera `Make Default` switching was unreliable, but 3-mesh visibility toggling workaround was stable.
|
||||||
|
- Task 2: Scene preset / transform state switching audit.
|
||||||
## Strongest Product Flow In Thob
|
- Vanilla three.js: reliable state switching, deterministic transforms/visibility, smooth transitions.
|
||||||
-
|
- R3F: reliable with clean state isolation and smooth interpolation.
|
||||||
|
- Thob: reliable with 3 prebuilt meshes + radio visibility toggles, but no transition animation.
|
||||||
## Weakest / Most Awkward Product Flow In Thob
|
- Task 3: 3-step guided flow reliability audit.
|
||||||
-
|
- Vanilla three.js: reliable sequencing (forward/backward/jump/reset) with smooth camera/object transitions.
|
||||||
|
- R3F: reliable for repeated multi-step flow with predictable state behavior.
|
||||||
## Top 2 High-Value Discoveries
|
- Thob: reliable for sequencing using same 3-mesh radio-toggle approach, but instant step changes (no smooth transitions).
|
||||||
- 1.
|
- Task 4: Grouping / parent motion structural audit.
|
||||||
- 2.
|
- Vanilla three.js: reliable true group hierarchy and parent-driven inheritance.
|
||||||
|
- R3F: reliable real hierarchy with predictable parent transform behavior.
|
||||||
## Top 1 Quick Win Recommendation
|
- Thob: reliable. Parent -> child -> grandchild nesting worked correctly and inheritance stayed stable.
|
||||||
-
|
|
||||||
|
|
||||||
## Top 1 Deeper Architecture Concern
|
|
||||||
-
|
|
||||||
|
|
||||||
## If A Customer Wanted A Guided 3D Product Story Or Multi-State Scene, Could Thob Support It Well?
|
|
||||||
- Yes / Partial / No
|
|
||||||
- Why:
|
|
||||||
|
|
||||||
# Divya — Week 3 Summary
|
|
||||||
|
|
||||||
## Tasks Completed
|
|
||||||
- Task 1:
|
|
||||||
- Task 2:
|
|
||||||
- Task 3:
|
|
||||||
- Task 4:
|
|
||||||
|
|
||||||
## Most Reliable Pattern In Thob
|
## Most Reliable Pattern In Thob
|
||||||
-
|
- Structural hierarchy and visibility-based state switching.
|
||||||
|
- Nesting meshes for parent-child-grandchild inheritance is stable.
|
||||||
|
- Radio-button visibility toggling across prebuilt state meshes is repeatable and predictable.
|
||||||
|
|
||||||
## Most Fragile / Misleading Pattern In Thob
|
## Most Fragile / Misleading Pattern In Thob
|
||||||
-
|
- Direct camera preset orchestration by toggling multiple cameras (`Make Default`) can be unreliable.
|
||||||
|
- It can appear to work initially, then fail after repeated toggles or at certain positions.
|
||||||
|
|
||||||
## Top 3 Visual / Configurator Gaps
|
## Top 3 Scene / Storytelling Gaps
|
||||||
- 1.
|
- 1. Missing smooth transition primitives between authored states/steps (camera + transform + visibility blend).
|
||||||
- 2.
|
- 2. No first-class guided-flow/state orchestration model (step bundles with transition settings and reset behavior).
|
||||||
- 3.
|
- 3. Camera preset authoring and multi-camera default switching is not consistently trustworthy.
|
||||||
|
|
||||||
## Top 1 Quick Win
|
## Top 1 Quick Win
|
||||||
-
|
- Add built-in transition controls (duration + easing) for state/step switches triggered by UI controls.
|
||||||
|
|
||||||
## Top 1 Deeper Architecture Concern
|
## Top 1 Deeper Architecture Concern
|
||||||
-
|
- Interaction orchestration model is still workaround-heavy: advanced flows often require visibility swapping of separate meshes instead of native stateful runtime orchestration.
|
||||||
|
|
||||||
## Can Thob Support Product-Configurator Style Visual State Changes Reliably?
|
## Can Thob Support Multi-State Scene Flows And Guided 3D Storytelling Reliably?
|
||||||
- Yes / Partial / No
|
- Partial
|
||||||
- Why:
|
- Why:
|
||||||
|
- Reliability is good for discrete state switching using prebuilt mesh visibility toggles.
|
||||||
|
- Structural grouping/hierarchy behavior is strong.
|
||||||
|
- But advanced storytelling quality is limited because transitions are instant and direct camera preset orchestration is not always reliable.
|
||||||
Loading…
x
Reference in New Issue
Block a user