Gosh - gentlemen, what are doing with my Pinegrow talk (Respectively Ian’s)?
(Grumbling):
Let’s first substitute:
Designing “in” Browser
by
###Designing “for” Browser
It enables us to change the perception - slightly! It let’s us understand that web design is not the artsy-fartsy self-beloved discipline between Webdesigner and his client (such as creating a PDF) but is, under all respect, creating user experiences that are way under the hood of a long dead WYSIWYG.
Design is craft, not art. And web design is a job, requiring much more expertise than just define a couple of metas, title and keywords. Ever tried to “read” your code, ever tried to imagine how a “screen-reader” will present your content to - say handicapped people? Ever thought about usability, accessibility, sustainability and performance?
Designing for browser makes “click and happy” applications hard doing an excellent job anyway - cause it takes all the responsibility from us. You depend on app-author’s view, you trust in someone you don’t know. His expertise is yours.
The major portion of a web project is good research and authoring. It’s making decisions which user experience is causing what action. It’s about solving problems, creating them. It’s a craft - not art!
Cheers
Thomas
freewaytalk mailing list
email@hidden
Update your subscriptions at: