Intel Developer Blog: Softtalkblog offers some key advice for keeping your players engaged for the long-term
Successfully developing your Android app and finding an interested audience is often a milestone moment for any developer. However, this isn’t a time to rest on your laurels.
The next step is to ensure users stay engaged and using your app. It’s often difficult to keep users satisfied beyond that initial app install but it is important to consider their long-term interest.
What are the app traits you can avoid to ensure users install your apps and then keep them installed? Beware of:
• Lengthy forms: Asking a user who has just installed an app to fill out a lengthy, convoluted form contributes to a poor user experience, especially on a mobile device.
• Asking for ratings: Apps that intrusively push for good ratings tend to be uninstalled; ratings requests need to be timed carefully in order to avoid user burnout.
• Collecting unnecessary data: If an app is collecting personal data without a clear demonstrable need – or without consent – the app is more likely to be uninstalled.
• Buggy apps: If an app is full of glitches, eats up too much memory, or crashes all the time, it tends to be uninstalled. Users are rarely forgiving of these kinds of issues. Using the right development tools and being sure to repeatedly test an app on multiple devices and versions of Android can greatly reduce the number of issues users encounter.
• Unnecessary notifications: Sending unnecessary push notifications that merely create an improper noise to signal ratio are annoying. They need to be timed effectively so that they are not intrusive or too pushy.
Are you going to avoid these app pitfalls? What other pitfalls have you seen? Let us know in the comments below.
• This blog post is written by Softtalkblog, and is sponsored by the Intel Developer Zone, which helps you to develop, market and sell software and apps for prominent platforms and emerging technologies powered by Intel Architecture.
For the latest Intel Developer Blogs, click here.