anshk/builder-research
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add week1 personal summary

Browse Source
This commit is contained in:
anshk 2026-03-31 15:59:44 +05:30
parent 6f00dddd73
commit fa5cc4f1d7
1 changed files with 17 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
Week-1/Week-1-PersonalSummary.md
View File

@ -1,26 +1,30 @@
# Ansh — Week 1 Summary # Ansh — Week 1 Summary
## Tasks Completed ## Tasks Completed
-Task 1: - Task 1: Built and compared a parent-child hierarchy (Sun -> Earth) in Vanilla, R3F, and Thob. Confirmed that basic parent transform inheritance works in all three, while Thob showed visual instability when editing child local position under transformed parent setups.
-Task 2: - Task 2: Built and compared a 3-level hierarchy (Sun -> Earth -> Moon). Vanilla and R3F stayed predictable for local vs inherited transforms. Thob was partially successful, but deeper nesting made transform behavior harder to reason about and trust.
-Task 3: - Task 3: Tested duplicate object and duplicate group behavior. All three supported duplication and preserved structure/transforms. Thob duplication was fast but always independent copy-paste, with no linked duplication mode.
-Task 4: - Task 4: Tested basic rotation/motion. Vanilla and R3F supported full custom per-frame animation. Thob supported only preset animations, so motion was possible but not truly customizable.
## What Thob Supports Well ## What Thob Supports Well
-1. - 1. Very fast visual setup for basic scenes and hierarchy creation without code.
-2. - 2. Quick duplicate workflow for both single objects and grouped structures.
-3. - 3. Easy entry-level motion using built-in presets for non-technical users.
## What Feels Weak / Awkward ## What Feels Weak / Awkward
-1. - 1. Local vs inherited transform behavior is not transparent enough in nested hierarchies, making debugging difficult.
-2. - 2. No linked duplication option (only independent copies), which limits synchronized editing workflows.
-3. - 3. Motion tooling is preset-only, so custom animation logic is not possible for use cases beyond simple demos.
## Most Product-Relevant Discovery ## Most Product-Relevant Discovery
- - Builder speed is valuable, but trust depends on transform predictability and controllability. As soon as hierarchy depth increases or motion needs become custom, reliability and clarity matter more than fast setup.
## Best Improvement Recommendation ## Best Improvement Recommendation
- - Prioritize transform reliability and visibility first: add a clear local/world transform inspector, inheritance path visibility for nested objects, and stable parent-child-grandchild behavior when editing position and scale. This would remove the biggest source of confusion across multiple tasks and unlock more advanced scene authoring confidence.
## What I Learned About Vanilla vs R3F vs Thob ## What I Learned About Vanilla vs R3F vs Thob
- - Vanilla three.js gives maximum control and predictable behavior, but requires more setup and deeper technical understanding.
- R3F keeps most of Vanilla's control while making scene structure and updates cleaner through declarative components.
- Thob is the fastest for initial visual authoring, but currently feels constrained for advanced workflows due to transform debugging gaps, limited duplication semantics, and lack of custom animation authoring.
Overall, Week 1 showed that Thob already has strong foundations for beginner and rapid prototyping workflows, but needs stronger transform tooling and deeper control surfaces to support production-level 3D interaction design.