Architectural decision
Native clients share contracts, not UI
Device interfaces differ while canonical work remains shared.
Before · Conflated concepts
Web ClientiOS ClientDesktop ClientMCP Client
After · Explicit boundaries
Relationships
- Desktop Client hosts the experience of Web Client
Problem and decision
Reimplementing server rules in each client creates divergent authority.
Share identity and server contracts while implementing native interaction separately.
Alternatives considered
- Require identical UI on every platform
- Implement a separate native backend
Tradeoffs and consequences
Incremental migration and uneven feature coverage need honest documentation.
A native screen uses the same domain truth without promising parity.
Related architecture
Related workflows
Current architectural direction; this record does not establish production release.