Mobile vs Web — Feature Parity
Parity matrix (responsive-web on mobile vs desktop web)
| Feature | Desktop | Phone (375px) | Tablet (768px) |
|---|---|---|---|
| Dashboard | full multi-pane | single-pane stack | 2-column |
| Portfolio + chip stack | full | full | full |
| Signal inbox | full | full | full |
| Alerts management | full | full | full |
| Trading-Intel hub | full | single-pane | 2-column |
| TA chart at L1–L3 | ✅ | ✅ | ✅ |
| TA chart at L4–L5 | ✅ | locked (L2 max) | unlocked |
| Education hub | full | full | full |
| Pattern trainer | post-GA | post-GA | post-GA |
| Admin observability | ✅ | ❌ (admin-only, desktop UX) | ✅ |
| Multi-pane charts | ✅ | carousel | 2-pane |
| Bulk operations | ✅ | ❌ | partial |
What “L2 max on phone” means
The Complexity dial L1-L5 controls overlay density on charts. On phone viewports (<768px), L4-L5 produce a chart that’s visually unreadable. We auto-cap at L2 by default. To unlock L3-L5 anyway, go to Settings → Preferences → Mobile complexity override and accept the explicit “this will be unreadable” warning.
What’s the same
Backend, data, signals, plan tier. There’s no separate mobile data model — the same API powers both. Your alerts, watchlist, portfolio, and education progress sync across devices instantly.
When the native app ships (Phase 2)
The matrix shifts toward parity with new mobile-only features (push, home-screen widgets, biometric session lock). The responsive-web experience continues to work indefinitely; native is additive, not a replacement.