project steps in web application design/programming -


I am starting to work on web applications and I have been with almost the functional specification:

< P> Where do I go now?

  • Can I start working on building HTML and CSS?
  • Can I start building backend body of code? (Server-side email verification and installation of database data-entry functions)
  • Can I start working on client-side scripting? (Javascript / jquery)
  • Can I start working on database structure?

Is these things the best practice order?

Thank you!

Okay, you have created a great idea, now this "description" is used to call the functional user interface Time to expand into a mockup.

Why?

One device says that an app is "what to do". It can be very detailed about it, but the full user interface says that what exactly is an app "actually does" After all, users really care about who is actually under the hood?

In our experience, we find that the user interface design and refine (for example, valid HTML) before the functionality of that project is

  • in a specific Only a small percentage of actual details can be executed when you run an application.
  • Almost all of the actual details can be covered in a functional user interface that actually work it out.

After being pleased with the customer / stakeholder UI, this functionality has an accelerated route for plugging in functionality.

And a functional UI is not a small job, maybe 20-40% of the work can also be spent.

-

It is being said that do not waste time on everything - strong> beautiful - just focus on the most useful interface, a graphic person Come in later and make it beautiful, when you are busy working on it.


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -