We are flirting with agile methods of design/development – almost all of our sites are application based – and are moving towards an iterated prototype model, rather than a very print design based approach of showing 3x visuals with greek text in them, almagamating elements of said visuals and then figuring out how to code them.
Designing in browser, for me, is indicative of a broader problem-solving approach that hinges around addressing the content, the purpose and the environment of the design, rather than just the look of the design.
Phil Wright
Great article.
We are flirting with agile methods of design/development – almost all of our sites are application based – and are moving towards an iterated prototype model, rather than a very print design based approach of showing 3x visuals with greek text in them, almagamating elements of said visuals and then figuring out how to code them.
Designing in browser, for me, is indicative of a broader problem-solving approach that hinges around addressing the content, the purpose and the environment of the design, rather than just the look of the design.