Tree Node Interactions

Hover Behavior:

Move cursor over any rectangular node in the tree
Node brightens slightly and border becomes more prominent
Tooltip appears near cursor showing:
- Node label (e.g., "Average Motion Sickness")
- Node value (e.g., "5.2/10")
- Node type/context (Root, Gender category, or Metric)

Tooltip Position:

Tooltip follows cursor smoothly
Auto-repositions to avoid going off-screen
Disappears when cursor leaves node
Smart positioning: appears to cursor right/below when possible, reverses if near screen edge

Radar Chart Interactions

Data Point Hover:

Move cursor over any colored point on the radar lines
Tooltip displays metric name and exact value for that gender
Example: "Male - Average Age: 34.5"

Center Hotspot Hover:

Move cursor to the center of the radar chart
Displays comprehensive summary tooltip
Shows all four metrics for each visible gender category
Useful for quick multi-metric comparison

Icon Label Hover:

Move cursor over gender label and count in corner
Confirmation tooltip appears (e.g., "Male: 152 users")
Provides quick reference for demographic breakdown

Filter Controls

View Selection (Primary):

Click "Individual" button to see three separate trees
Click "Summary" button for consolidated tree + headset filters
Click "Charts" button for radar visualization + headset & gender filters
Active view highlighted in blue with solid border

Headset Checkboxes (Summary & Charts Views):

Click checkbox to include/exclude a VR headset
Multiple selections allowed and encouraged
Selection labeled in tree title (e.g., "Summary: PlayStation VR, Oculus Rift")
Unchecked devices' data immediately excluded from visualization
All three devices selected by default

Gender Toggle Buttons (Charts View Only):

Click button to toggle gender category on/off
Button color fills when gender is selected
At least one gender must remain selected
Last selected gender cannot be deselected
Radar chart updates immediately to show only selected genders
Icons disappear if their gender is deselected

🚀 Getting Started

Initial Setup

Load the Application
- Open index.html in a modern web browser
- No build process or server required
- Works on desktop, tablet, and mobile devices
Wait for Data Load
- CSV file loads automatically on page open
- Small loading delay (data parsed and converted to n umubers)
- Visualization appears once data is ready

First-Time Usage

Select a View Mode
- Click one of three view buttons at top:
  - "Individual" (default: shows three trees)
  - "Summary" (shows consolidated view)
  - "Charts" (shows radar and demographics)
Explore Individual Trees (if viewing Individual)
- Three trees display side-by-side (or stacked on mobile)
- Each tree represents one VR headset
- Hover over nodes to learn about metrics
- Trees are read left-to-right: Root → Gender → Metrics
Apply Filters (if viewing Summary or Charts)
- Summary View:
  - Use checkboxes to select/deselect VR headsets
  - Tree updates instantly to show only selected devices
- Charts View:
  - Use headset checkboxes to filter devices
  - Use gender buttons to filter demographics
  - Radar and icons update in real-time
Interpret the Visualizations
- Tree size: Larger boxes = higher values
- Tree color: Indicates node type (green=root, b lule=male, pink=female, orange=other)
- Radar shape: Pentagon = balanced metrics, pointed s tatr = unbalanced
- Radar size: Larger polygon = higher average values
Generate Insights
- Compare metrics across genders using Summary view
- Check if certain devices cause more motion sickness
- Identify which demographics have longest sessions
- Find immersion correlations with age or gender

🎨 Visual Design System

Color Palette

| --------|- | - -----|---|| ------- | ---------|----| --| -- |oo Rt Node | G reGGe | # 4C##A50 | All Users total | | M|l Me | B luBBe| # 21##9F3 | Male gender category | | F|m Fale | Pi | Pink E91EE963 | Female gender category | | Other | O raOOne | # FF ##900 | Other gender identity | | M|eric Nodes | Light Blue | #B3E5FC | Calculated averages | | C||onections | G Gra| # 99 ##999 | Tree branch lines | | B|c Bkground | O f OO-hite | # #F5FA | Page background | | C||ads | W hiWWt | # FF##FFF | SVG backgrounds |

