Before reading this article, you can take a look at “Developing a wechat Applet from Scratch (Zero) — The Beginning”.
The requirements and prototyping phase determines what a product will look like and largely determines the fate of the product. In this stage, scattered demand points are excavated and sorted out, and feasible requirements are selected after consideration in the commercial sense. Then these requirements are integrated into a standardized document form, so as to unify the understanding and expectation of requirements of all parties, and finally form a clear product plan.
I. Demand analysis
1. The pain points
In daily life, it is common to forget the location of something and find it after a while. Especially for some items that are not commonly used for a long time, they may not be found in the end, and it is very painful. Personally, I usually write a list of items on the outside of the corresponding storage container, so that every time I look for things, I just need to look at the list of items on the outside to know whether the items are inside, saving the trouble of rummaging through cabinets.
But there’s a problem: you have to go through scattered lists of items each time you find something. In the worst case, it takes O(n×m) to find what you’re looking for. ? So I used a little notebook to keep a list of my items in one place, so that every time I looked at it I knew where everything was. Of course, there are drawbacks to this method, which makes the object less relevant to the actual container, but it worked, until ONE day I forgot where I put the notebook…
2. The motivation
Users need a lightweight “memory” that can record real-world clues about an object (shape, location, size, type…). In order to help users instantly recall the location of the item in the real world when needed.
3. The core
- The storage clues of items should have a strong mapping relationship with the real world, so as to instantly evoke memories;
- “Memory” must be lightweight and must itself be used frequently;
- Pay attention to efficiency, simple and efficient interaction.
Two, competitive product analysis
Early in “put where to go” before, on the market already appeared a batch of relatively mature goods receive kind of product, for example arrange cat, easy to find things, be there, receive where, receive box, small fish receive, what have in the home, etc.
Through analysis, I found that most of these products are in the form of native clients, among which the iOS terminal is the most, and most of the iOS terminal charges, while the wechat small program terminal is less at present. In terms of core functions, photos are generally used to record the storage clues of items, and when looking for things, “search for things according to the picture”. In terms of data storage, there are local storage and cloud storage.
Inspiration:
- This tool nature of the application, should be lightweight (use up and go), carrying small programs this platform is very suitable;
- Taking photos is a convenient and intuitive way to record the clues of items storage.
- The ability to store data in the cloud, so as not to lose data after users replace their phones;
- Use scenarios should not be limited to home use, but may also be used for work or other scenarios;
- To consider the convenience of information input, such as voice input, scan code input;
- Reasonable setting of some items attributes, increase items clues, convenient storage management;
- It is a practical function to combine the storage of items with the memo (shelf life).
Third, brain storm
According to the above analysis, we choose the two concepts of “finding things” and “saving things”, which are closely related to it, as the two entry points for brain burst.
Reader: You brainstorm all by yourself? Pure from high? Me: er… Never mind the details…
Through the above brain burst, we have sorted out the main function points of the product to some extent. About how to do brain storm, you can refer to: www.jianshu.com/p/361db0446…
Iv. Requirement description
After the above series of requirements analysis and sorting, we need to write down the requirements in this step and form a complete Product Requirement Document (PRD), which is the key step for the implementation of requirements. Common content includes: product overview, requirements overview, functional requirements list, functional map, Roadmap, etc. Since “Where did it Go” is a relatively simple small application, I only made a product overview, feature map and feature requirement list at this stage.
Don’t skip the documentation step. When you publish your mini program on wechat, you will need this information to fill in the mini program information.
1. Product Description
Where to put is a micro app for goods storage and management, to solve the problem of easy to forget the location of things in life, and can not find it when needed.
- Core requirements: Quickly locate and find what you are looking for according to the recorded information of the location of the item
- Core functions: mark the location of the item and find the item
- Target audience: the general public
- Platform carrier: wechat small program
2. List of functional requirements
Priority description: A- All core functions must be met first; B- Necessary functions, as far as possible; C- Secondary functions, which can be added and expanded in stages depending on the situation.
Regional column: [Priority: A]
- Users can build their own areas, such as study bookshelf, living room TV cabinet, bedroom nightstand, etc.
- The user can take a photo for the area, and the photo will be used as the base map of the item location marker.
- The user can see the cover map of each area and the quantity of storage items in the area list interface;
- After entering a certain area, users can see the photos and the list of items in the area at the same time, and the two can be linked in the interaction;
- Users can modify region information, such as region name and region photo.
- Users can delete an area, and the original items in the area become “items to be collected”.
- Users can click the edit button on the right of the item in the item list to enter the item details page.
(More information is omitted here due to space limitations)
3. Functional map
4. Interface prototype drawing
Due to the simplicity of the application and the relative clarity of the interface requirements, the prototype sketches were omitted.
To know what happened, and listen to the next “from scratch to develop a full stack of micro channel small program (two) – design” decomposition.