How do you organize the interaction between a frontend developer, a UX specialist and a designer when developing web applications?

Question

Design

By designer here I mean a person who makes beautiful and draws page layouts that are sent to the developer.
They are also interested in the tools and OS that are used in this process, and how the problems associated with them are solved. For example, the front-ender prefers to work in Linux (not everyone has switched to Macs yet?), and the designer draws in Adobe Illustrator on his Mac, as a result, the front-ender cannot open the layout on his own.
I would like to read about the real experience of the designated workflow and interaction, especially in large companies when developing serious projects. I can’t even imagine how such processes occur in the same Yandex or Google.

Answer 1

I'll tell you how it works for me and what implementations I saw.
Sample process:
There are small changes here, when there is an analyst (explores users and conducts usability tests), who conveys a set of requirements to the interface designer. The designer makes sketches, makes a design and uploads it to InVision to add interactivity. In this case, the designer designs and draws at the same time.
Further, everything is according to the scheme described above.

Answer 2

I can add a couple of tips from personal experience to the existing answers:
1. Make communication within the team as simple and effective as possible, there is Slack for this. Ideally, entrusting someone with the role of curator of these communications - this will slightly remove responsibility from the participants and liberate communication.
2. Distribute the roles in the team so that the responsibilities overlap - that is, to a small extent overlap with different participants. Where there is no overlap, the seams diverge, and processes come out of them that are not assigned to anyone.
In a team with well-established, easy communication and diligently allocated scope of responsibilities, high-level problems like “what OS” and “to whom to give what and in what form” will be solved by themselves - or rather, by the forces of your team. Good luck!

Answer 3

just in large companies, this problem can be solved simply - the range of technologies used is determined by management. freelancers and other equals need to be able to open any source themselves or have sufficient demand to filter out "I want it, I won't, send it in a different format."
IMHO, I'll listen to other answers)

Answer 4

It will be uncomfortable for a frontend worker to work in Linux.
Monsters from Adobe overtook their counterparts and set the course for everyone involved in web design.
Linux has GIMP - it falls short of Photoshop.
PSD files can be converted to another format, but information about layers and other important things will be lost.
We'll have to try to make sure that Photoshop starts. It could be:
In general, the choice: Mac or Windows. On Windows, you can save money by choosing a less powerful computer. An easy choice.

Answer 5

Well, I'll add about tools...
Adobe has such an online service for .PSD layouts - Assets. https://assets.adobe.com/files
For a front-end developer and a designer who works in Sketch to work together, test something like Zeplin .