> The few times in my career that I've ended up doing UI development, the code and complexity was in the presentation layer, not in events or model or business logic.
its true, though it doesn't necessarily have to be that way (view models (or even bff) if done properly)
speaking from experience, i think the big issue is how will your dev team be structured... will android/ios people be able to write idiomatic rust (or whatever language) or should that core be a completely separate team? now you cant just hire any dev, they need to understand how it's going to be used by multiple client languages specific to that cross-platform system
though this framework looks like its pre-baking the architecture which means it probably wont look idiomatic from the client-side, so now your hiring for ui needs to take that into account... and now you have multiple teams that need to communicate adding overhead.
using cross-platform sounds simple and easy in the beginning but its a big commitment with multiple facets
i'm not sure what the real answer is... my guess is "it depends: what are you actually trying to do?"
speaking from experience, i think the big issue is how will your dev team be structured... will android/ios people be able to write idiomatic rust (or whatever language) or should that core be a completely separate team? now you cant just hire any dev, they need to understand how it's going to be used by multiple client languages specific to that cross-platform system
though this framework looks like its pre-baking the architecture which means it probably wont look idiomatic from the client-side, so now your hiring for ui needs to take that into account... and now you have multiple teams that need to communicate adding overhead.
using cross-platform sounds simple and easy in the beginning but its a big commitment with multiple facets
i'm not sure what the real answer is... my guess is "it depends: what are you actually trying to do?"