I'm not sure I agree it's a good idea at this stage in Bevy's lifetime to dedicate significant effort away from the core project to showcases.
I agree it would be ideal if such projects existed, but at this point it probably makes more sense for development to be focused on fundamentals like their upcoming editor.
Close collaboration with the users of the library can provide the same benefits. Without taking core developers away work working on the core. There seems to be dozens of games in development using Bevy, so that is a good sign!
Bevy is a community-driven engine, and there are hundreds of hobbists making small games with it already, providing tons of feedbacks and often even pull requests.
The kind of feedback they lack at the moment is more feedback from professional shops especially big ones, but it's not the kind of things they can dogfood anyway.
Comments
I'm not sure I agree it's a good idea at this stage in Bevy's lifetime to dedicate significant effort away from the core project to showcases.
I agree it would be ideal if such projects existed, but at this point it probably makes more sense for development to be focused on fundamentals like their upcoming editor.
On the contrary, dogfooding early would allow you to more easily spot design flaws and steer the project in the right direction accordingly.
Close collaboration with the users of the library can provide the same benefits. Without taking core developers away work working on the core. There seems to be dozens of games in development using Bevy, so that is a good sign!
How do they know if they are building the right thing?
Bevy is a community-driven engine, and there are hundreds of hobbists making small games with it already, providing tons of feedbacks and often even pull requests.
The kind of feedback they lack at the moment is more feedback from professional shops especially big ones, but it's not the kind of things they can dogfood anyway.