By which method to remind users to update

Mobile Internet version update is a very important thing, because unlike the web can be deployed at any time, users need to click on the "update" in order to enjoy the latest service you provide. So how to remind users to update the application? How to design to attract users to update it?

Remind users to update the methods are: store reminder; application pop-up reminder; push reminder; The following for everyone one by one, I hope we can help.

First, the store reminded

Everyone knows that apps should be submitted to the store when the new version is released, and commits to the store is often a copy of something new about the version. Before there has been a lot of user feedback that update copy of these stores are never seen, so a large number of "update obsessive-compulsive disorder" patients tend to see all the updates on the bubble. Originally wanted to find the relevant data for this problem to find the ratio but did not find, but I believe there must be a lot of people like me to install a large number of applications, each update is a vast project, so I often first AppStore Look at this version of what have been updated, will choose whether to update. And since each store offers a new version of copywriting and is the easiest and most immediate place to remind users of an updated version, we should take it easy and think of how to write these updated copywriting:

(iTunes update copy shows the location)

(AppStore and GooglePlay update copy location)

So, how to write such a small store update copy? First of all, you have to remember that in any case, the purpose of your copywriting is to attract users to update, if you do not achieve the purpose of attracting users, it is better not to write.

1, what to write? What should not write?

The user's attention is valuable, if you really appreciate your updated copy, then it must be to obtain valid information. So you should try to highlight the new features, if only some simple improvements, or modify the program copy typo things like the very details is not necessary to write out. In addition, bug fixes can actually be written, but be sure to write meaningful fixes. For example, before a serious bug caused a lot of problems for users, then you write to solve this problem must let these users are very pleased.

2, stand from the user's point of view

There are a lot of people writing update copy, are standing on the point of view of their own products to write, or write in accordance with the realization of the model point of view. such as:

"Add message to share business information function"

This sentence is very much like the requirements in the requirements document or iterative planning tasks, first of all, users do not understand the meaning of this sentence, followed by absolutely no point to attract users. If you want to attract users, be sure to tell your new features to the user what kind of benefits, or to help users solve any problems. So according to this idea will just copy into:

"You can use SMS to share your business information with your friends."

This way, users not only understand this function, but also know the benefits of this feature for him.

When writing a copy, if you want to change from an implementation model to a mental model, you can try to use the subject from the beginning, such as:

1) You can ...

2) You can ...

3) Solved the problem of ...

And less use:

1) Add ...

2) Support ...

See above Sogou FM and WeChat though can read what the new function is, but standing in the emotional point of view I think it is not perfect.

3, organized

1) When writing update copy must be organized, do not mix all the descriptions into a large section;

2) because the user is basically glanced at the update copy, find the information in the text useful to him;

3) Therefore, when writing a copy, try to use "1, 2, 3, 4" to separate the information like I do;

4, appropriate modification

Often see some applications will use the five-pointed star, love symbols as delimiters, or do not forget to add a smiling face in the final expression. Some people may find it superfluous, but in fact doing so will not only highlight your product's eye-catching, but also give users a lively feeling of enthusiasm throughout the updated list.

(Honeycomb update copy, can not say perfect but has been considered better than the other)

Finally, a few friends added that their updated copy was written by the operator. I strongly recommend that this copy should be given to the interaction design or the PM because they often know what the original intention of doing this is. Find out what kind of sore that the new feature brings to the user or solves it. If the UE or PM writing skills is not good, you can write a draft, and then let a professional person to process ~

Second, the application of pop-up window to remind

In-app pop-up reminder, means open the app directly through the pop-up window to tell the user a new version. The benefits of doing so is that users can see when using the product, targeted. Bad place may suddenly block the user's operation, causing uncomfortable to the user experience it. So to do this kind of reminder is also a risk, to meet a few principles:

1, necessity

Unlike store update copywriting, because it's an in-app interaction, it's completely flexible and does not need to be prompted for every newer version. Because of this hint will block the user's operation, so that users uncomfortable, it should ensure that this version is very necessary to remind users, only pop-up reminder. Some pure bug fix version, submitted to the store can, but no need pop-up.

2, just focus

And stores are not the same, pop-up display text is relatively small, no way to list the new features one by one. So you should only highlight the focus, streamline the text, or just one of the most important new version features. For example, like the WeChat if you want to update the pop-up window can be designed to:

3, there must be mandatory updates

Do not know if you have a mandatory update mechanism for the product, if it is an experienced PM, it will certainly require the application must have a mandatory update mechanism. Mandatory updates are intended to prevent unexpected occurrences, release of a version that could result in a major incident, or a serious conflict between the old version and the new version. So in some cases, you need to consider a scene that requires all users must be updated, or the old version can not continue to use. This mechanism should be taken into account in the first version of the product, otherwise the problem is irreparable.

Because the update through the store is not so-called forced update, so only through the pop-up window to remind. Forced updates to popups often have only one option to update or close the application.

4, allowing users to ignore

Often the pop-up reminder is very annoying, and many designs will be made to open the application reminded once, then if you can not ignore, let the user is uncomfortable. Allow users to ignore the reminder there are 2 ways, one is the pop-up window to remind only when the new version first pops up, there is a pop-up window on the "ignore this version of" option, click on this version no longer Reminded.

This will satisfy the user's express desire to "know, but I do not want to update."

Third, push reminders

It's rare to remind users of updated versions by push, because push is just a snap, and you can not jump directly into the AppStore after clicking. However, the use of push can be very flexible, through the use of manual hair push method, activation has not been used for a long time and has not been updated for a long time the user is still very effective, the meaning of the performance is probably:

"You have not seen me for a long time, recently I have a lot of fun new features, come and update it ~"

However, we must pay attention to Oh, we must make a statistics of those who lost users and low active users, targeted to go, because you can not remind all users to update it.