Google + topics discuss sharing: applying fast iterations (Agile mode) and user not upgrading

Article Description: when the mobile application "Agile iterations" encounters "user does not upgrade".

One night at Google + to participate in a discussion of the topic, afterwards feel that the topic is valuable, then continue to do thinking. By the way the contents of the stream in the end of the text to stay to backup, convenient precipitation, you can continue to participate in the exchange of discussions.

app Upgrade Habit Survey is the source of this discussion, a series of thoughts and analyses that arise from the conflict between fast iterative upgrades of mobile applications and user neglect or not upgrading applications.

According to this topic, I have also done some extension of thinking.

In the development of mobile applications, the application of rapid iterations (Agile mode) and the user does not upgrade the application is really contradictory? Does the user not upgrade cause the product to fail? is rapid iteration not suitable for mobile application development? As the article said: "The more you do behind the strong fart use Ah, people do not upgrade." The first impression determines the fate of the product. ”

Is that so?

In fact, after careful thought, but relieved, this is a riding on the boat's conclusion, the beginning of the subject to ignore, the product behind the more stronger?

No matter what the product, the most essential is to solve the needs of users, mobile applications is a mobile terminal to provide a new form of demand solutions. So the essence of this application to meet what needs, and to address this need to solve the way, and ultimately face the user is what we often say the quality of the product . thereby affecting the user's cognition, acceptance, use, trust, love and affection.

Let's start with a quick iteration, a quick iteration does not mean that the product gives up the quality it deserves, and that by slowly upgrading it, that is, even the 1.0 version of the application, it should have a complete model of the need to solve this, attention, is complete, not perfect. If a product, application at the beginning did not let users understand its value, the beginning of a failure.

Rapid iteration and release is just a concept and thinking of research and development, emphasizing quick response and continuous improvement of product quality, which should be well validated in the application of BS. I think it is the service end of this application of the iterative mode, rapid iteration can always firmly grasp the quality of service in their own hands, now mobile terminal application is the client mode, relying on upgrades, only the author of that time to think about it.

In a sense, the initial version of an application represents the value of the application, if this is not done at the beginning of the release, failure to its own, there is nothing to say.

Of course, why users still keep this application in the terminal, the reasons for various, mobile terminal user behavior is indeed an interesting research topic.

As for the development of the product and the future, the most essential is the product itself, and the user upgrades or not necessarily link. So the product success or failure, and agile iterations, regardless of the user does not upgrade.

A classic example is the IE6 browser.

Of course, Android, iphone app developers are worth the effort to reduce the cost of user upgrades, or to boot, such as upgrade reminders.

But then again, if the user feels that the application is valuable, willing to stay at their terminals, and use, this is considered the first step of success (not including that temporary not unsightly, too lazy to delete)

At least to show that your application cover needs to meet the needs of users, as to whether the daily upgrade, is not an immediate upgrade, this is not the key, I think that the six-year upgrade of users, many are the App Store upgrade mode, as well as many upgrades experience and experience, education, Friends with the iphone should be aware that most of the applications are being changed by minor features, Bugfix, and frequently released versions. Once the experience is established, it is clearly reasonable and sensible for the user to upgrade once a year. This upgrade of the status quo, is indeed the cost of the user upgrades far higher than the benefits, time and time can, many users will not stand, especially installed a lot of users, although these applications are at the same time in the user's terminal, but the user's value and dependence on the application of the degree of 359. So this escalation behavior, the author describes the situation, people have different, but generally not too diligent, it is too normal. Just like you let someone one day impromptu sing a red song also can, let him sing every day only when the cure.

Some times, is our product person's custom, has detached from the ordinary user behavior, is not normal even a bit morbid.

So most of the recruitment situation, for product control and geek, there is a complex emotion, that is, love and worry about a thing drilled very deep, particularly passionate, but particularly easy to go to the point, the simple problem complex, but not realize the pain and suffering of ordinary users.

