You are reading a single comment by @allObjects and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@allObjects
@Blynk, my point was not mobile or desktop - yes, balance has already tipped towards mobile, but how is 'mobile' defined...
My point is native versus Web.
Native means: application platform is the device OS and version and applications are device OS and version specifically written and have to be downloaded and installed.
Web means: application platform is the universal browser and applications are written only once and run in the browser. 'Download' is transparent - dynamically and on demand, and when device storage gets tight, user has not to chose between which apps to keep and which ones to toss.
The comment about Mobile Web sucks on Desktop, is correct when UX design failed and no responsive framework is used. Building a real responsive and RESS - responsive with server side components - framwork and - really real estate oriented - UI versions can be done but turns out expensive and increases development complexity, especially with maximum reuse in mind. For example, each page has a device dependent table of contents / reference list what component and which implementation of this component to include and which ones not to include, and components are different only when real estate matters... said so: widgets with more elements have to be broken down or have to have multipe versions, models' values are populated in increments as user goes from initial/superficial to depth, and controller has to strike a compromise. As imaginable, this get's pretty complex and may not by all what is expected, and becomes also partially meaningless because bandwidth and plans grow (with same user costs). Higher develoment costs - because of elaborate implementations - are justified only when ultimate performance is required.
A mobile first UI approach on top of a framework good framework - that is actually/literally responsive and takes care of the hamburger and steakes - delivers good results. A framework with just CSS does not cut it, nor an application UI that uses only CSS with media query to hide and show things according to available real estate.
The application UI has to be responsive as well and load only the things that actuall - can be shown right away on the device (first fit, fit above the break). A hiding or reflow to endless (vertical) scrollable pages yield not a pleasant UI. On the other hand, for users swtiching between devices with small and large real estate, UI layout and flow have to stay 'structurally familiar', otherwise the user gets lost. In other words, a lot of fine line walking and compromises are required.
Btw, a 12" tablet, is it a mobile or a desk/lap top? And what about all the hybrids with flippable screens? ...with touch, mouse, or both?
After all, it is real estate, that makes the decision... because the human eye sight resolution is a given ...and looses out with age :(