As a product manager, how to conceive an APP?

"How to conceive an app", the more specific question should be "How to find a requirement and conceive a solution with an app product".

The specific strategy is to make bold assumptions and carefully verify them.

What is a bold assumption?

First of all, we must have a pair of eyes that are keenly aware of needs and pain points. By observing life and industry discovery, some people's pain points and some needs are not met.

If you find out, do you have an epiphany and think of some subversive solutions? If your idea is just "better", then I suggest you reconsider, or give up this field and look for other needs. You know, what can beat Rising antivirus is not better Rising antivirus, but free 360 antivirus; What can beat Nokia is not Nokia with higher pixels, faster camera and brighter shell, but an all-round revolutionary iPhone.

Well, now that you have found a real demand, and your idea is "different" rather than better, you can list this demand, existing pain points and your solution together. Then communicate with peers and peers in detail, and simply use common sense to verify.

At this time, you may find some subtle inappropriateness in your solution (if you don't feel this way, you may believe in yourself too much). Deep thinking, in fact, because it contains some assumptions, some unconfirmed assumptions.

For example, when conceiving the idea of Mo Mo, Tang Yan must have considered the following assumptions:

Young people (target group) have the need to know strangers.

Young people (target group) feel safe when they show their photos and other information to strangers.

Young people are more willing to communicate with strangers nearby and then dominate the relationship offline.

When Tang Yan thinks about these problems, he starts from himself, starting from himself. Assuming that these premises are confirmed, you can be a stranger.

How to check it carefully?

After you put forward some assumptions, you can do some small-scale interviews, directly find your target users and communicate directly. If your idea is verified, you can do a larger questionnaire survey.

Remember, at this moment, you should not deliberately guide users to favor your scheme, or take it for granted that your hypothesis is reality. Otherwise, in the end, until you make a product, you will find that the original assumption is not valid. Your so-called pain point is just itching, all you need is false demand.

If you can do this step seriously, the objective survey of the target population shows that more than 60% of the statistical results tend to your original ideas, which preliminarily verifies your hypothesis.

Then you can go to the next step and think about whether this product is best realized through an App solution:

Many people I have contacted want to make an App, no matter whether it is the best way to realize the product or the way of trial and error.

What kind of usage scenario is App suitable for?

Application environment with high performance requirements.

Requirements for starting and using high frequency.

Complex application of interactive logic.

Network requirements are low, or using App can greatly reduce traffic usage.

The cost of making an App is many times worse than that of making a mobile website. I saw someone say that they want to make an App to repair pipes and toilets, so the most obvious problem is the second one, an O2O App to repair pipes and toilets. I may not use it once a year, so why should I install an App that doesn't have to be launched more than once a year?

Now that various implementation schemes are so rich, WeChat official account can solve many problems. Why write an App on two platforms?

If you have questioned these questions and feel that you still need to make an App,

If you are the boss, consider the following:

Market analysis. Think about whether this market can support the growth of your products, who are the competitors in this market now, and from what aspects can your products cut into the edge of this market? After all, the success rate of the edge is 37%, while the success rate of frontal assault is only 6%. [ 1]

Business model. How will you profit from this product in the future? Do you want to think about whether you will fall into the ink weather cycle of "desperately being a user and finally not realizing it"?

Promotion. After you worked hard to release an App, if it didn't explode, then you only achieved 10% of this product. So how to promote it next? Is it a cute face that needs popularity to grow up, or is it a hard push to buy a beautiful group that users can generate value? So if it is the latter, is there enough money to promote this App? In the final analysis, it is the industry, this product, whether it is creativity-driven or capital-driven, and whether your team has enough relevant resources to complete this project.

If all the questions are clear, please concentrate on completing the first version of your App as soon as possible.

If you are a PM under the boss, you need to write a BRD (Business Requirements Document) to solve the above problems, and then convince him.

As for how to draw a prototype, first draw a sketch with paper, then use Axure to refine it, just interact, and don't engage in fancy high fidelity.