2013 hot The right way to release a mobile app - Human Services' new student app

I'm pleased to say that with all the apps now being developed by Australian governments, the Department of Human Services' new 'Express Plus Students' App, has managed to address almost all the criticisms I've had previously regarding government mobile apps.

What were these criticisms? And which did the Department fail to address? Read on...

Have a clear purpose

The first criticism I have about government mobile Apps is that sometimes they seem to be created without much thought about whether they actually are needed at all.

It is important to resist any urges to create a mobile App simply because you want to make one (as a shiny toy, for experience or credibility), or a senior manager wants to look good to their peers or Minister.

There are aspects of government business which, frankly, the community just isn't interested about. Apps, particularly in government, need a reason - a good reason - to exist, as well as an audience interested and ready to download and use them.

Don't create an App when you need a mobile site

One of the most costly mistakes governments (or anyone else) can make is in developing a mobile App when a mobile site would have met your needs and be more cost-effective.

If you're mainly providing a wrapper around website content and functionality, or providing textual information with a few images and buttons, it is usually faster and cheaper to build a mobile site than a mobile App.

This is because, well, building websites is simply cheaper, and while a mobile App needs to be recoded for every operating system and screen size, a mobile site will work across all internet-capable mobile devices without the coding overheads.

It is far easier to update as mobile site to suit emerging devices - by creating device specific style sheets, which are automatically applied when someone using a particular device visits.


This saves the money that would otherwise be spent in developing versions of your App for different devices and keeping them all up-to-date.

Mobile sites (should if built well) allow you to update the content easily, quickly and cheaply without potentially requiring development time and a user download. Though note that with clever App design this can also be achieved through having a mobile App that presents content drawn from a website or even a text file online.

The worst case - and I have seen it in practice - is when content is hard coded into an app, then there's a need to update it urgently. Frankly it's not easy to push an App through the iStore in less than two weeks, and this is after development. Apps are bad news for urgent updates.

Where your content is mostly words, mobile download speeds aren't generally an issue. It is when you get to video content and sophisticated functionality, or where your users are likely to operate beyond cost-effective 3G or wi-fi range (such as boat owners, remote communities and foreign travellers) that you may wish to consider a mobile App approach actively.

Design to standards including accessibility

When designing apps it seems that many basic usability and accessibility features can get forgotten, with many apps designed to operate in non-standard and non-intuitive ways. There are standards for a reason and standards-based apps will stand a better chance of feeling easy for regular app users to adopt (just like most Windows and Mac programs follow standards).

This means using the design paradigms for iOS, and Google's design principles for Android.

It also means tapping into the accessibility features built into iOS, and Android.

Use inbuilt controls

Using the inbuilt features and controls in mobile operating systems is also important. For example rather than building a map feature, use the one provided on the device.

I have seen Apps where the developer has built all kinds of nifty features that already existed in the operating system. This is sloppy, expensive and rarely results in a better experience.

Built in a reporting system

While you can find out how many App downloads have occurred from most App stores, tracking actual use of mobile Apps requires a reporting system hooked into the code itself.

This is fairly easy to do today, with Google Analytics supporting App reporting, and a number of custom reporting packages available from other organisations that are simply embedded in your App's code.

Having this reporting information is about more than accountability to the Minister, it is about understanding where, when, how and why people are using your mobile App, and helps you build an understanding of your audience so you can keep improving the App - and build new ones - that are even better.

Too many government apps are released without a reporting system, and it's very hard to reverse-engineer one in after release. People who previously downloaded an App can get mighty sensitive about the information you are suddenly collecting plus you miss the initial burst of activity that helps you identify issues and strengths.

Have an official agency account at App stores

This is one of my biggest frustrations, as seeing an official government App listed in an App store as having been created by 'Silly Mobile App Company' instantly reduces the credibility, trust and the ability to actually find the App by searching on the agency's name.

Also when an agency is making several Apps, often each is with a different Mobile App developer due to tender processes or skills. They then get listed under the name of the developer in the App store, which then cannot list your Apps together in a single place ('see other apps from this organisation'), reducing your agency's ability to cross-promote.

Plus, what happens if you make an App with a company, then have a falling out? It can be tricky, even impossible, to get the App out of the developer's account and move it to a new account on App stores.

