I'll talk about my experiences as a developer and as a manager!
Actually, it's hard to be as wronged as a front-end developer when it comes to schedules.
Work starts when the design is finished, and work can be completed when the backend API development is finished.
It's not often that front-end developers are lazy or diligent, causing work to be done quickly or delayed.
But if the development is not finished, the CEO and the manager will urge the front-end developers.
"When will the screen come out?"
It's easy to explain that the screen work is not progressing because the design is not out, but it's a little difficult to explain that the screen development is not completed because the backend function development is not completed. In that case, you can share Git to let them refer to the development of the backend developers.
However, in the case of front-end developers, they may not have been invited to the backend API repository, so ask the administrator to invite them to the backend repository.
Or, if you use a service like BCTO, you can show the commit history even if you are not invited to the repository, in conjunction with the task.
So, I recommend our front-end developers to watch YouTube or Netflix if they have nothing to do.
Because only the front end will be busy soon.
