Category Archives: mobile market

Tech trends to look out for in 2016

city-of-blinding-lights-1196157-1279x852

This time last year I was looking forward to what mobile would offer us in 2015. This year I’m casting the net further afield, but inevitably mobile still features to one extent or another, whichever technological trend you look at. After all, for many ‘the mobile internet’ is now simply ‘the internet’; the distinction has become immaterial as mobile becomes their main touch point for information and online interactions.

Here’s what I expect to be the main trends, concerns and areas of attention over the course of 2016.

Web design

There’s a lot of development around web design and UI patterns right now, fuelled by more businesses recognising the need for their sites to be mobile/multi platform ready. As mobile traffic starts to overtake desktop traffic, and continuity and consistency of customer experience across multiple touch points becomes increasingly relevant, so too does the adoption of approaches and templates that makes it easier to achieve.

The easier you make it for a customer to recognise regular functionality, such as registering an account or going to the checkout, the better – we’re now at a point with commonly used features where it’s no longer necessary to reinvent the wheel just because you can. If there’s a tried and tested model of usage that is instantly understandable by the user, then in most cases it’s going to be better to adopt that than force a person to work through something new.

This link goes through the common UI design patterns you can expect to see in 2016. In fact you’ve probably seen a few already.

Google AMP

In October last year, Google announced its Accelerated Mobile Pages (AMP) project. The objective was to development a set of technical specifications that publishers could adopt in order to make their websites and online content load faster when accessed by mobile browsers.

Following successful testing, Google are set to roll it out February this year and have already secured commitments from top news, advertising and analytics providers. For developers it should mean that the same code can be used across multiple mobile platforms in order to make pages, regardless of content, load more efficiently. For users it should mean less time surfing and less data spent in the process.

This page provides more info on AMP and links to instructions and code for developing your first page using the specification.

Mobile payments

Mobile payment options and awareness grew over the course of 2015. However, in spite of that, usage appears to have remained low, so expect 2016 to be about how to reduce the gap between awareness and adoption.

Doing so will be as much about increasing opportunities to use mobile payments as it will be about encouraging people to use them. In reality, mobile payment is just another way to use your credit card. Once mass adoption kicks in that won’t be such a big deal, but right now what’s the incentive for people to use a mobile wallet over other payment options that are so well established?

Starbucks provided a clear value proposition with their adoption of mobile payments, incentivising use with special offers on their own products as well as those offered by strategic partnerships (Spotify and The New York Times for example). July last year, Starbucks CEO Howard Schultz revealed that mobile transactions accounted for 20 percent of all in-store sales; equating to more than 9 million mobile transactions a week and a 4 percent increase in foot traffic.

Others are also starting to do loyalty programs too: Android Pay started last year with Coca-Cola (awarding points for use against purchases at Coca-Cola vending machines) and Samsung Pay incentivised activation on their handsets in the US with a free wireless charging pad.

Fragmentation, point of sale compatibility and ongoing concerns about the security of payments are still hurdles to adoption, but despite those it does seem that mobile payments are now finally in a position to start gaining some traction.

Rising mobile video adoption

This article from last year covers a comScore report highlighting how people consume video on mobile devices.

It’s clear that improvements in mobile technology and the networks supporting them has reduced the barrier to people accessing what they want, whenever they want. For example the report shows that YouTube app usage rates on smartphones increased by 34 percent over the year, nearing 5 hours of viewing a month; on tablets it was an average of 9 hours a month.

As this trend continues over the course of 2016, advertisers, businesses and media will increasingly be able to reach people with richer content on an everyday basis. With this in mind expect mobile viewings to continue to rise with mobile advertising increasing as a result. Also expect these increases to be supported by greater use of video in all aspects of mobile, as people are now willing to watch more video content for longer on their devices.

Wearable technology

Yes, 2015 was still slow moving for wearable tech. Google Glass stopped selling and smartwatches were still absent from many a writst, but hey Rome wasn’t built in a day.

In truth, the biggest hurdle isn’t the technology, it’s social acceptance. Google Glass is apparently coming back this year, but it’s coming back as a tool for enterprise, which makes sense because used within industries with a legitimate business case Glass provides genuine value without the social stigma to worry about.

