Roadmap

The roadmap records direction, not a delivery guarantee. Items stay marked as planned until an executable contract and documentation exist.

Runtime

• Stabilize the public server and package APIs toward 1.0.
• Expand real-world compatibility fixtures and long-duration memory testing.
• Broaden supported distribution targets while retaining reproducible bundles.
• Deepen production guidance from deployed workloads.

Laravel

• Continue the maintained Laravel 12 and 13 executable matrix.
• Track upstream package constraints without bypassing them.
• Expand package-specific persistence and worker-isolation evidence.
• Preserve the one-request-per-worker safety rule until the framework contract supports stronger concurrency.

Native mobile

• Complete the application host around the implemented Swift/UIKit renderer.
• Establish iOS packaging, signing, device testing, and compatibility gates.
• Complete component, navigation, accessibility, and performance parity evidence.
• Grow the native plugin ecosystem with reviewed examples.

Mobile UI

• Move individual components through maturity and verification gates.
• Fill incomplete behavior and accessibility evidence.
• Keep the machine-readable parity contract aligned with documentation.
• Define cross-platform visual behavior when an iOS renderer exists.

Desktop

• Preserve stable API 1, worker protocol 6, and Rust plugin protocol 1.
• Expand Linux compositor, GPU, and distribution certification.
• Build and certify Windows packaging without weakening the capability model.
• Complete macOS packaging, signing, updates, and physical-device validation when Apple hardware is available.
• Grow the reviewed plugin ecosystem and signed-update deployment evidence.

Suggest or own an item

Start with Contributing. A useful proposal explains the current limitation, the smallest safe contract, how it will be tested, and which documentation will change.