Roadmap

Messagevisor's roadmap prioritizes portable authoring and runtime contracts before adding convenience layers that could make translation data lossy or platform-specific.

Translation interchange#

Native XLIFF exchange is planned, with XLIFF 2.0 as the primary model and XLIFF 1.2 treated as a compatibility mode. The design must round-trip message and override identities, ICU and rich-text inline content, notes, translation workflow state, inheritance intent, and obsolete units. Until then, projects can build vendor-specific adapters through CLI plugins.

Application usage analysis#

A future source extractor will compare application call sites with authored message keys. Its goal is to report literal calls to undefined keys, likely orphaned definitions, and dynamic calls that require review across supported languages and wrapper APIs. Today, use generated TypeScript keys, list --messages --json, code search, and runtime deprecation diagnostics together.

Review automation#

npx messagevisor diff provides the foundation for PR copy review in terminal, Markdown, and JSON form. A future GitHub workflow can use its structured output to publish before/after copy summaries and Catalog artifacts without duplicating comparison logic.

Runtime performance#

Formatter caches are SDK-owned and shared by spawned children. Bounded cache policies and canonical cache keys remain an internal performance project: they will be benchmarked before adoption and will not become caller-managed API.