From a consumer perspective the sticking points for many are still design, varying standards, having to tether your device to a phone (in most cases), and of course the ever present poor battery life. All these are getting better though. Variety in design is growing, standards are maturing, both Apple and Google have taken steps towards making devices less dependant on direct tethering (through the introduction of Wi-Fi support), and devices with better battery life are starting to arrive.

It’s worth considering that eventually we will come to a point where we will no longer consider the delivery medium; we’ll simply expect to access information and services regardless of where we are, and that it will be delivered to us in the right context for that environment.

Think of television as an example. When I’m watching something at home with others (or on my own) I watch it on the big TV. When the big TV is already in use I use my tablet. When I’m on the train, squashed in with the other rush hour travellers, I look at it on my phone. That makes me sound like a TV junkie, but you get the idea. The point is I don’t even consider the hardware I’m using to watch what I want to watch anymore, I just use the right tool for the job without even thinking about it. Smartwatches and the Internet of Things will eventually become part of that ‘continuity of information access’ model for more and more people.

Perhaps one day we’ll have the Apple iEarBud whose UI is purely audio with voice control. You don’t think so? Give it time…

Internet of Things

IoT had a solid presence at CES, showing that there’s a real impetus behind moving it forward this year.

For starters Microsoft and Samsung announced a new partnership to integrate Samsung devices and software with Windows 10 devices, allowing the monitoring and controlling of household appliances through the use of apps that run on Windows.

Meanwhile, Qualcomm were putting a lot of focus on connected devices within the medical/health care vertical of IoT. Items on display covered diagnostics, therapeutics,  and physiological monitoring.

Kwikset’s Kevo Smart Lock turns a smartphone into keys for a home through the use of an accompanying app for iOS and Android devices. Keys can be set up and deleted and even temporarily given to other users to allow access on an ad hoc basis. Of course the main hurdle will be people’s concerns around security – Kevo will track and audit activity, detailing when eKeys have been locked, unlocked, sent out or accepted, but is that enough to make you feel comfortable with the concept?

Intelligent beds, smart shoes and other not so obvious items mixed with the more recognisable watches, jewellery and fitness trackers, showing that there’s a definite desire to explore the possibilities that a world of connected devices and apparel can offer. It was also clear that developers are now looking towards more focused areas of use whilst the larger consumer market continues to be slow to adopt; health care and engineering being the prime examples.

The knock on effect of a spreading Internet of Things will of course be even more data to consume and understand. Better and more effective ways of analysing the information as well as more accessible and creative ways of visualising the results will be needed in order to capitalise on the greater volumes of content streaming in.

Analytics and Big Data

And so we’re reaching a point now where Big Data is less a buzzword and more something that businesses actually do. The means to manipulate and analyse enormous amounts of information (that isn’t necessarily stored in one place) is going to be key to customer insight and maximising ROI. It’s also going to prove invaluable in improving the flows and processes internal to businesses as well.

As IoT, Cloud, and Big Data continue to converge, anyone that is still ignoring the importance of data and analytics, be it Big Data or the more traditional and established forms of analysis, is going to miss out on a vital source of intelligence and the means to understand it. This article on Big Data predictions for 2016 covers a lot of the points of interest.

Focus on customer service as the differentiator

As technology matures it becomes an equaliser rather than a differentiator. In some markets now the differences in the process you step through are minimal, regardless of the competitor you choose to go with. Where businesses have their web and mobile solutions figured out, expect them to start putting the focus back on the level of customer service they provide rather than the technology channel they use to deliver it;  and expect them to be supporting this with analytics and Big Data.

Virtual Reality

It seems to be the right time for VR; the tech being used is better, and unlike before people appear to be open to the greater breath of potential for it’s application.

Sure, it’ll start off being used for games this year, but this time round development frameworks for VR are more accessible and users have already dipped their collective feet into the concepts of augmented and virtual reality via their smartphones (Google Cardboard for example). What this should mean is greater interest, quicker adoption and more diverse application of the technology.

It also doesn’t hurt that the likes of Facebook are backing VR with their investment in Oculus Rift. They aren’t the only ones; Sony, Samsung and HTC are also coming to market with their offerings too.