Okay, a little off, so, do mobile terminal application of students, do not put the problem of the product to the user's problem, the product's core experience, should not rely on upgrading to solve, do not expect users to wait 3 seconds, wait for the next version to get the desired (this is the need, not a user of a functional requirements, Users often have a vague and even wrong demand for their own needs.

Agile advocated by the continuous optimization of product quality, when the user's basic needs to meet, access to the user's favor, after acceptance, iterative upgrade is the product how to make users more like, more rely on, and gradually deepen the positive experience of products effective way.

Or that sentence, really good things, everyone rob to, really important phone, Miss once will call again.

Finally, without affecting the user's core needs to meet the premise that the user is tolerant, or cruel. The former will continue to use this imperfect but problem-solving product, the latter may uninstall the deletion directly and scold away. The more popular products, the more the more the worse, you can refer to bit. Every product in this situation is actually facing. Because each user's requirements for the product are very different.

The following is a partial excerpt from the topic discussion: Because it is based on the open impromptu discussion of the flow, just pick and the topic of close relationship ...

Junyu Wang -Public

The question is a little shallow. The nature of the problem is that the user will balance ROI when make decision. Get the benefits of the upgrade, pay the cost of the upgrade operation. To get users to upgrade, either increase the benefits or reduce the cost.
From experience, reducing costs is easier to motivate users to upgrade. For example, Chrome, such as pea pods (not low enough).
The Android electronics market allows for automatic upgrades, it feels great, apps are always up to date, and you don't need to spend time maintaining them. IOS is very sad.

Jary Xie -This topic is quite interesting, upgrade the most essential or depends on the user's income, the threshold level of the results have impact, but not the key, this is the App Store upgrade experience is not good, users are happy to upgrade the reason, the key depends on the intensity of the income stimulation, Of course not ruled out many small white users do not understand the iphone can also upgrade the matter. However, for application developers, improve the value of their products is the core, in the product value is constant, under the premise of reducing the upgrade threshold will promote upgrades.

Huiwen Ji -reducing costs is just a stepping stone to the back of the door people perceive the obvious benefits of follow-up as positive reinforcement, so the next time the user's ROI expectancy will be promoted.

Junyu Wang -If the cost is 0, then there is no problem. Android Automatic upgrade is a lot of transfer costs, to guide users to open this function is also to have cost, but because it is batch, the return is relatively high. If silently automatically open, out of the question, in the future will have a conflict.

Jary Xie -even if the threshold is 0, I will also choose to upgrade the revenue expectations, will not upgrade their own value of mediocre applications, and may be ready to delete, upgrade is the cost of traffic and time costs, for example, if the front of the chrome and the World window browser, The former has the threshold I also can upgrade, the latter does not matter anyway. This is related to the user's value expectations. Many of the applications in the mobile phone in the latter position, of course, if the latter, upgrade the threshold is still high, it is finished. Automatic batch upgrade pros and cons, the app store focused on the quality of the application, upgrade is the ecological link, need to be specific trade-offs.

Chris Lau Cattle -if the electronic market automatically upgrades by default select WiFi upgrade on it. Or click on all upgrades are very low cost. For many users Ping said, will think that the new version at least no worse than the old version, 360 do not cultivate a lot of upgrade control it.

Jary Xie -in fact, the goal around the escalation discussion is easy to deviate from the target, as application developers, the user's continuing needs is the first problem.

Chris Lau Cattle -If an automatic upgrade is made, it is likely that upgrades will appear to ask for software, but automatic upgrades can also solve this question. 1.0 Stability 1.1 problems, then quickly out 1.2 fix the problem.

Arsalan Ma -When the Software pop-up window says, hey, we're ready for the X.X.XXX upgrade, you click on the following update Oh, Pro.
If it is Google or a similar background, blood of the software, I will point down;
If it is thunder, Storm, 360 or similar background software, I will uninstall it;
Pea pods are a special case, as the recent updates have not brought any operational improvements, his resource base is becoming bloated, the search is getting harder, and the new xt882/870 phone is automatically closed when it connects.

Zhou 007 -a group of Googles have a great influence on the appreciation of pea pods, trusting googlers and trusting pea pods.

Eric Levison -but with a pea clip and a whole bunch of apps upgraded, the average user doesn't open each application to see what's going on.

Cong Li -I would advise software developers to give a hint to the user's first run of an automatically upgraded software interface, outlining which major features were added to the upgrade or fixing bugs, just like Google Maps after the upgrade.

Liu Bobby -Roi. To be honest, I never know what some upgrades are for. "This upgrade solves the XX security vulnerability"--who knows what it means except pro? Upgrade does not upgrade anyway is only to see the convenience is not easy. I think the worst example is Acrobat Reader, which checks for updates every time it is opened, but turns off Acrobat reader when updating. But when you open the reader, it is usually a time to read, so.