How to organize the development of a client-server application?

Question

Work organization

I always wrote web applications as a full stack and in one, that is, controlling the entire process completely, but recently I moved to the team to the position of a front-end, there is another back-ender in the team, which also used to be a full-stack.

We clearly feel gaps in the organization of work. Especially in terms of api, as the place of our "docking".

Maybe there are ready-made recipes on how to organize such work? Write some plans? Regulate api in advance? Something else?

Separately, I note that I have to work, in fact, without technical specifications, everything is in flux.

Answer 1

Define api contracts at least at the level of json files, the backler will cut slowly, you will already have stubs. How to document this is already your troubles, I would pass on an approximate jison and boundary conditions. Let's say we use swagger, but since I'm writing a separate component, I do both the front and the back myself

Answer 2

UML