Roadmap to v1.0.0

[Flux159]

Roadmap

Creating a tracking issue to track the roadmap for a v1.0.0 release of Mystral Native. The source of truth for the roadmap is ROADMAP.md in the repo itself, but this is a github issue for users and developers to see the high level goals of the project.

v1.0.0

• Ensure that Three.js and Babylon.js can work with WebGPU renderer.
• Ensure that Pixi.js can work with WebGPU renderer (Pixi 8).
• Open source Mystral.js (the JS engine that MystralNative was specifically built for & the sponza example already uses).
• Ensure that iOS and Android builds are well documented & tested (with exact runtime specifics as well - ie JSC on iOS, etc.). Scripts for getting started with a new project on iOS / Android. Example code for how to integrate into existing apps.
• Setup GPU CI infrastructure to automate testing in CI / CD (beyond just build succeeds) and perform regression testing.

v2.0.0

• Add WebGL support via ANGLE to enable compatibility with WebGL games and frameworks
• Explore Hermes / Static Hermes as an additional JS runtime for iOS / Android.

v3.0.0

• Enable AOT compilation of a strict subset of Typescript to C++ to native code, eliminating the need for a JS runtime on restricted platforms. (Experimental).

[Flux159]

Three.js now has a working spinning cube example in v0.1.0! It's just the basics, but it should work - checkout https://github.com/mystralengine/mystralnative/blob/main/examples/threejs-cube-src.js for a reference (also note the build steps in the comments at the top of that file).

Next up will be Pixi 8 with the WebGPU renderer & fixing up other Three.js features (right now three.js has only been tested with some of the bascis, need to validate that more complex examples also work).

[robertpanvip]

Is there a plan to add CLI options at build time, for example to compile only Canvas2D, or WebGPU, or to choose which JavaScript engine to use?

[Flux159]

@robertpanvip These would be cmake options - there's some documentation on this: https://github.com/mystralengine/mystralnative?tab=readme-ov-file#build-options ; but I think adding it to the full docs would be helpful. I think we already have which WebGPU runtime to use and which JS engine to use, but right now nothing around Canvas2d since Skia is always included. It's probably a good idea, just needs extensive testing for a lot of different configurations (the matrix of things to test & what works/doesn't work for each config is already quite large - just building successfully doesn't guarantee that things work at runtime).

[wanton7]

There is TypeScriptToLua project that allows transpiling TypeScript into Lua. https://typescripttolua.github.io

ts-defold seems to be using it. This might allow you to drop V8 and use Lua runtime instead.