| I think the easiest way to explain this is: "It's a frontend in JS with a rendering engine in Dart/Flutter." So in goes JS/TS code, writing the familiar frameworks you know, and what does the interpretation/rendering of that code is Flutter and Dart. This is similar to how React Native works. It consumes a dialect of React and HTML-esque elements, and the renderer turns them into native UI widgets. --- As far as "Why would I use this?" If you think that Flutter is a better platform for cross-device UI development than React Native or NativeScript, but you don't actually want to write Flutter/Dart itself. (IE you want to stay in JS-land). Or you want to build the rest of your codebase in Flutter and Dart code/use it's FFI and interop facilities. Those are a few reasons I can think of. It's good to have a choice like this available IMO, I won't complain of it. |