3 ms·
> For an HTML5 desktop app to become a good HTML5 mobile app usually the changes are so big that you end anyway with a different set of code generating the outp
by maratd 14y ago
> For an HTML5 desktop app to become a good HTML5 mobile app usually the changes are so big that you end anyway with a different set of code generating the output for the two "sides".
I'm actually working on this right now.
HTML and CSS served to both desktop and mobile are identical. HTML is just headers and an empty body tag. CSS has shared code and @media specific to each interface.
Every visual element is built through JavaScript/DOM.
Javascript is split into two sections/folders. Logic and visual. Mobile and Desktop share the logic javascript, but not the visual.
Everything you can do on the desktop, you can do on mobile. The only differences are in how the visual elements are presented.
- wvenable 14y agoThat, however, is not taking a large pre-existing desktop site and converting it to mobile.
- nl 14y agoI'm actually working on this right now. Having been down this path before, I predict you will find that the "last 10%" of those small, annoying things that don't quite work like native mobile apps in HTML5 will take the same amount of time to fix as developing the rest of the app. If you don't think this is the case then either you aren't far enough along to hit the problems or your app doesn't make heavy use of hardware (which - given that it is also a desktop app - it sounds like it probably doesn't). In the second case then using HTML5 makes good sense.
- maratd 14y ago> your app doesn't make heavy use of hardware Bingo. Would be surprised if it lagged on hardware from 10 years ago.
- rimantas 14y ago> The only differences are in how the visual elements are > presented. If you don't care about performance, then yes. Everything that affect desktop web performance for the worse (number of requests, latency, lame caching policy) will bite you hundred times more on mobile.