Digital assistants, robo advice and AI

As Siri, Google Now and Cortana continue to improve, and as consumers search for information online more and more, we’ll be seeing “robo helpers”, online guided advice and the application of AI driven systems become more commonplace.

In any instance where advice can be automated, there’s a potential to apply technology to augment the supply of that advice to the end user. There’s good reason to consider it; automated services can allow your workforce to service more customers without a drop in quality, and it does so by allowing you to intelligently focus effort on the areas of customer service that deserve human involvement whilst leaving the simpler solutions or decisions to systems that can deliver them with minimal or no human intervention.

Used intelligently, and blended with access to a human end point as needed, automated advice systems will provide customers with efficient access to knowledge and help whilst simultaneously allowing businesses to reduce costs and scale effectively. In addition, integrating these mechanisms into existing processes will allow businesses to pivot their delivery model towards Millennials and Generation Z as they become the key demographics to target in the not so distant future.

Millennials and the drive for a seamless digital experience

As mentioned above, the expectation for continuity across digital platforms, and through to the associated real world touch points, is going to become increasingly more important.

Although this appears to be the case across an increasingly wider range of age groups than some would have expected, it is the tech-savvy Millennials that are driving this need the most, both with their technical knowledge and their assumptions of what should now be the norm; and as they represent such a high percentage of those who spend, should you really be ignoring their needs?

An increasing amount of people will check online before making any kind of purchasing decision, be it on a product or a service. Right now that means many consumers expect a brand to have a mobile presence, with all the associated features and advanced capabilities that it implies.

However, whilst that may be the focus right now, especially whilst the Internet of Things and wearables are still moving through their slow early days of adoption, we should prepare for the defining desire to be for a seamless multi channel experience, for an experience that is accessible at the point of need rather than dependant on a particular device. So, be prepared to start thinking about how you are accessible via desktop, mobile, tablet, TV, watch, insert you favourite home appliance here; as it’s only a matter of time before this becomes the expectation that mobile is today.  Understandably frameworks that help developers to easily do this are going to be a godsend moving forward, so look out for these in 2016 too.

When it comes to linking the online with the real world, technologies such as Apple’s proprietary iBeacon, Google’s Eddystone, as well as other more open and diverse approaches such as wifi and location triangulation, are attempting to bridge the gap. Feedback on how well these achieve the purpose though differs depending on who you ask,  so I’ll be looking to explore this further in a blog entry later this year.

And if millennials aren’t a good enough reason on their own to pay attention to your seamless digital experience, then consider Generation Z. Where Millennials embrace technology, Generation Z will be the coming of the true digital native, since all they have ever known is a world of mobile apps, touch-screen devices and a landscape carved from social media and a reduced concern about privacy. For them the boundary between real world and the online world is missing – it’s simply one world. Their idea of a seamless digital experience is not that it’s an added bonus. It’s expected. It’s a necessity. Will you be in a position to provide them with it?

Cyber security

There was plenty in 2015 to draw people’s attention to the topic of cybersecurity, and as potential threats continue to mount, it’s no surprise that cybersecurity is front of mind for many businesses as they look for ways to analyse potential weaknesses and protect themselves. SMBs particularly, are finding themselves the target of attacks more and more as criminals look for those they expect to have less security in place.

For companies with fewer IT resources, the threat of cyber attack is likely to push them in two directions:

  • Firstly the use of cloud based solutions that incorporate cybersecurity utilities and approaches that wouldn’t otherwise be available. Cloud providers are recognising this need and increasingly investing in technologies for data protection, network security, threat modelling and quicker incident response
  • Secondly companies, both small and large, are recognising the benfit of collaboration in order to share lessons learned and to establish best practices that will see all those participating better equipped for the threats that lay ahead.

Companies also need to provide their employees with awareness training. It’s important to remember that despite the increasingly sophisticated ways in which systems are being breached, it is often the older, tried and tested low tech approaches that are still the most effective. Phishing for example continues to be used, and the only way you combat that is by educating your workforce. Also, staff need to know the procedures that need to be followed in the event of a breach occurring; what steps to follow to get the systems back up and running and what is the right way to communicate the situation outwards to those it could have an effect on.

