Sunday 15 February 2015

From idea to chart-topper

app

The truth behind app development

What differentiates an also-ran app from an all-time great? Stuart Andrews speaks to the professional app developers to find out

Is developing an app still a route to riches? Done right, and with luck, the answer remains a resounding yes. Annual app sales now account for roughly $20 billion of revenue across the Apple and Google app stores, and Gartner predicts cumulative revenue will hit $77 billion (£51 billion) by 2017.

Meanwhile, both Facebook and Google are hungry when it comes to acquisitions: in the past few months, we’ve seen Facebook buy WhatsApp for $19 billion (£13 billion), while Google has gobbled up travel-app developer Jetpac and translation specialist Quest Visual for undisclosed sums. Undisclosed, but undoubtedly very high.


Yet the majority of app developers aren’t raking it in. A 2014 Gartner report claimed that less than 1% of apps were financially successful, while Midia Research found that only 50 companies were responsible for 81% of sales. It’s a market for superstars.

This doesn’t mean a new app can’t be a raging success, but it takes expertise, market knowledge, great ideas and hard graft. We spoke to a range of app developers, from freelance contractors to studios working with major brands. They told us how app development works in the real world, and what differentiates a success from another poor little orphan app.

SUCCES5 VS FAILURE


So, what differentiates a successful app from one that never makes It off the starting block? For one, the original idea plays a big part. Ben Paterson is creative producer at Figure Digital, developer of the virtual pet app, Animin. “Ideas for apps are ten a penny,” he said. “Everyone and their iDog down the pub has an idea for an app, and 99% of them are either rubbish, insane or completely undevelopable.”

It’s a view shared by Kevin King, founder of the Devon-based studio Createanet, which has a roster of successful apps that includes Temphis Availability Manager and the FA Coach’s App. “You get so many ‘sad birds’ instead of‘angry birds’ floating around,” he told us. “Because they didn’t have the creativity to start with, they don’t go anywhere.” It’s also no good trying to ape existing success stories: “We get two or three ideas a week where, once you drill down, they really just want to do Facebook. You can’t take on people like that.”

Successful apps are about satisfying needs, not inventing them. It doesn’t matter whether that need is a way to control a hot tub from a smartphone or enable property developers to keep on top of ongoing projects; as long as the app does something users want, and does it well, it has a chance of succeeding.

PRACTICAL HURDLES


A great idea also needs to be backed up by a business case. As Chris Williams, managing director of UK app studio B6o, puts it: “The first key step is to understand the business need and requirements. This is fundamental. Many apps fail because they have no real need, or the plan to make money from it isn’t thought through.”

Usability is just as crucial. Rob Hayward, a successful UK freelance app developer who has worked with Formula One and The Comedy Store, says you need to make it “effortlessly easy”. “You’ve got someone’s attention for a fraction of time, often a few spare seconds while they’re doing something else. They want a couple of taps and everything is done."

Williams thinks that a successful app “provides the features the end user needs while keeping the interface as clear, simple and easy to use as possible”. B6o pulls this off by understanding user habits mainly through a combination of in-house expertise, workflow analysis and client consultation, although it also sees value in focus groups and end-user research.

Mobile-development studio and marketing agency Rokk Media also spends a lengthy research phase looking at potential users, sorting them into personas and following those personas on a journey through the app. “We look at what they want to achieve and what their hopes and fears might be - particularly the fears, since understanding the concerns users might have can help you point them in the right direction,” said Martin Dainton, Rokk Media’s chief creative officer. When developing an app for internal use by the non-technical sales team of a car dealership, for example, Rokk ensured built in guidance and simple instructions were provided at every stage.

For Createanet, it’s a question of careful prototyping, so that the key interactions are in place before a single line of code is written - and then putting usability at the core of the design. “The beauty of apps is that they’re simplistic. You have to come up with an interface you can use with your thumb,” explained King. “They’re quite fickle. If you Find something and it engages you then you’re on board and that’s all about usability.”

Independent developer Nick Kuh would put usability ahead of even function. “I try to keep the UI as simple and uncluttered as possible,” he said. “I believe that a good app will focus on doing one thing really well rather than being feature-rich. Users are used to multitasking, so switching between apps that perform focused functions makes for a good experience in my book."

However, the biggest hurdle on the track to app success is how to stand out in such a crowded market. “My biggest obstacle these days is a saturated app store," said Kuh. “That, combined with competitors spending large advertising budgets on masses of paid-for installs, makes app store discovery very difficult.”

Figure Digital’s Paterson agreed, suggesting that “the biggest obstacle of all is getting the word out there and raising awareness, to find that community of about your app and have a chance to try it out.”

