Question about UI?

Question

Can any one have a answer of this question.

Q. That time spent collecting requirements for the UI (user interface) is time well spent or do you create the UI in parallel with the code development cycle.

Answer 1

It's time well spent.

Doing your requirements gathering throughly is worthwhile for more than just the UI.

If you know exactly what you're trying to build it makes life a lot easier and reduces the chances of the customer being unhappy with the finished product.

Answer 2

To the user, the UI "IS" the application. If the UI sucks, the application sucks to them. Gather as many requirements as you can in the time alloted. Sketch out UIs on paper to get quick feedback about whether the look is on the right track. Iterate until you get as close as you can. Then build the UI prototype and let the users play with it a while before coding in all of the functionality. UIs can easily become the most complex part of the application if there is a lot going on because there can be so many controls with complex interactions. Give the UI short-shrift at your own peril!

Answer 3

it's relative to what the user needs. if its a business application then it'll be used regularly by the business so they may have certain requirements for regular tasks.



Keep in mind what the applications for and work from that.