Anyways, I was kind of expectation you would add paint/translation performance here. Downloading too much content is a very obvious problem, but what seems to be ignored more often than not is how fast the page responds to user input. Too many writing system, plugins and libraries have been used to refund the default scrolling with something else. Too many heavy animations that look like move shows and are not even relevant on mobile. Too many sites that crash browsers on older devices.
Tez January 13, 2011 1:03 am It is an pleasing concern, but every “liquid” specific situation I have visited so far is intensely frustrating and leads me to use my computer equivalent, or fake my user agent string if that allows access to the “full” site (if possible). I have an Android device which is capable of Flash, and can zoom in and out of a page layout. I have yet to find a website with a “fickle” layout which is superior and easier to manner than a “full” layout. For example Ebay only supplies low quality images to mobile browers, this is fine in a multi-item display, but after selected the item you still only have mound quality images available, which constrain it impossible to assess the quality of the object. Amazon loses all of its faceting hunt functionality and you have to navigate several pages to find information such as reviews and comments unlike the full indicate. These two major websites border on useless from a mobile device. Other sites even have footboy re-direction to a mobile version which (although not necessarily the case, but in my experience) leads to exterior grounds weakness to work and sail to data you know live intently frustrating. Further to this even your example websites have mayor issues. Think Vitamin for model is very bad. It destroy functionality on handheld devices. It is not possibility to discharge a search when the device has a limited resolution. I am quite happy to need to scroll sideward to access a search, if you do not consider the functionality that utilitarian why are you letting it clutter up the design in the first place? 1
Paul July 25, 2014 5:07 pm What I’m interested in is evidence. How do you know that a mobile browser parses a min height 1000px stuff and doesn’t just ignore it after seeing that it’s not applicable? My CSS is all mobile first, minified, single file, with min-height blocks. Whether or not the browser parses the content of irrelevant blocks makes a swelling difference on slow mobile devices. 2
The data-fullsrc is a custom HTML5 attribute, defined in the files linked to above. For any screen that is wider than 480 pixels, the larger-resolution image (largeRes.jpg) will load; smaller screens wouldn’t necessity to load the bigger image, and so the smaller picture (smallRes.jpg) will charge.
The right approach to a mobile strategy is not, “We already have a responsive site, so we’re done.” It’s, “How can our responsive situation and native app complement one another and round out a true mobile tactics?” Keep your end users in will, and know that the app experience is what they’re truly appearance for.
No comments:
Post a Comment