You’ve launched your app and it’s doing well. You worked hard, kept your initial features lean, and all of your effort has resulted in an app that users like and recommend to friends. So, how do you maintain that momentum and ensure that your app keeps gaining in popularity?
This article covers some practical approaches to keeping users interested in and using your app, including talking to your users, keep on launching features, making the first impression count and using all functionalities of the operating system.
Get Talking To Your Users
According to a survey conducted by Google and Ipsos MediaCT, the top three reasons why users abandon an app are lack of interest, change in user needs and simply lack of usefulness. But usefulness, necessity and interestingness are subjective and change over time — what you think your users need or like isn’t always accurate. So it’s important to start a dialog with your users.
When everything is similar, being different attracts. Meet Art Direction For The Web, our new book on designing and building compelling, outstanding experiences. Inspired by vintage print magazines, with code snippets for your work.Jump to table of contents ↬
We’ve found that the best long-term approach is to foster a “VIP” beta-testing community. These beta-testing communities help us understand user needs, even as they change and adapt. These beta testers, in return, get early access to new features and have an opportunity to help shape the application, making them feel like VIPs and often turning them into advocates for the application as a result. We typically use the Play store’s beta distribution channel and a Google+ community for this purpose. This distribution channel enables users to receive app updates via the Play store as normal, but from the beta release group. The Google+ community acts as a place to leave comments and bug reports, and access to the channel can be restricted.
Creating your own beta-testing community is simple. First, find the first few people who have rated your app lower than you’d like or who are particularly vocal about its design, and engage them in a dialog. Treat their complaints and concerns sincerely, and recognize that they’ve spent time trying out your application. If they’re open to the idea, ask them to join your beta-testing community, and, where possible, ensure that your subsequent releases address their concerns specifically. When you do so, let them know and thank them for their help. You’ll find that these users go from being critics to advocates.
CCleaner for Android, an application published by Piriform, is one such application for which we took this approach. Within 18 months, it grew to over 15 million downloads, and the beta-testing group grew to 10,000 people. The people in this testing group have become advocates whose opinions help shape the app’s next features, keeping it useful and up to date with users’ needs. This beta group is very large. When setting up your own, try to keep it to a number that will allow you to respond to queries and bug reports, while still leaving you time to work on new features.
If you’ve kept your first launch lean, you should have a backlog of features that you’d have loved to put in the product but sensibly didn’t. Keep that version 1.1 lean, too, and assume that half of the effort that goes into it will be bug fixes, but get it out sooner than later.
Aim to update your application regularly, and get users used to (and excited about) these updates. This regular update rhythm will both act as a good personal motivator as well as teach users to expect timely, interesting updates. Companies such as Spotify make these regular releases a part of their engineering culture, creating a “release train” that leaves the station every two weeks. Features that are not completed in time for the next train are shipped as part of the release but are deactivated and unseen by user.
There are a number of tools you should consider adopting when attempting to decrease the time between your app’s updates.
Automated testing is the most important. A continuous integration server, such as Jenkins, can be used to automatically run tests on features and changes that you’ve made to the code as you work, ensuring that you never code yourself into a corner. Knowing that your updates and changes haven’t caused a new bug or broken an older feature means you shouldn’t ever have to waste time “doubling back” over old code.
An issue tracker is a good tool for prioritizing your workflow and maximizing the value you send out with each update. JIRA is a one such tool used by many large teams, while Trello is a good alternative for lone developers. Both tools allow you to create issues (or cards) that you can use to monitor your backlog. This helps you to plan and organize releases with minimal hassle and keep your administrative overhead to a minimum.
If you’re using Git, then another practical method of managing this selective integration of new features in time for a release is the Gitflow workflow. This workflow keeps code branches for new features separate from the main code base. When it’s time to create a release, these code branches can then be selectively merged back into the main code base.
Make That First Impression Count
According to a survey conducted by Quettra, on average 77% of users no longer actively engage with an app after just one week. If you want your app to keep engaging users and stay popular, then making a good impression in those first few days after installation is vital.
As an app developer, your aim, therefore, should be to highlight the app’s usefulness to new users in the first week after installation. A good onboarding process that highlights the app’s functionality is vital. Where possible, this onboarding should walk users through a real use case or show real data to best impress upon them the purpose of the application.
This can be a challenge in some cases, such as when the app’s content is behind a paywall or when its content is populated entirely through user action. In the case of “The Sun”, one of the world’s largest English-language newspapers, we worked with the company’s designers and API developers to ensure that the onboarding process contained real, timely data (in this case, football scores and recent headlines).