Explain the web frontend development cycle?

Question

Project management

Good day!
I have been involved in the development of back-ends for enterprise systems for almost my entire professional career. Backend borders always ended with some kind of API.
All I know about web interfaces is HTML and thymeleaf for easy PoC demos or manual testing.
But I would really like to understand the web frontend development cycle, what are the main stages in what order you need to go from idea to MVP, for example:
Idea -> formalization in the form of technical specifications (function description, outline how it looks) -> design layout preparation -> implementation of logic on some framework (React, etc.) -> connection of design and logic using HTML + CSS ?
I would also like to understand what is the result of the work of a designer, layout designer, front-end developer?

Answer 1

Idea - Business requirements - then system analysis and layouts are sawn in parallel - then it is divided into two teams back and front - often it is impossible to test the back separately, it is tested with a ready front and start bugs for each direction - corrections - retest - release - profit
All this work within the framework of one feature and the result is a set of works of analysts, designers, developers and testers, and then on quality control, retrospectives and other stories, it is evaluated how the work on this feature went. Where were the problems, who messed up, slowed down the process of rolling out features, and so on, because it happens that bugs hang only on the back, and the front is ready waiting or hangs on a retest, etc., etc. The business does not give a damn that the backs worked well, but on the test the task hung and the deadlines were missed. The whole feature is evaluated, the timing, quality and problems in this context.
If just so.