/plans/ui-pose-detection-rebuild.md

Human Pose Detection UI Component Rebuild Plan

Overview

Rebuild the Live Demo section's Human Pose Detection UI component with enhanced WebSocket integration, robust error handling, comprehensive debugging, and extensible architecture.

Current State Analysis

• Backend is running on port 8000 and actively broadcasting pose data to ws://localhost:8000/ws/pose-stream/zone_1
• Existing UI components: LiveDemoTab.js, pose.service.js, websocket.service.js
• Backend shows "0 clients" connected, indicating UI connection issues
• Need better error handling, debugging, and connection management

Requirements

1. WebSocket Integration: Connect to ws://localhost:8000/ws/pose-stream/zone_1
2. Console Debugging: Comprehensive logging for connection status, data reception, rendering
3. Robust Error Handling: Fallback mechanisms and retry logic for connection failures
4. Extensible Architecture: Modular and configurable for different zones and settings
5. Visual Feedback: Connection status, data flow indicators, pose visualization
6. Settings Panel: Controls for debugging, connection management, visualization options

Implementation Plan

Phase 1: Enhanced WebSocket Service

• File: ui/services/websocket.service.js
• Enhancements:
  • Automatic reconnection with exponential backoff
  • Connection state management
  • Comprehensive logging
  • Heartbeat/ping mechanism
  • Error categorization and handling

Phase 2: Improved Pose Service

• File: ui/services/pose.service.js
• Enhancements:
  • Better error handling and recovery
  • Connection status tracking
  • Data validation and sanitization
  • Performance metrics tracking

Phase 3: Enhanced Pose Renderer

• File: ui/utils/pose-renderer.js
• Features:
  • Modular pose rendering system
  • Multiple visualization modes
  • Performance optimizations
  • Debug overlays

Phase 4: New Pose Detection Canvas Component

• File: ui/components/PoseDetectionCanvas.js
• Features:
  • Dedicated canvas management
  • Real-time pose visualization
  • Connection status indicators
  • Performance metrics display

Phase 5: Rebuilt Live Demo Tab

• File: ui/components/LiveDemoTab.js
• Enhancements:
  • Settings panel integration
  • Better state management
  • Enhanced error handling
  • Debug controls

Phase 6: Settings Panel Component

• File: ui/components/SettingsPanel.js
• Features:
  • Connection management controls
  • Debug options
  • Visualization settings
  • Performance monitoring

Technical Specifications

WebSocket Connection

• URL: ws://localhost:8000/ws/pose-stream/zone_1
• Protocol: JSON message format
• Reconnection: Exponential backoff (1s, 2s, 4s, 8s, max 30s)
• Heartbeat: Every 30 seconds
• Timeout: 10 seconds for initial connection

Data Flow

1. WebSocket connects to backend
2. Backend sends pose data messages
3. Pose service processes and validates data
4. Canvas component renders poses
5. Settings panel shows connection status

Error Handling

• Connection Errors: Automatic retry with backoff
• Data Errors: Validation and fallback to previous data
• Rendering Errors: Graceful degradation
• User Feedback: Clear status messages and indicators

Debugging Features

• Console logging with categorized levels
• Connection state visualization
• Data flow indicators
• Performance metrics
• Error reporting

Configuration Options

• Zone selection
• Confidence thresholds
• Visualization modes
• Debug levels
• Connection parameters

File Structure

ui/
├── components/
│   ├── LiveDemoTab.js (enhanced)
│   ├── PoseDetectionCanvas.js (new)
│   └── SettingsPanel.js (new)
├── services/
│   ├── websocket.service.js (enhanced)
│   └── pose.service.js (enhanced)
└── utils/
    └── pose-renderer.js (new)

Success Criteria

1. ✅ WebSocket successfully connects to backend
2. ✅ Real-time pose data reception and visualization
3. ✅ Robust error handling with automatic recovery
4. ✅ Comprehensive debugging and logging
5. ✅ User-friendly settings and controls
6. ✅ Extensible architecture for future enhancements

Implementation Timeline

• Phase 1-2: Enhanced services (30 minutes)
• Phase 3-4: Rendering and canvas components (45 minutes)
• Phase 5-6: UI components and integration (30 minutes)
• Testing: End-to-end testing and debugging (15 minutes)

Dependencies

• Existing backend WebSocket endpoint
• Canvas API for pose visualization
• ES6 modules for component architecture