7 not the most common problems of mobile applications and how to solve them

The Appodeal company blog has already published articles about problems with mobile applications. One of these articles told about the reasons for which the user may decide to remove your program. We decided to continue this topic, but from the technical side.

Immediately it is worth mentioning that most often inexperienced developers do not provide for two things: a security system for the application and additional server resources in case of popularity growth (ordering pizza, choosing clothes, searching for a restaurant, etc.). We will talk about all this today. Note that the article deals with “connected” applications - with its own server, database, dynamic content and other attributes.

Problem: application performance drops as user base grows

If users ten, one hundred, one thousand, the problem can not be noticed. But if the bill has already gone to tens of thousands? The application may already be hanging for a long time, issuing the information requested by the user late.
')
Solving the problem: you need to improve performance; you can do this, for example, by converting mobile user requests into regular requests that receive content “on the go” in response. In addition, some data can be cached, and not dynamically output for each user each time (for example, the number of comments).

Problem: large objects in the database

Saving images and other heavy objects in the database results in poor application performance. This is especially pronounced with the growth of the user audience.
Problem Solving: Avoid storing massive sets of binary data in this form. Plus, consider deleting data that no one will request for a long time.

Problem: DDoS Himself

As an example, we can take the case when the developer plans to introduce a new function of the application and notifies all users of the program. This can lead to a huge load on the server, as a result of which it will simply cease to function normally.

Solution of the problem: divide your users into groups and send notifications to each group sequentially, and not to all at once. This will provide all users with an update, but the server load will not be excessive.

This way of notifying users will help to better track the effectiveness of feedback, as well as marketing campaigns, if you conduct them (sales, gifts, discounts, etc.).

Problem: users notice application errors

Popularity is good. But if the application has already received a large user base, it may happen that when working with the program they will begin to encounter various problems and software errors. For example, it could be a timeout of the north, resetting the connection or resetting the update (as happened recently with the software of one popular corporation).

Solution of the problem: it is necessary to provide it at the very beginning, before you get a large user base. It is worth analyzing what can happen if a user starts writing a long review, and the connection is suddenly dropped. Or if the user tries to register in the application, and the registration confirmation is delayed, and not for a minute or two, but for a long time.

Try to think over most of these problems at the design stage of the application. Add the ability to authorize users through third-party services.

Problem: there are too many ads in the application

Some developers are trying to get as much money as possible, monetize the application to the maximum. As a result, the program is equipped with pop-up banners and regular banners, plus offers to buy something. All this annoys the user.

Problem solving: application monetization should be approached wisely, using original ideas and new methods (for example, native advertising ). If you have problems with monetization, try registering with Appodeal , and we will help raise the yield on each position. Maybe after that you decide to turn off some advertising for the sake of users.

Problem: Security as a matter of primary importance

Many companies and startups do not provide reliable security measures for their products. As a result, users' data is at risk - they can be “led off” without any special problems, there would be a desire.

Problem solving : Servers with database and API must be kept up to date by regularly updating individual software components. This is not always an easy task, so you need to plan technical activities in advance.

• Do not use passwords to access remote servers, it is better to use SSH instead.
• Restrict access to the database, instead it’s better to use SSH.
• Document planned and implemented security measures. Make sure that the measures you take will really ensure the security of the data and the application itself.
• Store public, private, and protected data separately, using different access levels for each data group.
• Hash and "solite" your passwords, encrypt users' personal data such as phone numbers, or do not save them if this is not necessary.
• Give users the ability to delete their data from the system.

Problem: the application is removed immediately after installation, even without going into it

Your program may be the result of the implementation of a good idea, but not all users are convinced of the need to use it. Sometimes users don't like the app. Simply do not like it.

Solution of the problem: we described this problem in sufficient detail in the last publication .

As a conclusion : In general, such problems can be foreseen at the design stage of your application. If a rational approach to development, it is right to plan and implement everything, then difficulties, at least similar ones, will not appear. In the meantime, we wish you a maximum of users and a minimum of problems.