Neither art nor Java, we are front-end engineers, and see who we really want to fight with?
As early as in the ancient times, the UI and UE has not differentiated, UE has not been attached to this level of time, the front end of this position is mostly divided into the design department, so for the still confusing front-end for the art of friends, hope to know.
We all know that in the process of product development increasingly clear today, the role of PM is more and more important role, the external evaluation of a product good or bad, the first stakeholder on the PM, however, in the product line, the nearest user is the front end of the loop, so PM How to communicate well with the front end is particularly important. Simply speaking, designers out of the map, the development of writing programs, the front-end to do interaction, the user's eyes every page elements, fingertips on each interaction, have passed the front-end code packaging and precipitation.
Therefore, the front-end to the user is responsible for the PM.
Since the definition and characterization of this position in the front end is broad and vague, especially in small and medium-sized enterprises are different and each have differences (such as: fine components JS interaction and refactoring two directions), but no matter do refactoring or do interaction, the most important front-end responsibility is to the PM want the interface and the expected user experience, produced and presented to the user, And in their own professional perspective of the current solution optimization and in-depth research, feedback to PM.
Front and PM conversations
If you have seen the Product Manager column, "Technology to product manager" and so on, probably feel that most of the time, some company's products and technologies are in each other's state, its dialogue or complex or Jane, for example, we will first look at a PM and front-end dialogue:
PM: Is this sliding effect possible?
Front End: Can
PM: What about this Ajax interaction?
Front End: Can
PM: What about this background-color gradient with a shaded rounded corner and a translucent Hover layer with a rotating effect?
Front End: Uh ...
PM: I have seen a foreign website has this effect ...
Front End: Can
Front end and PM dialogue-Solution
The above conversation in the front end only said 3 "can" word, PM also got to want to reply.
Of course, the front end is thoughtful, like most programmers, when we think about the outside is a black box, that is not to say: An ideological Turing can let all the front end lose their jobs? The answer is No. Even without the "Chinese room hypothesis" (the Chinese reactiveness) to verify, I also guarantee that the final PM will still choose a creative front-end rather than a machine. So let's open the black box and look at the weird world in the front of the conversation:
PM: Is this sliding effect possible?
PM: What about this Ajax interaction?
Front End Brain Complement:
* Involving styles and interactions
* Page layout through the browser: IE8 + Firefox3.5 + Chrome 9 + and so on
* IE6/7 needs to write a hack
* New Write response CSS to compatible with mobile devices (iOS and Android) version
* Picture needs a x2 version compatible Retina monitor
* ......
* Is it optimized for users with color barriers?
* Do you need compatible blind browsers?
* What if the user disables the JS script
After several rounds of struggle, the front end gives the final solution "can", then continue:
PM: So this background color has a shaded rounded corner, and a layer with a spinning effect after the translucent Hover can implement the code?
Front End Brain Complement: (Er ...) If it is implemented with HTML5, so easy, but F*ck IE6, actually do not recommend to do so gorgeous decoration on the floor.
PM: I have seen a foreign website has this effect ...
Front-end Brain Repair: (CAN) well, since our users are not foreigners, so at the moment, or more write point Hack style, compatible are compatible with it
Now you know who the front end wants to fight with?
PM how to communicate with front end
Listed above, we can probably see that the front end of the biggest "enemy" is neither a strong PM, nor a frequent change of demand, but the evil browser vendors. This is also the front end usually why not with PM pinch a reason, originally, when internal and aggression coexistence, the front-end more naturally to all the resentment point to the browser, pointing to the reluctance to upgrade user groups, this is the main contradiction. (At this point, PM is not laughing?)
Even in the hostile view of the enemy, win, PM if you can understand some of the habits of the front end of certain ways of thinking, then the user experience to play to be able to do is no longer how difficult things. Moreover, the front-end is the development of engineers and designers of the bond between, we are very willing to cooperate with good PM, in accordance with the PM on the product understanding to create a good product.
Similarly, in an understanding and identity environment, the front end will also be full of sense of achievement, and at the same time inspire extraordinary creativity.
The front end is the scissors in the hands of the Gardener (PM), oh no, it should be the gardener's finger. (Don't forget to design, develop and so on other fingers yo ~)
How the front end communicates with PM
Change the position, then the front-end in and PM communication need to do what?
Some teams have this acquiescence: "Front end does not need to participate in product requirements and design, the design will naturally find you." ”
In the face of such trouble, we have to play their own initiative, to avoid the "done, boat very broken" situation, the practice is very simple, the initiative to the PM to ask for the participation of the project, even if only one more project Mail cc object, also for the late front-end code deployment brings great convenience. Otherwise, the design has been finalized, the front-end can not come out of the situation, the responsibility in who? Most of it will be attributed to the front-end technical reserves, but also to the designer is very embarrassing.
A joke: (PM) is the front end of the friend, and then the bad is "enemy" (designer) of the "Enemy" (PM). (PM again should laugh)
Note: Try to change the position of the person in () LOL
The front end of the "occupational disease"
Continue to know each other, understand the front end of this topic, talk about a few front-end "occupational disease", can be used as a welfare, for the right remedy, the future and front-end communication will be more smooth. (Each occupation has its own "occupational disease", of course, I do not think it is morbid, but it will be easier to understand the description) simply list two:
Layered World
It can be said that in the future of Google Glass before the advent of our contact with the Web page is almost 2D, the front-end (designers will be seconded?) The world in your eyes usually has a 2D layer version.
For example, the huge advertisement that is seen at the bus station the first impression in the front eye is that if you refactor the design to HTML page layout, how the tags are nested will be optimized, CSS compatibility is how, yes, we often take pictures to the layer of the prototype to see, and then proceed to the next "occupational disease" to the iteration.
It's always a bad thing to think about changing places.
Always consider compatibility
Know what the front end is most concerned about IT industry news? (see below)
XX browser upgrade, version number of XX
XX company announced to start browser
XX submitted a new XX standard to the Consortium
XX launched the latest Retina hardware, with XX browser
XX and the lack of integrity of the introduction of Non-mainstream resolution screen
XX system will stop updating in 500 days
Yes, we are concerned about the release of hardware digital devices, but compared to the device itself, we may be more concerned about screen resolution, the default browser kernel, JS performance run points and so on. We spend a lot of time and effort to solve the compatibility between different browsers, different screen sizes and different device cores, so that as many users as possible can get better user experience assurance. We will almost have all the new things connected to the compatibility level to discuss, which may be beyond the understanding of others.
Although the old version is stable, but the new edition is kingly.
Summary
Do a communication PM, do a communication front-end, so that products in the user experience in the jungle all the way.