Programmers, designers and project managers seem always be determining what should come first during the web application development: Userinterface or back-end part. I have been facing this issue since the first month in the web development business. Programmers argue that good functionality can not be limited by pre-designed UI, and creating right UI for the complicated application is rather hard (imagine Project Manager working closely with designer on the creation of 50+ templates of the inner pages for the application). On the other hand, programmers will never think like the customer really thinks and behaves, so in case the UI creation is moved to the back seat of development process, that could lead to the Application being not user-friendly.

Recently I dropped on really nice thought, comparing both models. Seems to be the vivid answer to that long-lasting question.

Which is easier:

1) Architect the backend
2) Build the backend
3) Build the front end
4) Test it
5) Client asks for a change
6) Change the Architecture
7) Rebuild the backend
Rebuild the front end
9) Test it
10) Client asks for another change
11) Change the Architecture
12) Rebuild the backend
13) Rebuild the front end
14) Test it
15-1000) Rinse and Repeat until client says you’re done or runs out of money
1001) You’re done, yeah!

Or:

1) Build the front end
2) Client asks for a change
3) Change the front end
4) Client asks for another change
5) Change the front end
6-250) Rinse and Repeat until client says you’re done or runs out of money
251) Architect the back based on the front end
252) Build it
253) Test it

Posted in web development | No Comments »