In the mobile device world, there is no such thing as one size fits all. Although just two mobile platforms dominate the market today – Android and iOS – applications will need to work well on devices of all shapes and sizes, from the sleekest smartphones to the bulkiest tablets.- Mobile app development
Apps might also need the ability to support new classes of a mobile device as and when they take off, such as smartwatches or augmented reality viewers such as Microsoft’s HoloLens. And the explosion of fixed and mobile connected sensors and appliances – the internet of things (IoT) – opens up countless opportunities
to develop ever more useful mobile apps that control and/ or communicate with these devices to enable innovative capabilities and services.
So how do organizations achieve the agility they need to develop useful and compelling mobile apps and services, in a timely and repeatable way, that continually delight customers? Should they opt for cross-platform web apps or create separate native apps for Android and iOS, optimized for different-sized devices? And what is the best way to organize development teams and processes? Among those at the forefront of mobile innovation, opinions on the most productive approaches to mobile development vary, but it is possible to draw out some common threads.
On the question of whether it is better to develop native apps or go for a cross-platform approach, there is no right or wrong answer – it depends on the business’s needs and its customers’ preferences. Many organizations deploy both.
Innovation consultant Nick Lansley spent three decades at Tesco, including over 10 years as head of research and development and latterly as head of open innovation at Tesco Labs. Having talked to many customers, he believes that although there are pros and cons to both the native and cross-platform approaches, native apps generally offer
the most advantages for retailers. Continue reading