#Typography

Heading/Title: 14-16px, bold, dark gray (#222)
Node Labels: 9-10px, bold, black
Node Values: 8-9px, medium weight, dark gray (#444)
Tooltips: 12-13px, white text on dark background
Buttons: 13-14px, varies by state

Responsive Breakpoints

| ------------------- | ----------------- | ---------- | -------|-----------------| ----- 4 <80px (Mobile) | 1 c1l cumn, stacked | 350px | V erVVtcal stack, touch-friendly | | 480-768px (Tablet) | 2 c2oumns | 3 8033p | S id SSeby-side pairs, wrapped | | 7|8 7-1200px (Laptop) | 2-3 columns | 3 8033-00px | F Fil available space | | >|1 >200px (Desktop) | 3 c3oumns | 4 0044p | F ixFFe widths, centered |

#Interactive Feedback

Hover Effects: +15% brightness, +1px border width
Button Active: Blue fill (#2196F3), solid border
Disabled Elements: 50% opacity, cursor changes to "no t-nolowed"
Transitions: 0.2-0.3s ease for smooth animations

💻 Technical Architecture

Technology Stack

| Technology | Purp ose | V io | ion|--- ------|-----|-- -----------------------|------ | --|--- |-| Re - actUI c omIonenmpot framework | 19. .0 1| |.0 D3 js D3D3 Tree /hi reereerchical visualization | 7.9.0 | | Ch artChCh. | Rada r adat rendering | Late st eCDNst | | HTML5 Canvas | 2D rendering for charts | Nati ve i| |ve ES M ESESoles | Code onigzation | Nati ve i| |ve CS 3 CSCS|esp ons espesp styling | Nati ve i|

ve |

  F###Organization

D aFtalw

###Br Bror Support

Chrome/Edge: Full support, ES6 modules
Firefox: Full support, ES6 modules
Safari: Full support, ES6 modules
Mobile Browsers: Responsive layout, touch-friendly
Minimum Requirements: ES6 module support, Canvas API, SVG s G supp

📊 Section-by-Section Breakdown

Section 1: Individual Tree Views

What it shows:

Three

seatea hierarchical visualizations

One tree per VR headset (PlayStation VR, HTC Vive, Oculus Rift -) tll) A)wauped by upedgender with averaged metrics

How to read it:

Left s

idgre en box) = Total users for that headset

Three branches from root = Male, Female, Other genders
Right side leaves = Four metrics (Age, Sickness, Duration, Immersi

Bo) x size corresponds to value (larger = higher number)

Interpretation tips:

Compar

e e srhapes across devices

Narrow leaf (e.g., motion sickness = 2.1) = good for that metric

lWieaf (e.g., motion sickness = 8.7) = potential issue
If one gender branch is much larger, that demographic dominat

t tdevice

When to use:

Initia

l lorxation of each device

Understanding device-specific patterns
Baseline comparison before viewing aggregates

Section 2: Summary View

What it shows:

Single

colindated tree combining selected headsets

User count aggregates across devices
Averaged metrics now represent the combined dataset

How to read it:

Same t

retru cture as Individual view

Root node count = sum of all selected headsets
Gender branches = combined males/females/others from selecte

d des

Leaf values = averages across the filtered dataset

Filtering workflow:

Unche

ckvicdes you want to exclude 2. Tree regenerates with remaining data 3. Title updates to show which devices are included 4. Compare different combinations to find patterns

Interpretation tips:

If Pla

ySiona VR + Oculus shows high motion sickness but individ

thlley're low, different user demographics

Subset comparison: try just PlayStation + HTC to see if pattern

-ol Watch how averages shift as you add/remove headsets

When to use:

Market

-w andalysis across devices

