So which mobile approaches is best for your business? Like most things, the answer is “It depends.” At the core understanding, your customer and your market are a given. You absolutely must have a website. These things are simply the table stakes. When a designing a website you must design for mobile first, otherwise you are just wasting your money.
A comScore report in 2014 stated that smartphone and tablets account for 60% of all online traffic and that 51% of the online traffic is driven by mobile applications. The numbers vary, but the average attention span in 2015 with 8.25 seconds and 17% of typical web page views last less than 4 seconds. So you have 4-8 seconds to capture attention and achieve engagement with a customer. Why do you want to achieve engagement? You want the person using the site to buy a product, call you, read your message, share your content, use your tool, or take some action. Because mobile rendering is slower your site must be highly optimized for mobile. This is why mobile first is required. Let’s examine each mobile approach.
While your capital costs for creating the site increase, you achieve a better experience for your customers that can facilitate more reach and engagement. Your operations and maintenance costs are less than other approaches because you only have to maintain one set of content. Additionally, your site is more future-proof or future-ready as new devices within the same general screen sizes as your set points are released. However, you are not protected from browser or standards changes. Overall Responsive Design is the best bang for the buck.
The advantage of responsive design is that you have one website and one set of content to maintain that provides a consistent user experience on all types of devices. Having one website means you have a single domain that exposes single canonical URL to the search engines. Bing, Google, Yahoo, and other search engines see this as the preferred way of providing a mobile site. This method of mobile design a best practice and keeps your site from having complicated redirects that could hinder indexing your site's content and preserves link equity. However, one drawback is that because a single page is used for multiple devices you may have to compromise on your calls to action options. This design method can also make pages more complicated when entering content.
Adaptive Design is a term first coined by Aaron Gustafson. Adaptive Design is similar to Responsive Design in that the website designer has to divide the design into “set points” that define the general size and layout of typical devices. The main difference is that adaptive design is that it is “server-side”. With adaptive design, the web server detects the type of device the user is using before it creates and sends the page to the browser. Once detected it loads a version of the page that is then optimized for the dimensions and native features of the device and then sends that page to the browser.
The big advantage of adaptive design is that it allows you to create a more mobile-centric experience because you can utilize the built-in features of the user's device. Options such as accessing location, touch interface, interacting with the camera, or rich interaction such as interacting with Cortana on a Windows Phone are all options with adaptive design. Additionally, by serving up a page optimized for a specific device you only have to implement the code necessary for that device, thus reducing download times, and improving the user experience.
Using adaptive design will increase both capital cost to build the site as well as operations & maintenance costs. Each update has to be carefully planned to be responsive reducing some of your agility.
Perhaps the biggest drawback of the mobile site approach is that you have two sites to maintain. Two sites means you will incur additional capital costs to build the site, but more importantly the operations and maintenance costs also increase.
Mobile sites are good when you already have a large site with a lot of content and re-working the site for a responsive framework is cost prohibited.
A Native Application is an application built for a specific mobile operating system and device or devices. It does not run in a browser. A separate version of the application is created to target a particular mobile operating system, computer chip set, and hardware of that device. The creator of the application must support it on the various platforms and devices that they target, so this is a significant commitment to the technology.
When choosing to build a native mobile application you must define your audience and what devices they use. Right now the major operating system providers for mobile applications are Apple - iOS, Google - Android, and Microsoft – Windows Mobile. Blackberry still exists. It’s not dead yet, but hospice is calling. Within these mobile operating system providers, there are multiple versions of their OS and hundreds of thousands of hardware devices that include smartphone and tablet platforms.
Native applications require the largest capital investment as they are expensive to build and they are costly to maintain. Capital costs and operations and maintenance costs to design, build, test, deploy, and support native applications increase with each device and OS you support. Each of the major mobile device players has a store where you must to "pay to play" per say, and your application must meet each store's certification requirements.
In many cases such as engaging with consumers, a native application is orthodox. It is the minimum requirement for entry into many markets these days. However, the cost versus the benefit must be weighed.
There is no one size fits all. Many companies that are looking to engage mobile visitors now take a Hybrid Approach. Their website may be a combination of responsive and adaptive or they may have a mobile site for a portion of their site.
In some cases, people are leveraging the responsive or adaptive code on their website to render a hybrid native application to re-use elements of their website. This method of mobile development provides a native application experience with an embedded browser control in the application to render the HTML code. However, this often comes with a degraded user experience.
The Hybrid / Combination Approach is a mixed bag when it comes to the cost element. The increased complexity of this approach can add to your cost of maintaining and updating this technology. However, your initial capital costs to develop and implement can be lower because you leverage the code in your website as part of this method. For example, you may implement a native application and used elements of your responsive design from your website in your user interface.
Many companies realized that both a mobile website and a native application are a cost of doing business and opting to provide both experiences for their audiences.
Can you achieve engagement and reach business nirvana or will you stick your head in the sand and lose your piece of the pie? If you reach just 1% of the 15 billion devices out there, you have the potential to engage 150 million customers. The real question is: Can you afford not to?
No matter what you do, act now! Educate yourself and seek help from a mobility expert. Your business could transcend into a much more profitable state.
So far, we’ve addressed the fundamentals of measurement and metric validity. In this post, we’ll apply those lessons to the specific arena of advertising.
Learn how to update an already scheduled newsletter send in Kentico 9.
We all have the same 140-character limit for our tweets so how do we make our content stand out above others?
In this blog learn how to work your way around the SQL Injection Kentico web part.
Heads-up! We are hiring a Cloud Infrastructure Architect https://t.co/9SmTWReKS2 #fldev
Heads-up! We are hiring a Front End Developer https://t.co/Rrn8L00knZ #fldev