Status

The current scope, expectations, and stage of Proto UI

Proto UI is currently in its pre-release stage (v0).

At this stage, the priority is not to expand surface-level features as quickly as possible, but to first clarify the core semantics between prototypes, adapters, and runtimes, and to verify whether this system can be translated and implemented consistently across different hosts.

Proto UI is currently focused on the following areas:

• Stabilizing the foundational way component prototypes are expressed
• Establishing clear translation relationships between prototypes, adapters, and hosts
• Verifying semantic consistency across different implementations through contract tests
• Expanding the foundational prototype library, adapter reference implementations, and documentation system

Proto UI already has a forming prototype authoring model, and its translation and implementation paths are being continuously validated across multiple Web runtimes.

At this stage, Proto UI is better understood as:

• a component interaction protocol that is still being stabilized
• an early-stage open-source project centered around prototypes and adapters
• a foundational system that emphasizes semantic consistency and verifiability

At the v0 stage, Proto UI should not yet be understood as:

• a fully complete production-grade UI framework
• a ready-made solution with a mature ecosystem and a rich component library.
• a general platform that is already well prepared for all hosts

If your goal is to adopt a mature, stable, and ready-to-use complete solution immediately, Proto UI is most likely not yet suitable for that role.

At the current stage, many parts of Proto UI are still subject to change, including but not limited to:

• the naming, organization, and detailed shape of some APIs
• the coverage and best practices of the adapter ecosystem
• the size of the prototype library and the completeness of its examples
• the documentation structure for both users and contributors

This does not mean Proto UI lacks direction. It means the project is still in the stage of consolidating its foundational capabilities.

At its current stage, Proto UI is more suitable for readers and contributors who are:

• interested in component abstraction, interaction protocols, or adapter-layer design
• willing to help build early prototype libraries, adapters, or documentation
• comfortable participating while semantics, constraints, and implementation boundaries are still being refined