Testing hypotheses about user behavior
Comparing subsets (e.g., "do premium devices attract differe

rs u?")

Generating management reports

Section 3: Charts (rWhatshow it s:**

Radar

ch wirth four metrics plotted in 2D space

Gender icons in corners with demographic counts
Center hotspot for summary statistics

Radar Chart Explanation:

Each a

xiepr esents one metric (Age, Motion Sickness, Duratio

er Ision)

Each colored polygon = one gender's data
Polygon size/shape shows relative performance across metrics

laOvpping areas show similarities between genders

Reading the Radar:

**Larg

e ygoon:** Gender has high average values

Pointed corners: Good performance in specific metrics
Rounded polygon: Balanced performance
Small polygon: Lower average values

Gender Icon Components:

**Visu

alon:i** SVG figure illustration in gender color

Label: Gender name
Count: "n = X" shows number of users in that demogra

icPosition:** Top-left (Male), Top-right (Female), Bottom-

Otfther)

Filtering on Charts:

**Head

se** sCheck/uncheck to include/exclude devices from ra

r Genders: Click buttons to show/hide gender polygons

Constraints: Must have at least one gender visible

Interaction features:

Hover

dapoiants → see specific metric value

Hover center → see all metrics summary
Hover icons → confirm user count

Interpretation tips:

If Fem

aloly gon is much larger, females in your dataset rate th

iggsher

If Male age point is far right, males are older on average
Comparing radar shapes: are males more immersed? Do females

iexpnce more sickness?

Test filtered subsets: "Do older users have longer session

W" hen to use:*

Demogr

ap anialysis and comparison

Understanding gender-based user experience differences
Identifying outlier metrics
Creating presentable comparative charts

⚙️ Advanced Features

Responsive Design Implementation

Mobile-First Approach:

Base s

ty taerget small screens (< 480px)

Breakpoints scale up from there
Touch-friendly button sizes (minimum 44px × 44px)
Vertical scrolling preferred over horizontal

Adaptive Layouts:

Indivi

duVielw: Stacks vertically on mobile

Trees reduce size but maintain proportions
Summary and Charts: Center with max-width for readability
Tooltips reposition to avoid screen edges

Real-Time Data Filtering

Filtering Architecture:

No dat

a alceulation → pure filtering of existing data

New aggregations computed immediately
Tree structure rebuilt with filtered data
Radar chart dataset updated with new averages

Performance Considerations:

CSV pa

rsapp ens once at startup

Filter operations are O(n) = fast even with large datasets
Tree layout recalculation < 100ms
Smooth visual transitions between states

Tooltip System

Smart Positioning:

Calcul

atoffdset from cursor (10px right/below)

Viewport boundary detection
Automatic repositioning if would go off-screen
Fixed positioning keeps tooltips visible during scroll

Content Adaptation:

Differ

enool tip formats for different elements

Node tooltips: include type/context
Metric tooltips: show actual values
Icon tooltips: confirm demographic labels
Center hotspot: comprehensive summary

🔍 Metrics Deep Dive:# Ra:# Ra Ager*Scals)

e:* Real-world ages from user population **Meaning ** A:eragver e ofguser in that demographic Implica ionst -:Older us

ers50):( May have different VR tolerance

Younger users (<25): Likely more gaming experience
Age differences by gender: Marketing targeting clues
Age differences by device: User preference correlation

Example interpretation:

PlayStat

ion femVale users average 45 years

HTC Vive female users average 28 years
PlayStation VR may attract different demographic

Motion Sickness (0-10 Scale)

Scale: 0 = No sickness, 10 = Severe nausea **Meaning ** A:eragver ported motion sickness level Implica ionst -:Score >

6: nifiicant usability issue

Score < 3: Device/content well-designed for comfort
Differences by gender: Women may report differently than men
Dif

fs beny device: Hardware/tracking quality matters

Correlation with duration: High sickness = shorter sessions

le xainterpretation:*

PlayStat

ion malVe users: 5.2/10 sickness

HTC Vive male users: 3.1/10 sickness
HTC Vive appears more comfortable for males

Duration (Minutes)

Scale: Session length from 0 to 60+ minutes **Meaning ** A:eragver sesRion sength before logout/break Implications:

Longer d

uran = ihigher engagement/tolerance

Shorter duration = content too intense or device uncomfort

aCore relates with immersion: Immersed users stay longer

May inverse-correlate with motion sickness: Sickness forces ex

irke- ting proxy: Engagement metric

Example interpretation:

High imm

ers useors stay 45 minutes on average

Low immersion users stay 15 minutes on average
3x engagement difference suggests immersion quality matters

#ers Iion Level (0-5 Scale)

Scale: 0 = Not immersive, 5 = Completely immersive Meaning: User's subjective sense of presence in VR Implications:

Score >

4: ellexnt user experience

Score < 2: Breaks sense of presence
Correlates with duration: Immersed users stay longer
May vary by content, not just hardware
Key metric for VR effectiveness

Example interpretation:

PlayStat

ion femVales: 3.8/5 immersion

Oculus Rift females: 2.1/5 immersion
PlayStation VR provides better female user immersion

🎯 Common Analysis Workflows

Workflow 1: Device Comparison

Switch to

Inddual vview 2. Compare tree shapes for PlayStation VR vs HTC Vive vs Oculus Rift

or Looconsistent patterns in motion sickness or duration 4.

t:Ins Which device has the best user experience?

Workflow 2: Gender-Based Analysis

Switch to

Cha viewt 2. Examine radar polygon shapes for each gender 3. Look at icon counts to understand demographic breakdown 4. Insight: Do different genders experience VR differently

rkf###low 3: Demographic Targeting

Use Summa

ry v withe specific headset combinations 2. Check age ranges for each gender 3. Combine with duration to understand engagement 4. Insight: Which demographic is most engaged with which device?

w 4ork: Troubleshooting User Experience

Look for

hightion msickness (> 6/10) in any category 2. Compare duration for that group 3. Check if immersion rating is also low 4. Insight: Hardware/content causing discomfort needs fixing

5:rkf Market Expansion

Analyze w

hichvice/dgender combination has lowest immersion 2

r ionst opportunity for improvement 3. Check if motion sickness is related to low immersion 4. Insight: Targeting this segment with better content could expan

--ark-

📱 Mobile Experience

Touch Interactions

Hover effect

s reped witah tap/hold feedback

Tooltips appear on tap, dismiss on tap elsewhere
Buttons enlarged for touch targets (48px minimum)
Scrolling enabled for long content

Screen Adaptations

< 480px: Sin

gle-cmn laylout, stacked trees

< 600px: Reduced font sizes, simplified spacing
Full-width SVGs scale responsively
Radar chart height reduced but maintains aspect ratio

Performance on Mobile

Smaller tree

dimeons tos reduce rendering load

Tooltip positioned intelligently to avoid occlusion
Canvas rendering optimized for tablet processors
Touch events debounced to prevent double-triggers

🐛 Troubleshooting

Data Not Loading

Issue: CSV

file found o- Solution: Verify "Virtual Reality Experiences.csv" is in same directo

ry ax.htmlin

Check: Browser console for 404 errors

Trees Not Rendering

Issue: SVG

appeablank -s Solution: Wait for data to load (check browser network tab)

**Check

:** browssuer supports ES6 modules (Chrome 63+)

Toolt

ips ing Ofpefscreen

Issue: Too

ltips off atu screen edges

Solution: This is auto-corrected, may need to move cursor
**Chec

k:**er zoorom level (try 100%)

Mobile Layout Issues

Issue: Tre

es ovepping olr too narrow

Solution: Rotate device to landscape for more space
Check: Browser zoom reset to 100%

📞 Support & Questions

For technical issues:

Check browser co

nsole () for er1ror messages

Verify data file exists and is properly formatted
Test in different browser
Check that JavaScript is enabled

For data interpretation questions:

Review "Metrics

Deep Di sectione above

Check "Interpretation tips" in Section-by-Section breakdown
Try f

ilter test hg ypotheses

Compare across multiple views for validation

Share visualization

Share visualization