Platform Watchlist
Purpose
The watchlist tracks technologies that may change frontend architecture decisions. A watched item is not automatically recommended.
Watch states
| State | Meaning |
|---|---|
| Adopt | Mature enough for normal production use with standard review. |
| Adopt selectively | Useful in specific conditions with explicit constraints. |
| Pilot | Worth testing in controlled areas; not a default. |
| Watch | Track movement; do not build strategy around it yet. |
| Avoid for now | Risk or immaturity outweighs likely value for most teams. |
Current watchlist
| Topic | State | Review trigger |
|---|---|---|
| React Server Components | Adopt selectively | Framework support, caching model, and team debugging skill. |
| React Compiler | Pilot/adopt selectively | Official guidance, build compatibility, measurable render wins, and rollback confidence. |
| Server Functions and Actions | Adopt selectively | Auth, validation, idempotency, cache effects, and progressive-enhancement states are documented. |
| Local-first sync engines | Pilot/adopt selectively | Product requires offline/collaboration, conflict policy is explicit, and storage/sync failure modes are tested. |
| Partial hydration/islands | Adopt selectively | Route profile shows mostly static content with focused interactivity. |
| Resumability | Watch | Ecosystem maturity and hiring/debugging confidence. |
| Edge rendering | Adopt selectively | Clear latency or personalization benefit with observability. |
| WebGPU | Pilot | Product requires advanced visualization or compute. |
| View Transitions API | Adopt selectively | Progressive enhancement and reduced-motion path exist. |
| Passkeys/WebAuthn | Adopt selectively | Identity provider, recovery, and support flows are ready. |
| Privacy-preserving attribution APIs | Watch/pilot | Business needs attribution, browser support and reporting limits are understood, and privacy review approves the data flow. |
| MCP | Adopt carefully | Tool isolation, permissions, audit, and security review exist. |
| A2A | Watch/pilot | Real multi-agent delegation need exists. |
| GenUI component registries | Adopt for GenUI | Registry, schema validation, and design-system contracts exist. |
| GenUI eval platforms | Adopt carefully | Fixture ownership, release gates, redaction, trace review, and incident feedback loops exist. |
Review rule
Move an item between states only after checking current primary sources and real product constraints. Record why the state changed in the relevant chapter or future-radar entry.