Wearables, mobile and the the Internet of Things are not going to help. Unsurprisingly the more connected devices in use by businesses and consumers, the more vulnerabilities there are to exploit. With that in mind it’s likely we’ll see more major data breaches through the course of 2016.

And of course the increase in incidents will increase the focus on security and privacy regulation. Right now attention is on Safe Harbour 2.0, as EU officials meet with US counterparts in February to find a common position regarding which legal channels companies can use to transfer data across the Atlantic.

Going cross platform on mobile, part two: Native, web and hybrid apps

So if we decide, having looked at the market and our product’s objectives, that we need to move beyond a single platform reach model, then we need to look at how we do this in the most efficient and effective way.

You can go native, using the primary programming language for each platform, but it’s going to need dedicated skills for each and of course the time to code for each mobile OS you want to have a presence on.  The alternative is to use well established and understood web technologies for product development, or to use a mixture of the two to create a hybrid approach with the aim of gaining the best of both approaches.  There are also frameworks that allow you to develop for cross platform delivery in one particular language and cross compile as necessary.  We mention these briefly below, but will cover the concept in more detail in part three along with frameworks that use web technologies as well.

In simple terms we can classify the three approaches to mobile app development as follows:

Native app

  • An app installed on a device (usually from an app store, but not necessarily) written in the ’native’ code of the platform/device.  It’s generally accepted that the UI of native apps does not consist of full-screen web page views alone – in this sense a web site ‘wrapped’ in native code in order for it to be distributable via Google Play, the App Store etc. does not constitute a native app.

Web app

  • Web apps are developed using standard web technologies to create a ‘web site’ that attempts to imitate the look and feel of a native app, or at least is designed to look and feel comfortable within the confines of a ‘mobile’ device i.e. it is not just a web page designed for desktop simply shrunk to show on a mobile phone.
  • When is a web app a web app and not a (mobile) web site?  It’s arguable, but for me in most cases it suffices to say that a web app follows the same model, and is used in the same way, as a native app.  The UI is structured along similar lines as an app and is focused upon a specific task.  That it might be consumed via the device’s browser rather than installed through an app store is not seen as making the defining difference (it might make a difference in terms of performance, but that’s not the user’s concern).
  • Also a web site may use responsive web design approaches and mobile best practices to improve the look and consumption of the content on a mobile device, but if it isn’t following an app style user model it can again be argued that this is a web site and not a web app.  As you can tell the difference can be a bit of a grey area.

Hybrid

  • Hybrid apps are an instance of a native app, utilising web and native tech/functionality to varying degrees (e.g to access the device’s camera or to provide the ability to receive push notifications).
  • Most people probably understand a hybrid app to be a similar proposition to a mobile web app, but packaged as a native app with access to native services (à la Phonegap/Cordova apps).  They either try to mimic native look and feel or at least are (hopefully) designed to look and function comfortably within the confines of the app use case.
  • However, hybrid apps sit on a spectrum; ranging from simply being mobile web products ‘wrapped’ in an app (offering little if any native functionality to differentiate them from mobile web) through to hybrid apps that are almost fully native.

Cross compiled apps

  • Cross compiled apps are another approach that need to be mentioned.  Frameworks in this category allow you to write code in web technologies and/or a selection of programming languages, which can then be compiled down to native code for specific platforms.  In theory they should provide closer to native performance than web apps do, but feedback from developers is varied and likely dependant on what is required from the app.

The above are touch points on a spectrum of possibilities, where native functionality can be mixed with web centric technology to varying degrees resulting in varying strengths and weaknesses.  The mix you choose for your product will determine the level of interoperability you have verses the level of functionality:

IntVsFunct

from: http://designmind.frogdesign.com/blog/unraveling-html5-vs-native.html

Or to show it another way:

Nathtmlhyb

from: http://wiki.developerforce.com/page/Native,_HTML5,_or_Hybrid:_Understanding_Your_Mobile_Application_Development_Options

