Thatโs theoretically true, but in practice, the desktop experience (screen size, interaction model, etc.) is sufficiently different that adapting it to mobile to get an app-like experience is not that different from building a separate app.
Itโs not at all like building a separate app. All the back-end code is identical - all you have to do is make the mobile version not take up as much screen-space, and thatโs not much work. e.g. on desktop I use icon and text, but on mobile icon only.
Then why do you think most business are already writing a separate Android app rather than just optimising their mobile website?
But โmake the mobile version not take up as much screen-spaceโ is not as simple as simply zooming out and just hiding some icon labels. And just the fact that people interact by touch rather than with a mouse and keyboard is already a major adjustment.
Anyway, Iโll leave it at this, since I feel like thereโs not much to gain here for me from the discussion anymore :) Cheers!
why do you think most business are already writing a separate Android app
I donโt think that. I know some businesses who are still writing separate apps, instead of switching to cross-platform. Youโll have to ask them why theyโre doing that. It frustrates me no end when platform-specific bugs come up because theyโre running different code on each platform, each written by different people.
the fact that people interact by touch rather than with a mouse and keyboard
โฆmakes no difference at all. Whether a user has touched a button, clicked on it, or tabbed to it and pressed enter, the same Button.Clicked event gets triggered.