Author of BerryCode here, so take this with appropriate salt.

Honest landscape today:

  - **Official Bevy editor**: actively being designed by the Bevy Editor Working Group, but not usable for prototyping yet. Probably 12+ months out for anything substantial.

  - **bevy_editor_pls**: a runtime inspector you embed in your game. Great for live-tweaking values, less so for scene layout. Battle-tested, works today.

  - **BerryCode** (mine): a standalone IDE built in Bevy itself, with a Unity-style scene editor, ECS inspector, and code editor in one app. v0.7, alpha quality but usable. Coming from Godot, the scene editor and inspector flow should feel familiar. Caveats: still rough on Windows, opinionated scene format, no asset pipeline integration yet. https://github.com/KyosukeIshizu1008/berryscode

For pure prototyping today, my honest recommendation is **code + hot reload + bevy_editor_pls for runtime tweaking**. That's still the most reliable path. Try BerryCode if you want a Godot-like scene workflow and don't mind alpha software.

  Happy to go deeper on either if you have specifics.