Placing bones on a GTFL/GLB model in Animate 3D with Promenad
As you can see, we’ve been steadily advancing Animate 3D with Promenad, and what excites us most isn’t just the feature set, but what it represents.
We believe the future of modern game development belongs to teams who can prototype quickly, test ideas immediately, and deploy without friction. The old workflow of exporting files, reimporting assets, rebuilding projects, and waiting for results creates hesitation. Hesitation slows creativity. We’re designing against that.
Just like Build 3D with Promenad, it isn’t a disconnected editor. It’s part of the larger Promenad ecosystem. When we edit an in-game object in the browser, that object isn’t trapped in a local file. It lives in a structured environment and is delivered through APIs. When we adjust a bone hierarchy or tweak an animation curve, those changes can flow directly into the game consuming the asset. That means iteration becomes immediate.
For us, rapid iteration is not a luxury — it’s survival. In game development, bugs surface constantly. A joint bends incorrectly. A weight pulls too far. A prop sits slightly off-axis. If resolving that issue requires a heavy export pipeline, momentum dies. If it can be corrected live, tested instantly, and pushed forward, momentum builds.
Editing bone behavior on a GTFL/GLB model in Animate 3D with Promenad
That’s the environment we’re creating.
We’ve also made a deliberate choice to design Animate 3D as mobile-first. It forces clarity in interaction. If you can place bones, adjust hierarchies, scrub timelines, and key transforms on a phone without frustration, the system is truly intuitive. Desktop becomes expansive rather than necessary. The constraint sharpens the tool.
One of the areas we’re especially proud of is the language framework we’re developing around rigging. Instead of thinking purely in terms of raw vertex weights, we’re introducing semantic zones — structured regions of a mesh that describe intent. This opens the door for AI-assisted rigging that feels collaborative rather than opaque. AI can recommend pivot points or snapping suggestions within defined zones, but the developer remains in control. You can override, refine, and manually snap vertices to bones just as easily — even on a mobile device.
That blend of automation and precision is important to us. AI should accelerate, not obscure.
Because everything is structured within Promenad, animations themselves become first-class data. Duration, FPS, keyframes, transforms — they aren’t locked in a binary blob. They’re part of a system that can be versioned, inspected, and delivered dynamically. This aligns with a broader philosophy we’ve been building toward: games, like websites, should be outputs of well-designed systems.
We’re not chasing novelty. We’re chasing velocity.
Testing animations on a GTFL/GLB model in Animate 3D with Promenad
When game developers can rapidly prototype, deploy ideas into a live environment, identify issues, and resolve them without friction, creativity compounds. The faster feedback loop produces better mechanics, cleaner assets, and more confident experimentation.
Animate 3D is still evolving, but each iteration reinforces what we believe: modern game development isn’t about bigger tools. It’s about tighter loops.
And we’re getting there.