How to make a product from a mobile application
Make a mobile application is very simple. Making a good mobile app is more difficult. Creating a product from a mobile application is a more serious task. In the article I want to share some observations on how to achieve this.
Go!
The presence of user feedback indicates that someone is interested in your product. In the case of a mobile application, feedback can be called a review or rating in the app store, a comment on your website or an email with wishes and (more often) criticism.
For mobile applications, it is fair to say that people tend to post negative evaluations and reviews more often than write complimentary comments. This is normal, although for many newbies this is very daunting.
')
The situation with negative reviews is very similar to the work of Habr: no matter how ingenious the article, anyway, some group of readers will put a minus (at best), or write that article XXX is nonsense, and the author is an incompetent freak.
In general, the essence is simple: provide users with the easiest way to send you feedback. This may be the usual "send feedback" button; A pop-up window, say, once a week, which asks you to write a few lines, etc. The main thing is that the desire to receive feedback does not grow into a requirement for your users.
And yes, all emails need to be answered :-)
After the application is published in the store, many developers no longer take an active interest in what happens there, limiting themselves to a brief glance of the number of copies sold once a week.
In fact, you need to keep track of all available information - the number of downloads, the average time spent working with the application, the geography of users, etc. For these purposes, there are a large number of analytical tools that allow you to always keep your finger on the pulse.
Statistics itself does not matter much, but it can help to answer such important questions:
And in the context of comparing your application with the best (top apps) and similar (competitors) apps you can get answers to the following questions:
Of course, the application must perform some functionality. But really popular are those applications that enable the user not only to solve the problem, but also to make it convenient.
When developing our applications for each request for new functionality, we have a question: how to implement it so that the user is comfortable?
There are some simple tips:
Remember, the first advice was to listen to feedback. So, to listen - does not mean blindly perform.
The main principle of a mobile application is to do one thing, but better than anyone. Leave multi-tasking and multi-windowing to desktop clients.
Take for example Photoshop. Practice shows that the average user needs 3-5% of the functionality of a full-featured Photoshop. Therefore, Paint.NET for desktop and Lomogram for Windows Phone should be enough for the average user.
In simple terms, localize your applications. If the application is more or less popular, there will probably be volunteers who will want to help you translate the application. If there are no such volunteers - do not hesitate to ask about it on the website or in the application itself.
And yet, do not localize the application using google translate. It is better in any way than with him.
“And let's turn on push notifications for the application“ Non-boring wallpapers ”, integrate the application with all social networks, add geolocation and dating! After all, this is functional and cool, and the user will surely appreciate the new feature of the mobile SDK! ”- so many application creators think.
In fact, the end user doesn’t care deeply about the new SDKs, push notifications, or the super-mega-shader, if these “features” do not fit into the usual scenarios.
I would say this: when developing your mobile application, be guided by users who understand mobile phones and software like this:
Thanks for attention!
Go!
Feedback
The presence of user feedback indicates that someone is interested in your product. In the case of a mobile application, feedback can be called a review or rating in the app store, a comment on your website or an email with wishes and (more often) criticism.
For mobile applications, it is fair to say that people tend to post negative evaluations and reviews more often than write complimentary comments. This is normal, although for many newbies this is very daunting.
')
The situation with negative reviews is very similar to the work of Habr: no matter how ingenious the article, anyway, some group of readers will put a minus (at best), or write that article XXX is nonsense, and the author is an incompetent freak.
In general, the essence is simple: provide users with the easiest way to send you feedback. This may be the usual "send feedback" button; A pop-up window, say, once a week, which asks you to write a few lines, etc. The main thing is that the desire to receive feedback does not grow into a requirement for your users.
And yes, all emails need to be answered :-)
You need to know what is happening with your application (and not only)
After the application is published in the store, many developers no longer take an active interest in what happens there, limiting themselves to a brief glance of the number of copies sold once a week.
In fact, you need to keep track of all available information - the number of downloads, the average time spent working with the application, the geography of users, etc. For these purposes, there are a large number of analytical tools that allow you to always keep your finger on the pulse.
Statistics itself does not matter much, but it can help to answer such important questions:
- How did the update of the application affect the rating and the number of downloads?
- How has the average usage time of applications changed?
- The download and purchase curve is growing, falling, stable, and for how long does it already last?
- How do bugs, promo, weather conditions and marketing activities affect the purchase / download of the application?
And in the context of comparing your application with the best (top apps) and similar (competitors) apps you can get answers to the following questions:
- what applications are most often put in promo?
- What parameters (design, work speed, brand) most of all influence popularity?
- What are the average statistics for similar applications?
The focus is not on functionality, but on convenience.
Of course, the application must perform some functionality. But really popular are those applications that enable the user not only to solve the problem, but also to make it convenient.
When developing our applications for each request for new functionality, we have a question: how to implement it so that the user is comfortable?
There are some simple tips:
- page nesting - as little as possible;
- the number of clicks (actions) for any scenario is no more than four or five (kill feature is no more than two or three);
- emphasis on content, not design;
- less is better, but faster than more, but longer (this applies to downloading content).
Do not let users decide for you
Remember, the first advice was to listen to feedback. So, to listen - does not mean blindly perform.
The main principle of a mobile application is to do one thing, but better than anyone. Leave multi-tasking and multi-windowing to desktop clients.
Take for example Photoshop. Practice shows that the average user needs 3-5% of the functionality of a full-featured Photoshop. Therefore, Paint.NET for desktop and Lomogram for Windows Phone should be enough for the average user.
Talk to users in their own language
In simple terms, localize your applications. If the application is more or less popular, there will probably be volunteers who will want to help you translate the application. If there are no such volunteers - do not hesitate to ask about it on the website or in the application itself.
And yet, do not localize the application using google translate. It is better in any way than with him.
Think like a user, not a developer
“And let's turn on push notifications for the application“ Non-boring wallpapers ”, integrate the application with all social networks, add geolocation and dating! After all, this is functional and cool, and the user will surely appreciate the new feature of the mobile SDK! ”- so many application creators think.
In fact, the end user doesn’t care deeply about the new SDKs, push notifications, or the super-mega-shader, if these “features” do not fit into the usual scenarios.
Write the code as if it would be accompanied by a violent psychopath who knows where you live.
I would say this: when developing your mobile application, be guided by users who understand mobile phones and software like this:
Thanks for attention!
Source: https://habr.com/ru/post/162251/
All Articles