The average smartphone user downloads only 2.5 new apps a month. Of these, only 26% are used 11 times or more and 26% are only opened once.
Luke recommends “gradual engagement”
Gradual engagement is the process of moving a user through an application or service – actually engaging with it, and seeing its benefits. With gradual engagement, new users are not just presented with a registration form and then dropped off a cliff. Instead, registration is either postponed, or handled behind the scenes and the first time experience is focused on giving people an understanding of how they can use a service and why they should care to.
In his Faster Mobile Anyone? presentation at Breaking Development in Nashville, Steve Souders discussed the importance of performance on the Web, why it is even more important on mobile, and a set of emerging best practices for faster mobile Web site.
Techniques for Faster Mobile Experiences
Top techniques for mobile performance: make fewer http requests, reduce DNS lookups, avoid redirects.
Redirects globally take about 500ms. When using them to switch between mobile and desktop pages, people will see a blank page until the redirect takes effect. On mobile redirects are more painful.
Be careful of sharding dominant domains on mobile as there’s a maximum number of connections that can be open at any time.
Images are 50-60% of byte size. You can resize images based on screen size in the client or use a server side solution to adjust the image you send over.
Reduce http requests: use sprites, data URIs, CSS3
Google Search uses 68 inline images by marking them up with data:URIs in their mobile experience.
50% of unique users come in with an empty cache. Once during the day, half your users are coming in with an empty cache. Caches are small and don’t work as well as they should.
Internet Explorer will be giving scripts priority in the cache over images in IE 10.
Caches are much smaller on mobile and in some places (iPhone) non-existant.
App cache is for offline apps but because of existing browser cache issues, you might still want to use app cache to boost performance of online apps as well. Any HTML document that uses a manifest file is by default put into the app cache. If anything you list in your manifest hits a 404, then nothing is cached.
App cache reload: once you rev a manifest and reload a web page, you’ll still see older content pulled from the app cache. If you reload again, you’ll see the update (from the cache).
App cache has good intentions but it is really hard to work with. We need a framework for making things more manageable.
More opportunities include: localStorage, audio & video tags, WebSockets, onTouchEnd instead of onClickHistory, a ping request, AnimationFrame – not timersn native JSON parse/stringify
Key takeaways. Speed matters. There is a lot of opportunity for performance on mobile as people know it is an issue.
Could you do a blurb 4/4 for where he finds out your dad left you when you were very young? :)
i think they’d all react pretty much the same like they’d be so buffled like they’d wonder why the fuck someone would leave such an amazing girl and his family behind and just ditch them and if you told him that your dad left he’d probably hug you and tell you how much of a douche your dad was
The mobile era of computing is here. Global shipments of smartphones surpassed global shipments of desktop and laptop computers combined at the end of 2010 —two years earlier than predicted. So designing and developing Web sites today means testing on mobile devices. But with hundreds of mobile devices to choose from… what needs to be in your testing arsenal and why?
Thankfully several mobile aficionados on Bagcheck have taken the time to catalog their devices and give us a glimpse into the mobiles they design and develop for.
if you were dating luke he would probably always record himself singing his new favourite love song, hemmo1996 style, and send it to you because he wants to make sure you know how much he loves you even though he cant be there for you
Luke Wroblewski presents how-to tutorials for user experience
I dag har jeg igjen lært at Luke W er en kul dude. Sjekk ut kanalen han har laget sammen med Intel. Luke har predikert innholdet i flere år, men det er herlig å få en rask refresh via video – om du ikke har fått dette med deg er det virkelig påtide.
Notes from LukeW: “In his There Is No Mobile Web presentation at Breaking Development in Nashville TN, Jeremy Keith outlined why Web designers and developers need to embrace the flexibility inherent in the Web especially in today’s multi-device world.”
LukeW Ideation + Design provides resources for mobile and Web product design and strategy including presentations, workshops, articles, books and more on usability, interaction design and visual design.
okay but this looks like michael and luke are members of the same football team and tragically during one of the games luke got hurt really bad and was in the hospital and they weren’t sure if he was going to make it or be able to ever walk again and now he’s seeing michael for the first time in 4 months because he was finally released and miCHAEL IS SO HAPPY THAT HE’S OKAY
In his presentation at An Event Apart in Atlanta, GA 2011 Jared Spool detailed the importance and role of links on Web pages. Here are my notes from his The Secret Lives of Links
It’s easy to know when your website scent is bad. Use of the back button, pogo-sticking, and using search are all signs that the scent of your links is off.
Usage patterns are the same across all websites. In 15 years (and thousands of sites) things have not changed much. Only 42% find what they are looking for. 58% do not find what they are looking for. For these people the scent is not coming through.
Tons of other great stats. Luke Wroblewski aka LukeW takes great notes ;)