You can't even catch bugs, what's the sense of participation?

The woods are big and all the birds are there, so is the app market. For example, there has been a period of time the image of the development of the blowout, all kinds of pictures social apps flooded the market. Many examples of short-lived apps are "come fast" and "you Sing to Me", with apps that focus on image processing or social elements. The reason, in addition to market saturation and other objective factors, more or some enterprises and developers anxious, envious market, to build a sense of participation as an excuse to put untested swaddling app into the market, the results exposed a variety of bugs, eventually evolved into the user's slot assembly.

Xiaomi Bible "Participation Feeling" a book on the Internet users thinking of reputation as Wang, focus on promoting participatory marketing, put forward to build a sense of participation in three strategies: to do explosive products, fans, do from the media; three tactics: Open participation node, design interaction mode, diffusion of word of mouth event; domineering is called "participatory" 33 law, The analysis of market development and consumer demand is profound and unique, and Xiaomi's success is benefiting from this. But if you can't catch a bug, talk about the sense of participation.

Building a sense of participation and engaging customers in the construction of products and services does not mean that the customer is obligated to make improvements to the bug, take the user's feedback and even let the user see jokes. Some entrepreneurs have developed an app that is impatient to build a sense of user engagement, the name of the United States: open to participate in the node; will not be strictly beta products on-line, fantasy through the UGC community to gather fans, rely on users to find and fix bugs; This "flaw"-like distorted participatory marketing is bullying. This is like late at night, you plump belly run downstairs to buy bubble noodles, hunger and unbearable open but found there is no seasoning bag, so you will never want to buy this brand of bubble noodles.

Open participation node refers to the process of making products or services open, screening out the benefits of both enterprises and users of the node, the mutual benefit of participation in the interaction can be sustainable. Open nodes should be based on functional requirements, where the more you need to participate in the more people, let users go to the imagination and you always have to down-to-earth. An app in the context of the existing full-featured users, users in the process of the use of divergent thinking, the new demand and desire to feedback to the developers, so as to participate in product development and operation and other links, so that everyone becomes Product manager, constantly refresh and enlarge each user in the product development and operation of the sense of existence, Finally realize the common growth of users and brands. This is the true meaning of the sense of engagement.

The same bubble surface example, you launch spicy bubble noodles widely loved by consumers, users also hope that your family can make three umami, he will be very enthusiastic to express their needs, you need to do is to cherish every communication with the user, the end of the enterprise and users together "pregnant" out of the three umami bubble surface, while the user also promoted to your favor. Millet 4 years of development miracle is also relying on high-quality MIUI ROM to complete the accumulation of fans, this is the right logic of participation, this is the right way to open a box of bubble surface.

However, even if we all understand the above, but we still see a lot of app hurt online. The reason, in addition to "not fine," is also related to the app testing industry pain points. According to the past experience of the app industry, product quality control or product on-line testing, whether in large companies or small and medium-sized developers in the team is a soft rib, which is mainly affected by two aspects of the objective factor constraints: 1, the figure to save money-enterprises do not want to specifically raise Test team or engineers, development test a nest; 2 -There are not enough end-devices in the team for testing, the sample capacity is small, the sub-critical. In addition, there are enterprises in pursuit of the first advantage will be the product hastily on-line and deliberately create a sense of participation, the user intimate to help you find the bug ... Eventually it turns into a company that throws a bunch of irresponsible rubbish to the user, and the user throws the rubbish into the trash. You always have to come out and mix.

Since testing is so tricky and so important, how can the small and medium teams solve it? You know, one of the essential differences between humans and animals is the use of tools, so here we recommend a beta tool called pre.im, which is quick and easy to use. Once the app is uploaded, the developer can distribute the app to the user's hands with a QR code or a short link. In addition, embedded in the Beta SDK, the user shakes a shake to automatically feedback bugs and suggestions within the app, and is completely free. Through this means, in particular, to please the SMEs and start-ups and other seed users, but also a good solution to the needs of developers pain points.

In a word, for the current app industry to ignore the test troubled waters phenomenon, whether intentionally or helpless, enterprises and developers should change the concept, set up a sense of testing. Clearly see that rigorous testing of app science must never be missed. Life three big embarrassing bubble noodles no material, can't endure, the app has bug, also can't endure. If a startup team doesn't guarantee the quality of its own application, what qualifies your users to be more involved in improving your application? Want to play with millet participation, testin teach you to participate in the sense of playing out flowers.

You can't even catch bugs, what's the sense of participation?