Designing for the web 2.0: from wireframe to prototype
When preparing the design of an IT project, several concepts comes to mind like wireframe, design, sketches or prototypes. But at a time of exploding devices and new technologies like the web 2.0, it's important to define all these notions and put them back into their current perspective.
A wireframe is usually seen as a starting point for designing a future app or website. It usually consists of a rough sketch, usually hand-drawn, of the user interface. Its main purpose is to throw out ideas and design directions”. Hence, it has to be fluid” and disposable to be changed quickly. A wireframes is a team work by definition. Everyone has to be invited to provoke ideas and directions. It primarily focuses on communicating concepts and structure.
Design and prototypes usually go hand in hand. After they have gone through different ideas and concepts, designers usually start designing their future website. But with the coming of the web 2.0 and the growing importance of functionalities, the design has to be functional and tested among users and on different devices (desktop, web, mobiles…) in order to be validated.
Testing their design before implementing it is one of the reasons why more and more IT companies have started using functional prototypes.
If the main objective of a wireframe is to explore and suggest, a prototype will be more triggered towards validation. Moreover, with the coming of the web 2.0 and new devices like mobiles and PC, the focus was put on dynamism and interaction design. Today, apps have now to be crossplatform, taking into account a wide range of devices (mobiles, pocket PCs, tablets…).
That s why prototypes first came into being as IT professionals realised that making changes to a final product was a lot longer and expensive than changing a quick and inexpensive functional prototype. Very close from the final application, functional prototypes are made to carry out user testing. From design to functionalities, Business rules and requirements, an application prototype has to include them all in order to get the validation and start the development process.
Web apps, mobile devices, RIA, dynamic websites.. the competition between apps is growing and their success depends on both the design and user experience. Both have to be carefully orchestrated.
Companies increasingly tend to merge these processes to get a more agile process. Some teams even use prototypes for both designing and developing purposes so that they can carry out user tests and quickly operate and visualize the changes that will have to be made on the final app.
Daniel works at Justinmind, an IT company developing website wireframe and prototyping solutions for IT professionals.
All Best Articles at http://www.allbestarticles.com
You Can Link Directly to "Designing for the web 2.0: from wireframe to prototype"
by using the url: http://www.allbestarticles.com//internet/web-development/designing-for-the-web-2.0-from-wireframe-to-prototype.html
Add Your Picture
Article Submitted By:
Daniel007
This Article Has Been Read 215 Times
Publish/Share this article
Remember: The article body, title, author bio and links may not be changed or removed. By publishing this article, you agree to all the terms in our Terms of Service.
Get the HTML for reprinting the article to your site
Rating: Not yet rated
How To Do Ethical SEO For Educational Facilities
Is Medical Web Design Different to Traditional Web Design?
How to create a successful website?
Why Medical Website Development Needs A Different Approach
How Web Apps differ from Traditional Website
Optimizing a Website for Mobile Devices
Flash based websites: Are they beneficial for you
Web Applications and their Popularity
Vital Aspects of Android Development
Can A Good Website Benefit Your Business?
Using The Google Webmaster Tools
The New Generation of Smart Phone Application Development
Why Is Mobile So Important To Medical Website Design
