Lock-in ease. Most of the mobile frameworks attempt to lock you in to their platform. So they are specifically meant to be easy. This really is the Microsoft pl

Lock-in ease. Most of the mobile frameworks attempt to lock you in to their platform. So they are specifically meant to be easy. This really is the Microsoft playbook of old. You want resistance and choice to be minimized in this case, and lock into tools and platforms due to their ease. On the web all the libs/frameworks are really just faster ways to use web technology (HTTP/TCP/etc), where native apps have to tie into hardware and systems so you must use them so there can be only one. There are actually lots of ways to develop for mobile beyond these frameworks though. But even within these frameworks (Android, iOS) things are changed and swapped out at their will i.e. changing UIKit, Apple switching from Carbon to Cocoa, In-App Billing changing etc. So lock-in sometimes creates massive ripples of forced change. If you are making cross platform apps, like the web is cross platform, that is where things get more difficult. Complexity goes up, more solutions appear to solve and iterate on the problem. The web and web tech is the best solution we have for cross platform currently.