I usually start with the front end and have the user journey drive the requirements. Then build the back end, knowing what data the front end needs already, and then everything meets in the middle. At least that's the theory.
Although, this is just in terms of personal / solo projects. At most of my jobs the back end is written first because the UI is often an afterthought in the planning stages 👀
I usually start with the front end and have the user journey drive the requirements. Then build the back end, knowing what data the front end needs already, and then everything meets in the middle. At least that's the theory.
Although, this is just in terms of personal / solo projects. At most of my jobs the back end is written first because the UI is often an afterthought in the planning stages 👀
Casual case especially for enterprises, where the business logic and data flow comes first 😉