# NuvioTV Screen Port vs Clean Rewrite — Quick Reference

## Two approaches for adding NuvioTV features to UNSPOOLED

### Option A: Clean Rewrite (preferred)
Write the screen from scratch using UNSPOOLED's design system and data layer.
Same functionality, zero NuvioTV coupling.
- **When**: architectural differences exist, UNSPOOLED data layer supports it
- **Effort**: ~2-3h per screen
- **Result**: Maintainable, UNSPOOLED-native code
- **Reference**: `references/nuvio-screen-clean-rewrite.md`

### Option C: Bridge/Port
Mechanically port NuvioTV screens, wrap with adapter ViewModels.
- **When**: screen is self-contained with few NuvioTV-internal deps
- **Effort**: Faster initially, permanent maintenance tax
- **Result**: Adapter layer = dual state models, harder debugging
- **Reference**: `references/nuvio-screen-port-pattern.md`

### Option B: Infrastructure Migration (avoid)
Import NuvioTV's entire backend alongside UNSPOOLED. Fragile, high maintenance.