How? “We have a philosophy that great content finds its users,” said Paterson. “First, make something amazing. Second, find your advocates: those users who will effectively do your marketing and PR for you. Finally, continue to develop, tweak and innovate based on what these key advocates want.” Nick Kuh concurs: “Focus on making apps that will retain users. Enable your users to reach out to you, and listen to their feature requests and concerns. Continue to iterate and don’t give up on a good product.”

Finally, as Rokk Media’s Dainton explains, you need to acknowledge that the launch is the beginning, not the end. “You have to spend time marketing apps, nurturing and developing them, and when there’s a new release of the operating system - particularly with Apple - you’ve got to update them.” Not only will this keep the app fresh, but it will also ensure that Apple’s habit of cycling out deprecated code doesn’t leave you with an app that no longer functions.

THE PROCESS


All apps begin with an idea, whether it's promoting a brand or something truly groundbreaking. If you have technical skills, you might be able to develop that idea for yourself, but in most cases there'll be a need to find investment and partner with a professional developer or studio.

The development process tends to take a standard shape. First, there’s a pre-production phase, which may take in conceptualisation, user research and profiling, prototyping with wireframes or mock-ups, and the nailing down of a set of features, functions, specifications and requirements. The app then goes through a design phase, where those concepts are transformed into screens, buttons, menus and displays.

At this point, development begins in earnest, as servers are set up to support any back-end functions, and the different elements and features are coded. As with most software projects, there’ll be milestones, where limited alpha or beta releases or slices of the app are released internally and to the client for feedback. Bugs, issues and feedback will be spun back into development, hopefully producing a more polished and stable version 1 release.

When ready, the app is submitted to the relevant app stores. With Android, launch may be merely a few hours away. On iOS, however, you could be looking at a wait of up to two weeks as Apple vets the app. Only when Apple's gatekeepers are happy is it released, appearing on the App Store’s “Featured" pages if you're lucky, or joining the endless ranks if not.

INVESTED DEVELOPMENT


Unless you have the skills to design, code and test an app yourself, development doesn’t come cheap. “Some people expect to get an app developed for £150, and they can’t,” said Createanet’s King.

It’s possible to find solo developers who will tackle a project for a few hundred pounds, he explained, but warned that the archetypal bedroom whizz-kid “might be really good at the coding, but he won’t be so good at the design or the user experience side of things”. King went on: “If you can’t spend money on decent development, then you won’t get a company that will be around in a couple of months’ time to support you.”

In other words, apps need a budget, which may be anywhere between a few thousand pounds and hundreds of thousands. Even freelance app developers will look at the budget as a means of separating serious prospects from those without a realistic idea of what’s involved. “I get lots of enquiries,” said Jason Kneen, who develops iOS and Android apps through his studio, BouncingFish. “A lot of them are rubbish, to be honest. They want to do the next WhatsApp or Instagram and usually have no clue about how the whole process works or the costs involved.”

Having worked with the likes of English Heritage and Friends of the Earth, Kneen takes the ideas that interest him and sketches out the work involved, then uses that to form a ballpark budget. It’s at this point that those without a solid business plan back out.

Many would-be app tycoons also underestimate the costs of the back-end infrastructure that supports the app. “People look sites such as Instagram and Yo, and are unaware that alongside the front-end there’s back-end infrastructure in place,” said Kneen. “This needs to be paid for somehow. There are cloud services that will do this for free, up to a point, but when they start charging you when you hit a million users - you might suddenly receive a bill for $10,000.”

In addition there are design and technical challenges, from the difficulties inherent in building an app to work across multiple devices, resolutions and screen sizes, to issues concerning mobile connectivity and data flow'.

Perhaps the biggest challenge in app development is time. App projects often run on short two- or three-month cycles, with immovable deadlines such as Christmas or sporting events with which to contend. “Anything is possible, within reason," said Rob Hayward. “It’s just figuring out what you can achieve in the given amount of time." While there’s always a temptation to add more features, app developers learn to resist. “If there weren’t a limited amount of time, there wouldn’t be any restrictions,” Hayward said, “but when you’re delivering a product In three months, then extras need to do something vital - or at least tick a box with an investor."

In a world where the changing of a single button can often result in hours of work, testing can be a major time sink, one that benefits from someone dedicated to the job, according to Hayward. This will not only cut down on lead times when adding new features, but could also uncover issues that developers and designers fail to spot. “You could be focused on how' the design works, with different screen resolutions or languages, then a tester comes along, presses all the buttons in a different order, and finds something you wouldn’t normally find."

