All those minutes reading your news feed in bed, messaging friends over lunch, and browsing photos on the bus really add up. Time spent on Facebook’s mobile site and apps per month (441 minutes) has finally surpassed usage of its classic website (391 minutes) — for Americans who use both Facebook interfaces according to the latest report from comScore. And that’s actually a big problem for the social network.

Foresight.js gives webpages the ability to tell if the user’s device is capable of viewing high-resolution images (such as the 3rd generation iPad) before the image has been requested from the server. Additionally, it judges if the user’s device currently has a fast enough network connection for high-resolution images. Depending on device display and network connectivity, foresight.js will request the appropriate image for the webpage.

Mozilla CEO Gary Kovacs wants programmers and device manufacturers to focus their efforts on creating HTML 5 based products rather than isolating the technology environment to specific mobile apps. Speaking at CTIA on Thursday Kovacs said users do not want to be shackled to an app ecosystem and will embrace freedom of choice.

When it comes to building interactive maps for desktop web, most of us are quite comfortable using APIs like Google Maps or Bing Maps. But when we need to port or build something for mobile, it often feels like we’re crumpling a clean sheet of paper into a paper ball. Certainly, dealing with a smaller screen size, slower processor, and less memory can feel like a frustrating step backwards. But if you consider that mobile devices have touch screens, cameras, microphones, accelerometers, wireless and GPS capabilities on top of being portable, mobile devices are in a way better place than desktop PCs. So if we take the time to understand their limitations and features, we can build lightweight applications that are more like origami — compact, elegant, and functional — instead of like a crumpled paper ball that you’re ready to throw in the trash can.

I felt bad for not doing anything on that completely real evening. It’s painful to see articles that praise ApplicationCache’s ease of use, written by people who’ve clearly only met him in passing. I must set the record straight: I’m here to tell you ApplicationCache is a douchebag.

I wasn't sure if I should create a new tag here for "douchebag"?

The experience of using a mobile website should naturally be different from a desktop experience – not just visual presentation, content should be prioritised and structured differently. The risk, though, is that you’ll wind up maintaining different versions. News flash: this will be a disaster. Duplicate content. Out-of-sync updates. Wasted effort.

Today, comScore released startling data about the mobile web, which bodes poorly for the browser. In March, the web browser accounted for just 18.5 percent of time spent online among US smartphone users. Mobile apps accounted for the rest. Now we know why Safari for iOS capabilities advance so sparingly: Apple sees it as irrelevant. Stated differently: Safari is to mobile what Internet Explorer 6 was to the desktop 10 years ago. Apps matter more to both developers.

Yaaaawn, here we go again.

Site speed is one of the most important things about creating web content, and web applications.

Touch interaction has become practically ubiquitous in developed markets, and that has changed users' expectations and the way UX practitioners think about human–computer interaction (HCI). Now, touch-free gestures and Natural Language Interaction (NLI) are bleeding into the computing mainstream the way touch did years ago. These will again disrupt UX, from the heuristics that guide us, to our design patterns and deliverables.

Many mobile apps could benefit from working without an Internet connection. Here, we take a look at how offline capabilities affect the decision of developing native apps vs. mobile web based apps.