Product design: How to remind users to update applications?

Many designers in the main function of the product design completed, everything is only owed to the east wind, often ignore the design of the product update mechanism. In fact, mobile Internet version update is a very important thing, because it is not like the Web can be deployed at any time, users need to click "Update" to enjoy the latest services you provide. So how to remind users to update the application? How to design to attract user updates?

To remind users of the updated methods are: Store reminders, the application of the window to remind, push reminders, the following will be introduced.

One, the store reminded

Everyone knows that when the application is released to the new version of the store, and the submission store is often to write some of this version of the new features such as copy. There has been a lot of user feedback that the store's updated copy is never read, there are a large number of "update obsessive-compulsive disorder" patients are often seen bubbles on the full update. I was going to look for the relevant data to check the ratio, but I didn't find it. But I believe there must be a lot of people like me who have installed a lot of apps, and every update is a huge project, so I will always be in the app Store to see what this version is updated before I choose whether to update it. And since each store offers a new version of Copywriting, and the simplest and most straightforward way to alert users to newer versions, we should treat them well and think about how to write these updates:

(The location that itunes updates the copy to show)

(Location of the updated copy of the App Store and GooglePlay)

So how should this little shop update the copy? First of all, you have to remember, anyway, that the purpose of your writing is to attract users to update, if you do not achieve the purpose of attracting users, you might as well not write.

1, what should be written?

The user's attention is valuable, if you really have the honor to see your update copy, then must be to obtain valid information. So you should try to highlight the new features, if only some simple small improvements, or modify the program copy typos and so on the very details of the things are completely unnecessary to write out. In addition, bug fixes can also be written, but be sure to write meaningful fixes. For example, before a serious bug to many users caused a problem, then you write this back to solve this issue will certainly make these users very happy.

2, standing in the user's perspective to write

A lot of people write updated copy, are standing in the perspective of their products to write, or according to the perspective of the implementation model to write. Like what:

"Add SMS to share merchant information"

This sentence is very much like the requirements of the requirements in the document or the task of the iteration plan, first of all, users do not understand the meaning of this sentence, and then there is no point to attract users. If you want to attract users, be sure to tell you what the new features bring to the user, or help the user solve the problem. So if you follow this idea to change the copy you just made:

"You can use SMS to share information about a merchant with your friends."

This allows the user not only to understand the function, but also to know the benefits of this feature.

When writing a copy, if you want to change from an implementation model to a mental model, try starting with a subject, such as multiple use:

1. You can ...

2. Can you ...

3) solved the ... The problem

and less use:

1) New ...

2) Support ...

The Sogou FM and micro-letter read above can understand what the new function is, but I don't think it is perfect to stand in the angle of the words emotion.

3, organized

1 Write update copy must be organized, do not make all the description of a large section;

2 because the user is looking at the update copy of the time is also basically scanning, in the text to find the information useful to him;

3 So when writing a copy, try to use "1,2,3,4" to divide the information, such as I do;

4, the appropriate modification

Often see some applications will use the pentagram, love symbol as a separator, or do not forget to add a smiley face at the end. Some people may feel superfluous, but in fact doing so will not only highlight your product in the entire update list, but also give users a lively and enthusiastic feeling.

(The hive's updated copy, not to say perfect but it's better than the others)

Finally, some friends say that their updated copy is written by the operator. I strongly recommend that the copy be given to the interactive design or PM, because they often know what the original purpose of the function was, and also understand what kind of satisfaction or pain the new feature brings to the user. If the UE or PM text is not good, you can write a draft, and then let professional people to processing ~

Second, the application of the window to remind

Application of the window to remind, is to open the application of the window directly through the way to tell the user has a new version. The advantage of this is that users can see when they use the product, targeted. A bad place might be to suddenly block the user's operation and create an uncomfortable experience for the user. So it is risky to do this kind of reminders, to meet several principles:

1, necessity

and store update copy is different, because it is in the application of the interaction, so you can flexibly handle, do not need to update the version every time need to be prompted. Because this hint will block the user's operation, make the user uncomfortable, so you should ensure that this version is necessary to remind users, only the window to remind. Some pure bug fix version, submitted to the store can, but no need to play the window.

2, just the point.

And the store is not the same, the window display less text, there is no way to list the new features. So you should just focus, thin text, or just one of the most important new version features. such as the above micro-letter if you want to update the window, you can design:

3, to have a mandatory update

I do not know whether your products have mandatory update mechanism, if it is an experienced PM, it will require the application must have mandatory update mechanism. Mandatory updates are intended to prevent unexpected situations, release versions that cause major accidents, or situations where there is a serious conflict between the old version and the new version. So in some cases, you need to consider a scenario where all users must be updated, or the old version will not continue to be used. This mechanism is to be considered in the first version of the product, otherwise there will be irreparable problems.

Because there is no such thing as a forced update through a store update, it can only be reminded by the way the window is played. Forced to update the window, there is often only one option to update otherwise off application.

4, allow users to ignore

Usually the window warning is very disturbing, and many of the design will be made to open the application of the time to remind, then if you can not ignore, let the user is difficult to suffer. There are 2 ways to allow users to ignore reminders, one is the pop-up reminder only when a new version is first entered, there is a "ignore this version" option on the window, and after clicking this version is no longer a reminder.

This will satisfy the user express a "know, but I do not want to update" appeal.

Three, push reminders

By sending a push to remind users of the newer version is relatively rare, because the push is only for a moment, also can not click to jump directly into the App store. However, the use of push can be very flexible, through the use of manual delivery method, activated for a long time did not use and has not been updated for a long time the user is very effective, presumably can be performed means:

"You haven't looked at me for a long time, I have a lot of fun new features recently Oh, come on update it ~"

But pay attention to Oh, must count the loss of users and low active users, targeted to send, because you can not remind all the user update it.

Above is the update mechanism that I often use in the project, if everybody has better welcome to add and discuss!