There are many sites that list the pros and cons of these approaches in detail, but in overview you’ll find the following to be true:

  • Native will always be faster, and especially so for richer and more involved experiences, however the drawback is you have to redevelop your product for each platform and you need access to skilled developers as required
  • It’s good to remember that expectations are different when people open an app compared to when they browse a site – native is on balance more capable of delivering the functionality that’s expected from an app, and so more focus will be needed to meet user expectations when developing apps via non native frameworks
  • Mobile web apps use known technologies, offer greater cross platform reach and promise ‘write once, deploy many’ capabilities, however the truth is that the differences between devices, their browsers and OS means you can not guarantee how well they will perform across all permutations – pure web apps do not have access to native functionality and we’re still waiting on standards to be set by W3C.
  • Hybrid apps potentially offer the best of both worlds, utilising native code to leverage native performance and functionality, whilst creating other elements in web technologies to gain the benefit of known tech, quicker updating/maintenance (web elements can be updated within the app without the need to resubmit the entire app to the app store), and easier portability
  • As previously mentioned, hybrid apps exist on a spectrum going from highly web app oriented to heavily native, depending on the needs of the product – there are also a number of frameworks that allow web code to communicate with and use native functionality, but these perform to varying degrees and due diligence is needed to confirm if the framework delivers sufficiently for your particular needs.

There is no right or wrong approach, but right now you have more chance of seeing a badly performing web tech based app than a native one.  If you’re going to leverage web or go hybrid make sure you do what you can to make your solution as performant as possible.  I have read a number of studies during 2013 that indicated the majority of people were disappointed with their experience of browsing web on mobile devices and would use their smartphones more if the browsing experience improved.  64% of smartphone users expected websites to load in 4 seconds (compuware, April 2013).  Download speeds are the biggest factor in achieving this – to hit the 4 second load time, based on general UK speeds right now, a website should aim to be a maximum of 1MB for 3G users and 3MB for 4G users. However due to network latency, smartphone memory, cache and CPU, in reality the download size needs to be less to make up for all of these potential bottlenecks.

Below are some best practices for making web performant.  These especially apply to mobile:

  • Reduce dependencies/HTTP requests, image dimensions, and client side processing whenever you can
  • Use CSS3 instead of images where possible, sprite your images using CSS or transfer your images using a data URI scheme
  • Minify your code
  • Eliminate redirects
  • Load contents lazily and don’t load data that will never be seen or used by the user
  • Utilise a mobile content first policy for your web content or create pages specifically for mobile use alone
  • Plan for the lowest common denominator if you’re looking to reach many users – alternatively focused on a specific set of devices that represent your audience and focus on their capabilities alone
  • JavaScript on devices with slow processors can be expensive to execute, so it is important to make sure your client-side code is lean, mean, and uses minimal memory too, as well as implementing network-based optimisations
  • Policies and standards for web technologies using advanced features like geo-location, camera integration etc. are still developing and the implementation of HTML5 is far from uniform – it varies from browser to browser and from mobile platform to mobile platform, so be cautious of any promises of “one size fits all” tools and perform some proof of performance tests up front:
  • The Nitro JS engine used in mobile Safari is not available to the UIWebView, which is used to show web content within apps on Apple devices, so performance will be worse – test how (the lack of) JIT compilation affects your app’s performance by building a test app, or alternatively by installing Google Chrome for iOS, as it uses the same UIWebView component and is similarly compromised when it comes to JIT compilation
  • Similarly the same browser engine isn’t used across all Android devices and so performance can differ in this way too
  • Write efficient JavaScript code that doesn’t block the UI thread and follow language optimisations and best practices for it

Lots of scope for deep diving on this subject, but that would turn this blog entry into a book.  Instead the below links should provide some food for thought on the subject of mobile app/web development and act as a springboard to further investigation:

If you take away one thought from the above let it be this: there isn’t one ring to rule them all… not yet anyway.  Right now we still need to take each mobile project on its own merits and decide the best approach for it.  The choice you make will be dependant on the product you want to create, the skills you have to hand and the other business factors that influence your efforts on a daily basis.

That said there is still a trend for developers to be moving towards HTML5 and other cross platform facilitating frameworks, and understandably so when we need to make our development efforts as efficient as possible, but it is by no means a clear cut decision yet and the options available must be explored.   Take a look at this article from VenturBeat on what developers felt at the end of last year.

