- Domains - Posted by James Pearce 4 weeks ago
A Very Modern Mobile Switching Algorithm - Part II- This article follows on from last month's Part I, where we discussed some of the principles of handling mobile users and switching their experiences. If you haven't read it yet please do so before we dive into some of the technical ideas and implementation details.
- Best Practices - Posted by ronan 4 weeks ago
Transcoding: what are the Viagra, Cialis and "Dear Winner" of HTML tag soup?- Over the last 6 months or so part of the tech team in dotMobi has been working on Instant Mobilizer, a site mobilizer service to help small businesses dip their toes in the waters of the mobile web. One of the big problems with content transcoding is deciding when it should be applied: if there is little hope of it working well another alternative should be offered.
- Best Practices - Posted by ruadhan 5 weeks ago
The Best and Worst of the Mobile Web- Our sister-site mobiThinking.com has just published an eBook on "The Best and Worst of the Mobile Web". In it there are examples of winners and sinners, those who do it right, and those not quite right, and why! So now might be a good time to fire up your mobile browser and let us know if you agree.
- Domains - Posted by James Pearce 13 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?
- Best Practices - Posted by ronan 1 year ago
- Web Developer's Guide released
- I am proud to announce we recently posted the dotMobi Mobile Web Developer's Guide on mobiForge. This is quite a comprehensive guide to mobile web developement. It layers on the advice from the W3C's Mobile Web Initiative Mobile Web Best Practices 1.0 document, but takes it further.
