One application platform. Across operating systems.
The developer platform
Build an application once and distribute one package to compatible Windows, Linux, macOS, Android, iOS and browser hosts. This is the platform goal; current releases support different contract profiles.
Application behavior can run without ambient access to the operating system.
A host can render semantic intent without packaging a rendering engine with the application.
Offline state can belong to the host and survive replacement of application logic.
How the platform fits together
SDK and CLI: author, validate, run, sign and release your application.
The MZI contract: portable behavior, semantic interface, data and capabilities.
MZI Host: platform presentation, execution, safe local storage and approved system access.
mzi.app: documentation, specification, reference packages, host downloads and compatibility evidence.
Next platform milestones
Release criteria, followed by reference implementations. Evidence for an example is separate from readiness for arbitrary applications.
- NextGeneral application APIsrelease criterion
Two independent applications define their own records and actions without changes to the host. Domain behavior belongs to the application.
- NextCross-host conformancerelease criterion
The same fixtures verify state, Unicode, numbers, errors and lifecycle on supported host profiles.
- NextApplication lifecyclerelease criterion
Updates, schema migrations, export and recovery preserve user data across verified compatible releases.
- NextIndependent developer workflowrelease criterion
A developer builds, distributes and updates a real application using the documentation, SDK and CLI without editing MZI Host.
- EvidenceApplication 0.2reference evidence
One package provides a form, dynamic records and persistent offline behavior in two hosts.
- EvidenceSigned package identityreference evidence
Deterministic archives carry a canonical Ed25519 publisher signature verified by independent hosts.
- EvidenceComponent host runtimereference evidence
A real WebAssembly component invokes the embedded versioned WIT contract through Jco, Wasmtime, Chicory and WasmKit.
- EvidenceNative Windows hostreference evidence
The exact Field Notes package runs through an independent native Windows host.
- EvidenceState migrationreference evidence
Host-owned records survive a compatible schema and application logic upgrade.
- EvidenceLinux hostpreview evidence
Self-contained x64 and ARM64 GTK4 AppImages run offline and replace validated development revisions in process.
- EvidencemacOS hostpreview evidence
A native AppKit ARM64 bundle opens the same package from Finder and negotiates in-process development reload.
- EvidenceAndroid hostpreview evidence
Native Compose executes the signed MZI Application 0.3 Component, owns offline state and uses no WebView or JNI runtime.
- EvidenceiOS hostpreview evidence
Native SwiftUI executes the same Component in Simulator, while CI also verifies an unsigned iPhoneOS ARM64 build.
- FutureApp Store policy proofplanned
A constrained catalog and distribution model must survive physical-device signing and Apple review.
- FutureAccessible adaptive interfaceplanned
Navigation, validation and async work map to keyboard, pointer, touch and assistive technology.
Open questions
Semantic ceiling — how much UI meaning can be portable before the protocol becomes another framework?
Publisher trust — how should registries handle verification, revocation, rotation and lost keys without centralizing MZI?
State evolution — how should hosts coordinate destructive migrations, encrypted sync and multi-device conflicts?
Distribution — where can universal packages coexist with platform review and execution restrictions?