For truly novel UIs with high dynamism it is probably a good decision. For anything else it is almost certainly more work for the dev and more resource-intensi

For truly novel UIs with high dynamism it is probably a good decision. For anything else it is almost certainly more work for the dev and more resource-intensive for the system. One thing I haven't seen anyone else mention is that a game engine is generally going to be re-rendering constantly, as part of the game/render loop. This is because in a game it is almost always the case that something is changing on screen at any given moment. In a more "normal" app UI, most things are static, so having a render loop operate like that doesn't make much sense. So instead things are optimized for the static case – if nothing is happening on screen, resources are not being used.