- This topic has 8 replies, 6 voices, and was last updated 1 week, 4 days ago by
.
-
Hi,
We have no traditional roadmap, because we consider it too old school
. There are hundreds of small and big tasks in our TODO list (kanban), but the priority of their implementation is very uncertain and subject to constant change.For the upcoming months the team is busy with major refactoring of the software and documentation. We’re about to make Verge3D more robust and reliable for professional users. I can’t say more for now but Yuri will provide more details in the press release for the first 4.11 preview (expected in a few weeks).
I appreciate the update, but I have mixed feelings about the “no roadmap” approach. I completely understand the need for flexibility — priorities can shift quickly with bug fixes, refactors, or new tech changes, and you don’t want to get locked into promises that become unrealistic.
That said, many tools in the 3D and dev space (like Blender, Godot, and even Three.js) share at least a high-level roadmap with their communities. These usually outline major features, long-term goals, or release cycles, even if smaller tasks remain fluid.
There are a few big advantages to this:
Transparency & trust: Users can see the direction the tool is headed and plan their own projects accordingly.
Community engagement: Public roadmaps often spark feedback, suggestions, or even contributions from the community.
Professional confidence: For studios and businesses, knowing what’s coming helps justify investing time and money into the platform.
I think a middle ground would work well for Verge3D:
A high-level public roadmap for major features or milestones (e.g., WebGPU, physics upgrades, AR/VR improvements).
Detailed changelogs and previews for smaller updates as they happen.
Maybe even community polls to see which features people value most.
This way the team keeps its flexibility but also gives the community a clearer sense of where things are headed.
I look forward to the 4.11 preview
Adam's Verge3D Tools:
GitHub
- You must be logged in to reply to this topic.