I didn’t say there’s no toooling, it’s just that these tools work great and are mostly transparent. There’s no part where you setup or manage the tool. Even the

I didn’t say there’s no toooling, it’s just that these tools work great and are mostly transparent. There’s no part where you setup or manage the tool. Even the deployment is just a few clicks. The overhead is so low compared to the web tech, it’s no comparison. If you want to do something weird you can complicate things if you like but the defaults are great so most of the time you don’t have to. You know how on web tech there's many tools like packers, linters etc? Those are all tools you need only because you want to pretend that JS is not JS and you end up putting a distance between yourself and the actual thing that runs so you loose your ability to understand what's actually going on because it's actually not your code that's running in the browser and you had to do the chores to achieve it. On native development these things also exists(the CPU doesn't understand human readable code, right? However the abstraction layers are straightforward), the packer equivalent would be linker I guess(not exactly but...) but you don't have to even know about that unless you are doing something that explicitly requires you to control how modules need to be connected. These tools are mature and simple, they daisy chain, you don't go through huge configuration files and its usually just a flag you add when you want to do something non-default(which you wouldn't if you are doing something like building UI). For huge projects things can get quite complex but the complexity isn't the default, unlike React & similar.