Mobile app Design Entry level: What is the true front and back end prototype?

It is not the product manager that can only draw a functional prototype, but if the product manager does not draw a prototype that battle is also a lot of discount, not only because the prototype is the design of the function display, but also because the product prototype is actually the user's actual needs, business processes, system specifications and other processes of product crystallization. This article is suitable for entry-level mobile product managers and can be used as a reference when thinking, designing, creating clients and background prototypes.

Product prototypes are important confidential documents for the product, so the introduction of a product that is currently discontinued and relatively simple is available for beginners to get started as soon as possible. After that, we will continue to carry out advanced product design instructions for more complex or multi-plug-in apps.

First, before doing the prototype

Demand research, demand acquisition, all kinds of communication, all kinds of materials here is not much to say, product design related articles or books a one, we can take the initiative to see. One thing to emphasize here:

What the user wants, not all the users need.

To give a chestnut: users want to add keywords to the document, in fact, just need a label classification, the user to modify the content of the submission, in fact, sometimes just lacks the draft function. Grasping the real needs of users is the first in the design process.

So, teenager, please don't rush to open the axure first.

Ii. What does the prototype look like?

Prototype content basically includes: Flowchart, page display, field description, interactive operation, rule description, special notes, etc.

Business Flowchart:

　　

Business process is the core of product design, if you want to achieve what purpose, how to achieve it is not clear, the product is meaningless. As for the need to do business flow chart, Swimlane map, Sequence diagram, page flowchart, etc., according to the actual situation of different projects, the key is: to be able to read! A lot of flowchart, voluminous several large pages, unknown feeling Li, to the needs of the review, explain a process to spend half a day, and do not expect the beloved program ape in the development of the time to look at.

Page navigation:

　　

According to the menu or core function block set product navigation, I personally used to differentiate the page according to different business status, so that their own and development can be more clearly in what level page, page purposes, this look at their own habits, can clearly express the functional structure can be.

Content and Description:

　　

A simple page that allows you to annotate content, conditions, interactions, and specific instructions directly on the page. If it is a complex logic process module, it is recommended that for modules, independent design flowchart, module Global description, Rule description, field description, etc., this will be detailed in the subsequent product design for the more complex process.

In this process, when you finish a module of the associated page design, you can close your eyes in the mind, simulate yourself as a user on the various pages of the actual operation, can help you to find and modify some of the minor problems in a timely manner.

Manage Background design:

Often see the sharing of mobile design articles, but rarely see the introduction of mobile side of the background, it is not mobile and management background is different people design it? Anyway, as a mobile product manager Ben Wang has been silently doing backstage prototype (sad face).

　　

　　

Mobile app's backend core functions are concentrated in the data class or business Operation class, the main function of the app is to achieve the purpose of online ordering of some kind of mall, order after sale, and then the main users are platform operators, the core goal is to operate the front-end orders, so the focus of the backend design is:

Front-end Basic data configuration

Business Data Classification Aggregation

Document flow processing (emphasis)

User Rights

Report Analysis

It is recommended that the entry-level Product Manager synchronize the implementation of the back-end, which is good for business logic grooming. In general, I will first design the mobile side, and then design the corresponding management background, and finally iterative adjustment to achieve a smooth front-end business.

Some final words:

Product prototypes are only used to express their own design ideas, even if there is no axure, the use of ordinary paper and pens can come up with a practical product prototype (of course, to improve efficiency, why not?).

It must be no harm to think more and practise more.

Drink less "unknown sensation" product chicken soup. Or you can thoroughly understand them for their own use, or some years later there may be a "listen to a lot of truth, but still have a bad life" feeling.

Product managers sometimes easy to walk on "although I do not, but in fact I am very good" fruitless, good, practical, OK?

Mobile app Design Entry level: What is the true front and back end prototype?