Custom Renderers

[brainkim]

Starting with 0.7, the CustomRenderer API has stabilized (see RenderAdapter API). I’m optimistic that I can get a Pixi.js/Three.js renderer out of the door in about a week or so, thanks to some spiking by Claude Code. I’m also investigating terminal-kit for a terminal-kit Renderer, and potentially reviving the Crank-NativeScript renderer written by @shirakaba, which uses an old, old adapter interface.

• Pixi.js
• Three.js
• Terminal (using terminal-kit?)
• Test Renderer which produces virtual Elements?
• NativeScript (Crank Native [and other custom Crank renderers] #11)

[shirakaba]

Very cool! I think sadly I don't have enough time these days to develop/support Crank NativeScript to a point where one would actually want to use it, as beyond just the renderer, there's the build system, plugins API, ecosystem, etc.

A custom renderer API would certainly clean up some code, but I'm already burnt out on supporting React NativeScript as it is 😅 but very happy to see it exist! Was actually talking about Crank and Crank Native just last week.

[brainkim]

@shirakaba No pressure haha. I’m on it. I’ve been experiencing a personal renaissance with Claude Code, and have been really excited to use Crank for a Pixi.js game idea I had. No pressure, and when I get to NativeScript I’ll keep you informed!

beyond just the renderer, there's the build system, plugins API, ecosystem, etc.

Yes I imagine mobile development is very complicated.

Thanks for mentioning Crank!