It's not just that forms need to resize. Mobile phones are entirely different computing environments, and VB never had a good answer for that. A mobile phone ha

It's not just that forms need to resize. Mobile phones are entirely different computing environments, and VB never had a good answer for that. A mobile phone has different UI paradigms altogether, you cannot just resize a desktop app to a phone resolution and call it a day. You cannot be as precise with a thumb as you can with a mouse. You also do not have a keyboard, so anytime a user attempts to type into an input, a virtual keyboard will usually occupy almost 30-40% of the vertical space your app previously had. As a result it's much more difficult to even get a keypress from a mobile user, so you have to resort to alternative gestures and UI buttons to make up for this lack. This limits you to mostly lists and cards on mobile screens. You'll also be forced to reimplement or import a UI library that attempts to mimic things like app bars and navigation buttons that users expect from native mobile apps, as the web was never designed with these paradigms in mind. Native app ecosystems benefit from the fact that they are a singular computing and OS target. Web apps have to work on everything. It's the same reason gaming consoles tend to have a wider variety of AAA games than PCs. It's easier to optimize for the PS5 or Switch and call it a day, than it is to port a game to work on 6 year old video cards and get it to work on Mac (both ARM based and x86 based), Windows, and Linux. A web dev has to inherently target thousands of different devices, dozens of different operating systems, 3 or 4 browsers, and dozens of screen resolutions, and cannot make any assumptions about what type of input devices are available. Oh, and they also have to assume an async programming environment with intermittent connectivity, and possible throttled connections as low as 100-200 kbps, so try to keep the bundle size under 100KB to keep time to first paint under 1s, mmkay? Even Windows 95 apps could assume a few dozen MBs loaded in via disc, and count on cached assets being available on disk.