This is super cool, but I wonder what the application might be.
I can imagine wanting to use it to pepper in 3D elements into an existing RN app, but surely embedding the entire Godot engine is kinda heavy?
Then I can imagine wanting to embed a larger 3D experience into an RN app... maybe a 3D product preview or something? I guess that could be cool. But still, the heft of embedding the Godot frameworks...
I am actually developing an app that has 3d elements, but if i were to use this the Godot experience might just feel too separate from the rest of the app. like 2 siphoned off apps in one. Something like react native three might be more appropriate for a lot of the use cases I can imagine. But I'm probably missing something
I would think, if anything, it would be for creating a UI for a Godot-native game (after a prototype stage where the UI is Godot-native programmer art); and being able to break off the responsibility for that component to a UI team that can simply hire React frontend devs to do the design and development, where those devs don’t need any knowledge of how Godot works. Architecturally, the game UI wraps and controls the game engine, because of course it does; but organizationally, the UI team would serve the needs of the game dev team, rather than the other way around.
I could see this being interesting in treating game elements as React components and using that level of abstraction.
E.g. imagine a Snapchat "lens" type experience (one screen with little fun mini game experiences) that the user can easily add or remove characters or entire chunks of the "game" (turn on/off raining objects the character can interact with, configure, etc).
Could also make it easier for LLMs to generate unique simple game experiences with these building block "components" vs having to build everything from scratch.
If the team's goal is to be able to write a cross-platform game, but also have a great UI toolkit, they could have just used Flutter. This is eating massive costs just to use HTML, CSS and JS.
This is super cool, but I wonder what the application might be.
I can imagine wanting to use it to pepper in 3D elements into an existing RN app, but surely embedding the entire Godot engine is kinda heavy?
Then I can imagine wanting to embed a larger 3D experience into an RN app... maybe a 3D product preview or something? I guess that could be cool. But still, the heft of embedding the Godot frameworks...
I am actually developing an app that has 3d elements, but if i were to use this the Godot experience might just feel too separate from the rest of the app. like 2 siphoned off apps in one. Something like react native three might be more appropriate for a lot of the use cases I can imagine. But I'm probably missing something
I would think, if anything, it would be for creating a UI for a Godot-native game (after a prototype stage where the UI is Godot-native programmer art); and being able to break off the responsibility for that component to a UI team that can simply hire React frontend devs to do the design and development, where those devs don’t need any knowledge of how Godot works. Architecturally, the game UI wraps and controls the game engine, because of course it does; but organizationally, the UI team would serve the needs of the game dev team, rather than the other way around.
I could see this being interesting in treating game elements as React components and using that level of abstraction.
E.g. imagine a Snapchat "lens" type experience (one screen with little fun mini game experiences) that the user can easily add or remove characters or entire chunks of the "game" (turn on/off raining objects the character can interact with, configure, etc).
Could also make it easier for LLMs to generate unique simple game experiences with these building block "components" vs having to build everything from scratch.
If the team's goal is to be able to write a cross-platform game, but also have a great UI toolkit, they could have just used Flutter. This is eating massive costs just to use HTML, CSS and JS.