In part three we’ll wrap things up by taking a look at three available frameworks that offer an alternative to native development for going cross platform on mobile.

Going cross platform on mobile, part one: How the market looks

I know there are a 101 articles written on the topic already, and I’ve been involved in more than enough conversations about it myself, however interest is rising to appreciable levels again here within the group, especially as our brands move more and more beyond their initial iOS based initiatives, so the time felt right to actually put some words down on the topic myself.

The pure native app approach is great if you’re targeting one platform (or if your budget allows you to go native ad infinititum), but depending on what your objectives are and what type of product it is that you are developing, the numbers don’t always stack up so well when you want to expand your audience reach beyond a single marketplace running on a single OS.  In most cases you’re going to want to look at how you reach more people, on more platforms, whilst doing it efficiently in terms of effort and cost, whilst at the same time also ensuring quality doesn’t drop to a level that’s detrimental.  So, you need to look into what the options are and what each of these options mean, in order to make the right decision for the app you have in mind.

More on that in part two.  Firstly, it’s worth noting the state of the market and confirming that there is in fact a good reason for your app to go cross platform in the first place.  I can’t tell you if your app suits a single platform release or not, but here’s the current trends and state of the mobile market…

Worldwide statistics from IDC Worldwide Mobile Phone Tracker (November 12, 2013):

OS 3Q 2013 Market Share 3Q 2012 Market Share
Android 81% 74.9%
iOS 12.9% 14.4%
Windows Phone 3.6% 2%
BlackBerry 1.7% 4.1%

In terms of year on year trends global figures are pretty much in line with those tracked for the UK by Kantar Worldpanel last year (for July to Sept 2013, published November 4, 2013) other than the more pronounced uptake in Windows:

  • Android – 58.4% share compared to 58.6% for the same period 2012
  • iOS – 27% share of the market, compared to 28%
  • Win. Phone -11.4% of UK market, compared to 4.2%
  • Blackberry OS share dropped from 8.5% to 3.1%

While iOS has a higher market share in the UK compared to the global figures, the Android figures are still high enough to highlight the value of cross platform deployment when wanting to reach a wider consumer base.

Keep an eye on Windows going forward too.  Although it only accounts for 1/10th of the UK market, in terms of trends it has risen around 300% in the past year.  A comparably small user base, but the right cross platform development approach will allow you to prepare for future market growth without committing dedicated work effort in order to do so.

Finally, taking a look at the most popular handsets tracked by uswitch shows us that Apple and Android handsets make up the top 10, with iPhone and Samsung consistently the strongest brands from 2013 through to 2014:

UKs most popular mobiles, Sept 2013 (uswitch mobile tracker)

  1. iPhone 5
  2. iPhone 4S
  3. Galaxy S4
  4. iPhone 4
  5. Galaxy S3
  6. HTC One
  7. Galaxy S4 Mini
  8. Galaxy Ace
  9. Xperia Z
  10. Galaxy S4 Mini

UKs most popular mobiles, Jan 2014 (uswitch mobile tracker)

  1. iPhone 5s
  2. Galaxy S4
  3. iPhone 5c
  4. Galaxy S3
  5. Galaxy Note 3
  6. iPhone 4S
  7. HTC One
  8. Sony Xperia Z1
  9. Galaxy S4 Mini
  10. Google Nexus 5

So yes, if you’re looking to expand your reach it stands to reason that you want to look beyond iOS to at least Android.  Previously if you were more interested in direct profits from your apps rather than extending user base and brand awareness then you might as well stick to iOS, and so far latest figures suggest this is still the case.  However I think we can expect this to change at some point, so even if now isn’t the time sooner or later you’re going to have to spread your wings and move to new skies.  If you’re looking to extend reach and brand awareness then it’s a no brainer – you want to put you’re app into as many hands as possible.  Going cross platform is the way to do it, and leveraging technologies that are easily reusable is the most efficient way to do it.

In part two we’ll cover the differences between native, mobile web and hybrid apps, and cover the principles to keep in mind when using web technologies rather than native code to develop apps.