When will be Bevy Production Ready?

[rnp0728]

Is there any timeline for bevy engine to be production ready?

[NthTensor]

The short answer is: no.

The slightly longer answer is: it depends on your production requirements. I know for a fact that Bevy has been part of production projects since like v0.6. It has some great stuff and some faults. The degree to which using it in production is a good/bad idea really depends on what you need from it.

If you are asking about when the api will stabilize, it probably never will -- game engines don't really do that. But we are working towards a point where you will be able to stay on older versions for longer.

[Magnitus-]

So far, bevy has been pretty solid for me in terms of runtime stability (currently at 0.15.3). All the bugs I've encountered found so far where my own and not the engine.

It does feel very barebones in some ways. I don't have enough game dev experience to clamor for an editor or some of the other stuff more knowledgeable game devs ask for, but I do have enough web dev experience to feel like I was reinventing the wheel when I wrote my own GUI components (as educational as that was).

Other than that, documentation can be lacking in certain areas (for example, I felt like I was partly on my own to figure out how to persist and load a scene which you kind of need if you want to save or load your game... the feature is there, just not well documented).

And if you have more limited time to work on your project, the (sometimes major) breaking changes every ~3 months can be a killer, but if you give up on chasing the latest and greatest version of bevy and just upgrade when you switch projects (or if your current project is released and doing well), even that can be manageable. It is mostly a matter of switching priorities and focusing on what is really important: Getting your project done.

Only thing that would kill me at this point is having to upgrade because of a bug in bevy, but as it turns out, that doesn't seem to happen a whole lot. By the time they get to the next major release with breaking changes, they've usually done a couple of bug fix releases on the current release which I think probably helps.

[ekwoka]

Well, define "production ready".

In terms of a v1.0 it would be when you could expect most apis to be stable for safe upgrade, but if the features it has now are enough for your case, then it's production ready already.

The last versions had less breaking changes than Unreal 5.6 so....

[Magnitus-]

I'd say the main thing that is missing right now would be some kind stable version with someone that is paid to either directly address reported bug fixes in that stable version or at least accept and manage community PRs on that stable version (to maintain quality and backward compatibility).

Without that, if I find a problem in my 0.x.x version that is behind the last bleeding edge version, I have to dig into the internals of bevy myself to address the problem and should I successfully do so, there is probably zero chance that the fix will get merged into a stable branch in the upstream bevy repo, thus cutting any community potential to rally around a stable version in the bud. Everyone depending on a deprecated (but api stable) 0.x.x version is on their own to fix their problems. Furthermore, as there is no advertised stable version, the exact 0.x.x version that different people wanting a stable api will use is likely to differ quite a bit which would further discourage community efforts around a specific stable version.