Qatar Airways launched a sparkling mobile version of its website this week and raised the question once again over how to prioritise mobile web development.
The Middle Eastern airline created the new service in conjunction with mobile content specialist Mobiqa, allowing passengers to fulfil a range of tools.
Customers can check-in, view flight status, select seats for departure as well as find out information on services and the airline.
As with most mobile websites, a browser is automatically detected so functionality and screen size can be optimised for the user.
Qatar has opted for the service over developing other types of check-in and passenger tools, boasting that the system works "without the need to download an application".
This leads to an interesting question, and one which many airlines and other travel suppliers and services will no doubt be grappling with as they develop a mobile strategy.
What are the advantages of mobile browser version of a site over a dedicated app?
For some it will be development costs and the prohibitive nature of focusing resources on a product for one or more types of handset, rather than a general mobile web version.
But perhaps the flipside of the argument is whether the additional, not critical content such as guides and other information, which can be viewed without data roaming, is a value-add for customers and should be pushed into an app.