What to do first? Design and interfaces or server development? (backend/API)?

Question

Programming

I am developing a project plan. You need to know exactly the sequence of developing a website and mobile applications. Is there any single sequence? Any standard?

Answer 1

Depends on the circumstances. And from what is more important - costs or timing.
If we have a detailed TOR for the functionality that both the back-end and the designers work on, then the development can go along with the design. Or there are integration tasks with the customer's systems, on which you can work without design at all - development does not need to wait for the design.
Or, if the UI team is only engaged in drawing standard templates, then almost all development can be completed without layouts. But, if there is a goal-oriented design stage, i.e. at the start there is no understanding of what functionality will be implemented, then it is worth waiting for the prototypes. Although even in this case - the underlying data models rarely change.
With the development management experience comes an understanding of what exactly can change dramatically after the UI is rendered, and what does not. And this "no" can be put into development. Well, the errors of such an understanding are refactored - in most cases it will still be faster, although more expensive.
It's the same with the mobile app. We know the basic data models, we can make APIs. But as the application screens are drawn, the API can change and be supplemented.

Answer 2

Well, they usually start with a prototype (layout), i.e. from the interface, and then the shell is pulled onto the backend

Answer 3

While designers get at least some kind of interface, coders can already finish everything, and vice versa, if the code is fucked up, and the interface is simple, designers will rest while coders write many letters. Therefore, design is done in parallel with coding, coders have something to do before outputting to the interface, objects, base, structure, connections, logic ...

Answer 4

Depending on what gives understanding.
Sometimes a drawn prototype gives an understanding of the project and the challenges ahead. And it can be a kind of TK.
Sometimes it's the other way around - working with data is so unknown (for example, we program our own relap.io or write our own findface.ru) - there the understanding of the possibilities comes only after the code and the design is secondary.