- Design Patterns - Posted by ronan 7 weeks 5 days ago
Anatomy of a mobile web experience: google.com- In a recent blog post that I did here on mobiForge (Server-side device detection used by 82% of Alexa top 100 sites) some people expressed surprise that a 47 byte difference in the HTML payload delivered by Google to different devices constituted a significant level of server-side adaptation. On checking my results, it turned out that this minor 47 byte file size difference actually masks an entirely different HTML document served to
- Design Patterns - Posted by ronan 5 weeks 5 days ago
Anatomy of a mobile web experience: facebook.com- This is the second article in a series about how the major internet brands deliver their mobile web experience. The previous article is available here: Anatomy of a mobile web experience: google.com
- Design Patterns - Posted by ronan 1 year 34 weeks ago
- Mobile/Desktop Switching Code
- goMobi allows you to create a mobile site for your business. In order to make the best use of this mobile-friendly site we recommend that you add functionality to your existing desktop web site to automatically redirect mobile devices to the mobile site. This ensures the mobile users get the best experience even if they type in the address of the existing desktop site.
- Design Patterns - Posted by jonarne 3 years 24 weeks ago
One web 2.0 - social edition- I bet I am not the only one wondering what Nokia was going to announce yesterday... In addition to the N97, Nokia Messaging was the big news. Put short, Nokia Messaging is enabling a bunch of IM-like services on the phone. In my mind this is an important change in the traditional mind pattern device manufacturers, and MNOs, have had until the iPhone.
- Domains - Posted by James Pearce 3 years 33 weeks ago
A Very Modern Mobile Switching Algorithm - Part I- An important question that most web developers ask when developing their first mobile web site is "how do I distinguish between mobile users and desktop users?". Although this seems like a simple enough question at first, of course there's more to it than meets the eye. In fact, what do we even mean by 'distinguish'? How we distinguish their requirements? Their desires? The services they expect? The browsers they happen to be using?
