background image
  • Apps - Posted by ruadhan - 22 Jan 2015
  • Thumbnail of Section Feature Image

    App deep linking: Do we really need Facebook App Links and similar services

  • It seems odd that in 2015 we must address ourselves to the problem of linking resources across a network, but in the version of 2015 we're lumbered with, we live in an appified world, so address ourselves we must. While linking has formed the backbone of the web since the demise of Compuserve and AOL's walled gardens in the mid-nineties, the apps that populate our smartphone home screens are about as interlinked as Compuserve's forums in the early 1990s; which is to say, not very interlinked at all.
  • Browsers - Posted by ruadhan - 19 Jan 2015
  • Thumbnail of Section Feature Image

    Standards and browser compatibility

  • Browser compatibility is hard. Especially on mobile. If you thought things were difficult 10 years ago when there were only a handful of browsers to contend with, then thinking about the situation for mobile may make you dizzy or depressed. For now we live in a world of tens of thousands of devices of wildly variable shapes and sizes and capabilities. And we have to make the web work on all of them.
  • Browsers - Posted by mark.anderson - 18 Feb 2015
  • Thumbnail of Section Feature Image

    Getting Ready For HTTP 2.0

  • HTTP is the underlying mechanism that runs the web. It is the language spoken by browsers and web servers to communicate, download webpage elements and upload user data. The version we currently use is 1.1, a specification that is now almost 15 years old.
  • Browsers - Posted by casaise - 06 Mar 2013
  • Thumbnail of Section Feature Image

    Developing custom pictograms for the mobile Web

  • A matter of trade-offs Pictograms – miniature graphical representations of states, actions and objects – made their way into the mobile Web over 15 years ago. Several normalized (UNICODE, WAP) and proprietary (Japanese emojis, Openwave) mechanisms are in place to enrich Web applications with pre-defined images.
  • HTML5 - Posted by SantthoshSelvadurai - 10 Jan 2013
  • Thumbnail of Image of man evolving from monkey

    HTML5 for mobile developers

  • Why HTML5 and why now? When it comes to touch-screen mobile devices, native applications have led the way in terms of performance, speed and tighter integration to specific platforms. Unbound by the need to conform to standards, native apps could rapidly take advantage of the latest hardware and operating system innovations, while Web technologies always had to wait for the international community to agree and implement standards first. But with the HTML5 specification coming to fruition, browser-based mobile apps are rapidly catching up with the natives.
  • Browsers - Posted by casaise - 06 Nov 2012
  • Thumbnail of Stone tablet with hieroglyph pictograms

    A Guide to Using Pictograms in Mobile Applications

  • A long-standing feature Developers inspecting the user agent profile of a modern handset like the Motorola XT682 ATRIX TV may be surprised to discover the following ImageCapable declaration which indicates whether a device can display images or not: <prf:ImageCapable>Yes</prf:ImageCapable>
  • Content Adaptation - Posted by mclancy - 03 Feb 2012
  • Thumbnail of Martin Clancy

    Future of the Mobile Web

  • Last week we hosted an event loftily entitled "The Future of the Mobile Web" at the Dublin Convention Centre.
  • Best Practices - Posted by ronan - 23 Jun 2010
  • Thumbnail of

    Measuring the Effects of Operator Transcoders

  • The issue of mobile-operator transcoders on the mobile web has been hugely controversial. For many iPhone and Android phone owners the negative effects of the transcoders are no longer visible and the issue has dropped off the radar, but they remain a serious problem for those using lower-end devices.
  • Content Adaptation - Posted by jonarne - 03 Mar 2009
  • Thumbnail of

    Kind of a "sunshine transcoder story"

  • I guess many of you have been following discussions on various attempts by network operators to transcode desktop web sites and squeeze them on to a mobile device, without respecting the intentions of content owners. The case I'll be talking about is the TeliaSonera case, and their "SurfOpen" service. First time around, the launch caused an uprising among the content owners forcing TeliaSonera to go offline with SurfOpen. Now SurfOpen is launched again with a more reasonable approach.
  • Usability - Posted by casaise - 05 Dec 2008
  • Thumbnail of Section Feature Image

    Character Encoding Issues and the Mobile Web

  • Character encoding, the binary representation underlying every symbol in documents delivered to mobile devices, is often treated as an afterthought in mobile Web development. Many developers simply rely upon ISO-8859-1; not a bad choice, as this encoding efficiently supports all important Western European languages, has long been available in the mobile and fixed Internet, is widespread among low-end phones, and is the default encoding in the HTTP standard.