The submission process can also lead to delays. Kneen told us how' agencies often expect an app finished on Friday to go live on Monday. “I have to say that we can submit it on Monday, but it may be ten to 15 days before it can go live.” Apple sometimes rejects apps for peculiar reasons, and you may need to resubmit several times before this reason becomes clear.

One way to work with the time issue is to forget about cramming every last feature into version 1, and focus instead on producing a good, stable version that you can update. “You might get to a point where you have a fully functioning app, but with two missing features that the client wants to add," said Jason Kneen. “If they hold out they could miss a deadline, and there’s no shame in having a version l app that docs the job, then updating it two days later.”

Nick Kuh agrees this can be a viable approach, with developers “creating an MVP (minimum viable product), then iterating frequent app updates as they learn from their users and improve their product over time”. However, he also sounded a note of caution: “If you’re launching a brand-new app based on a great idea then you want your Initial offering to be polished at launch.”

Why? Because it’s at launch that the app might benefit from press coverage and establish a long term position in search results, while initial reviews will be more prominent and, in Kuh’s words, “more likely to sway new users”. “The better you make your app for launch," he argued, “the more chance you have of long-term success. Also, submitting a great first version to the App Store gives you your best shot at getting featured by Apple - the holy grail.”

WHICH PLATFORM?


According to the latest figures from app-market analyst App Annie, there are 60% more downloads from Google Play than the Apple App Store - yet the App Store makes 60% more revenue. Does that make iOS development a safer bet?

It depends. For some apps, the core purpose is to support the brand, increase online sales or support a product, in which case ignoring Android is risky. “Android has definitely caught up." said Rokk Media's Martin Dainton, “so the requirement tends to be that your app must work across the board. For some clients, this means we need to consider a framework that allows us to publish to different platforms, or they may need simply to develop different apps for those platforms."

However, as Createanet's Kevin King explains: “if you’re trialling something new - a new concept or a new idea - then my recommendation would always be to build iOS first. Make sure you're completely happy with it. go through the first two or three months of development and get the bugs and usability issues ironed out You'll then have a stable platform from which you can build in Android."

The ease with which you can go cross-platform boils down to your approach. You can code natively using Apple or Google’s development tools, then port the finished app to the other platform; or you can build within a framework such as PhoneGap or Appcelerator's Titanium, so that you can compile apps that run across both.

The first approach has some key advantages. “If you’re building something as a native app, then you definitely have more access to the device and its functionality," said Dainton. “If you're using a framework-such as PhoneGap, for example-then there’ll be limitations."

The upside of using a framework is that it speeds up development and makes supporting other platforms far quicker and easier. As Titanium user Jason Kneen explained, “90% of the work that has to be done will be applicable to both platforms, and the other 10% covers whatever I have to do to get it working on the other platform, which is usually Ul-related."

And what about Windows? Well, what about it? Most of the developers we spoke to said there was little to no interest in developing apps for Windows or Windows Phone. “There’s just no demand," said King. “It's chicken and egg. A few top apps are now on Windows, but there’s an app culture around Apple that just doesn’t exist in Windows."

“Clients don't seem to be that worried about Windows," said Dainton. “We ask them if they'd like to consider it, but it often isn't on their radar." B60’s Chris Williams agrees. “We have targeted Windows Phone devices, but it’s rare for this to be a viable prospect due to the relatively small userbase."

Will Microsoft’s unified Windows platform change this situation? Possibly- as might the growth in business-app development across tablets, phones and the desktop. At the moment, however, iOS and Android remain the focus of the app-development scene, even for those building business-focused apps.

THE BOTTOM LINE


Is all this effort worth it? Well, few app developers end up selling up to Facebook for several billion dollars, but all those we spoke to were sustaining a successful business. “There’s plenty of work out there," said Jason Kneen, who became a full-time freelance app developer in 2011 and has been busy ever since.

“It’s definitely possible to make a good living from app development if you combine the development of good indie apps with work-for-hire,” agreed Nick Kuh. “I’ve been developing solely for iOS since 2009, and five years on I’m still inundated with iOS projects and opportunities. I pride myself on the fact that every one of my own apps has earned enough through App Store sales to pay me back for the development time that I originally invested.”

What’s more, there are major opportunities in the enterprise sphere. “From our point of view, the biggest growth has been in business applications,” said Rokk Media’s Dainton. “People are starting to see that these devices are really useful on a business level. If they have satellite teams or those going into different areas and different departments, then apps really help with productivity.” It’s a market Createanet is also chasing in earnest. “You might not make the next Angry Birds, but you could sell a lot of product into a 2,000-seat business,” said Kevin King.

In short, the gold rush might be over, but it’s still possible to make a good living from app development, and keep your hopes of building a breakthrough app alive. It won’t be quick or easy, but then building a successful business rarely is.