It seems a no-brainer to me that agencies should register accounts on the main App stores before they start creating mobile Apps. This allows them to register their Apps under their own name, rather than that of developers and to use their reputation to build interest and trust.

Link to your Apps

Due to the wonders of modern technology it is possible to link from your media release and website to your App, as well as to link from your Apps to your other Apps.

Something that agencies still don't appear to do well is to link their mobile Apps together, with an in-App method of downloading other Apps from the same agency, or even government.

Also media releases still lack basic details such as screenshots of Apps or links to them in the App stores. I know it might come as a surprise to some people, but journalists understand how to use hyperlinks, as does the community - and both groups love pictures as much, if not more, than they love words.

Most media releases are read online, not on fax machines - so links can allow someone to get straight to the mobile App without messing around with a search in an App store.

With many releases now read on mobile devices, it makes sense to allow people to click to download the App straight away. It is inconsiderate to force someone to search when they can click.


And that final point is my only criticism of Human Services' 'Express Plus Students' App.

Go to their media release, which has been widely tweeted, and there is no link to the App in the iStore. Hopefully this is an oversight they will fix. It should not take long!

Note that I can't tell if Human Services' App has a reporting system built in either, but I'll give them the benefit of the doubt!


So how has Human Services' App been received by its audience?

This is a great 'good news' story already - with a number of five-star reviews. Check them out yourself at the App iStore (and note that there's more reviews to read if you can click through to iTunes).

2012 OpenAustralia Hack(s)fest on FOI - for hackers, media, activists & FOI gurus

The OpenAustralia Foundation will be holding the first Australian Hack(s)fest as part of the countdown to the launch of their new FOI assistance site, designed to make it easier for ordinary Australians to put in FOI requests to Commonwealth agencies.

The event, being held in Sydney at Google's office, will be held on the weekend of 17-18 November.

For more details and to register, visit: www.openaustraliafoundation.org.au/2012/11/05/youre-invited-to-our-freedom-of-information-hacksfest/

2013 Are organisations failing in their use of social media and apps as customer service channels?

Guy Cranswick of IBRS has brought my attention to a media release about a new report from Fifth Quadrant, a leading Australian customer experience strategy and research consultancy, on social media and smartphone app customer service enquiries.

The report looked at how many Australian consumers had used these channels for customer service enquiries and why they'd used, or not used, them.

The figures are quite dim reading...

The study (of 520 participants) indicated that only 16% of Australian consumers have ever used social media for a customer service enquiry and less than one in 10 Australians had used this channel for customer service in the last three months. Gen Y ran 'hotter', with 29% having ever used social media for a customer service enquiry.

Why didn't people use social media for these enquiries? The survey broke down the reasons as follows (multiple reasons allowed):

• 32% said it isn't personal, 
• 30% said they did not know that they could,
• 30% said they were concerned with security issues,
• 22% said they thought it would take longer than a phone call, and
• 20% said they did not think it would be a good experience. 

The research also looked at smartphone apps and their use in customer enquiries. Here the figures were even lower. Only 15% of Australian consumers had ever used a smartphone application for a customer enquiry (20% amongst Gen Y), and only 8% of consumers had used this channel in the last three months.

The reasons for not using apps were similar to social media:

• 41% said they did not know they could,
• 21% said they thought it would take longer than a phone call,
• 16% said they thought it would make the process slower to talk to a customer service representative,
• 15% said they did not think it would be a good experience, and 
• 13% said that they did not think it would be easy to use.

My immediate reaction was to say that, well, social media and smartphone apps are still very young and immature, both effectively five or less years old as mass communication and engagement channels. It takes time for organisations and customers to adopt their use for customer service.

However, other research suggests that this may not exactly be the case.

Fifth Quadrant’s 2012 Customer Service Industry Market Report (with 120 business participants) found that 69% of Australian based organisations had implemented social media and 23% had implemented smartphone apps for customer service. This is a small sample, but still statistically significant.

In other words, while 69% of organisations will accept customer service enquiries via social media, only 16% of Australians have used this approach and while 23% accept these enquiries via smartphone apps, only 15% of Australians have used these channels.

So if organisations are offering these channels, why do so few Australians use them?

More of Fifth Quadrant's research offers a clue...

How many times should a customer have to contact an organisation to resolve a customer service issue?

Fifth Quadrant reports that the level of 'first contact resolution' (where a customer only needs to contact an organisation once to have their query resolved) is much lower for social media or smartphone app than for phone contacts.

• Phone: 78% of queries handled in one contact
• Social media: 59%
• Smartphone app: 51%

In other words, 41% of people attempting to use social media and 49% of those using smartphone apps will have to contact the organisation multiple times (often resorting to phone) to resolve their query.

This significantly increases the cost of the interaction to the organisation and the customer and reduces customer satisfaction.

So what's the issue? Poor organisational implementation of social media and app channels.

Fifth Quadrant's Director, Dr Wallace said,

“There is no question that social media and mobile channels will be important in the next few years as the percentage of consumers who use these channels for customer service doubles year on year. Rather, it is a question of how effectively organisations address the supporting business processes and skill levels of social media customer service representatives.

The challenge for Australian business is that they typically do not consider Multi-channel Customer Experience as a strategy, hence these new channels lack integration, they do not have accurate revenue and cost models and there is poor data analytics. This has resulted in a sub-optimal channel deployment and as the research shows, ultimately, a sub-optimal customer experience.”

So let's go back to the reasons again...

• There was an awareness issue (social media: 30%; apps: 41%).
  Organisations need to integrate information about the ability to engage them through social media and apps in their promotion, packaging and engagement.
• There was a speed/perceived speed issue (social media: 22% (take longer); apps: 21% (take longer) and 16% (slower)).
  Organisations need to integrate these channels with their other customer contact points, building the protocols and processes to make it faster and easier to engage online than by phone.
• There was an experience/usability issue (social media: 30% (not personal), 20% (experience); apps: 15% (experience) and 13% (easy to use)).
  Organisations need to codesign their channels with customers, putting extensive work into the upfront experiential design to make them an easy to use service with a great user experience. The investment in design is more than offset by the long-term cost savings in moving people from high-cost phone to low cost online service channels.
• There was a security issue (social media 30%).
  Organisations need to take the same actions as ecommerce companies did to reduce this to a minimum, providing context, clear security measures and escalation and rectification mechanisms that assure users that they won't be disadvantaged by any security problems.

Overall, organisations need to run these channels as part of their customer service framework, not remotely via communication, marketing or IT teams.

Want to learn more about the research and report?

See Dr Wallace's blog, Your call.

And here are some of the key findings from Fifth Quadrant’s 2012 Customer Service Industry Market Report (n=120):

Social Media:

1. In Australia, the predominant share of the 22 million daily customer interactions handled by contact centres is still handled by live agents (52%). Despite industry increasing the implementation of social media as a customer service channel, Share of Contact Handling by Social Media channels is 0.2%
2. Amongst organisations that offer social media as a channel for customer service, 67% report that the marketing department is responsible for managing it.
3. 63% of organisations in the study have only had social media as a channel for customer service implemented for 1 to 2 years.
4. Amongst organisations that currently have social media as a customer service channel only 29% reported their contact centre has the ability to escalate a social media query through to a customer support application that links through to an agent.
5. Past three months usage of social media as a customer service channel has doubled in the past 12 months (4% 2011; 8% 2012).
6. The proportion of consumers who believe they will be using social media more often in the future has also nearly doubled from 4% in 2011 to 7% in 2012. 
7. When asked whether they had received a response from an organisation via a Social Media network to comments they had made through Social Media, only 7% of consumers reported that they had. About 5% of consumers claim to have received essential information posted via a Social Media network. 14% of consumers report they have received information from an organisation via social media about new products and services. 

Smartphone Apps:

1. Amongst organisations that offer smartphone apps as a channel for customer service 50% report that the marketing department is responsible for managing it, with a further 33% reporting that IT is responsible.
2. 50% have only had smartphone apps as a channel for customer service implemented for one to two years, with 33% reporting smartphone app has been available for less than 12 months. 
3. Amongst organisations that do not currently offer smartphone app as a channel for customer service, 25% report they have no plans to. 
4. Further to the existing 8% of consumers who have used a smartphone app for customer service, a further 33% of consumers report that they are likely to use a smartphone app for a customer service enquiry in the next 12 months. 
5. Amongst Gen Y consumers, 29% report that they will be using smartphone apps for customer service issues more often in the next 1-2 years. This is significantly higher compared to Baby Boomer (8%) and Silent (4%) generations.