Product industrialization is of great significance to product managers and developers. In this article, the author shares his thoughts on products based on the philosophy of React. Interested friends may wish to take a look, maybe it can help you. After going through a lot of projects, I found that I accumulated a lot of prototype pictures, and I opened it again with curiosity and found that most of them are actually similar;
However, the prototype of each project is basically reworked, and rework means that the logic needs to be rewritten, and rewriting means that there will be a conflict of understanding with R&D.
In previous projects, I also encountered other product managers who had disputes with developers and even had to leave.
All along, I have been reflecting on two questions:
Is there a way to quickly produce a prototype?
Is the idea of product and development a natural conflict, and can only the special leads product learn code knowledge to solve this problem?
Just recently learned React, and got some thoughts and solutions from it, especially its philosophy:
Single responsibility principle and componentization (of course there are many philosophies of React, but these two are the most profound to me), perhaps the key to solving problem two is to solve problem one first.
First of all, let's introduce React: this is a relatively well-known JS framework in the development industry, and developers will use these JS frameworks to write apps, small programs, and the web.
The core philosophy of React is: "componentization", dividing a page into small components, each performing its own role.
1. Prototyping shouldn’t be the most time-consuming part
Conflicts come from different understandings of the same thing. For example, when working on project A, developers will feel that writing this way will make the code concise;
But the product will feel that it is more convenient for the user to do so;
When we do another similar business, the developer feels that the business is similar and wants to quote the previous code;
However, at this time, the product will change some functions due to specific business scenarios (for example, in the announcement, the delayed shutdown may be changed to active shutdown.