23 ms·
Rapid prototyping shouldn't involve HTML or CSS at all.
by richcollins 17y ago
Rapid prototyping shouldn't involve HTML or CSS at all.
- dschobel 17y agoWhat do you propose? Photoshop? Balsamiq?
- richcollins 17y agoI'm not proposing a tool, I'm proposing an approach. We shouldn't have to build custom GUIs over and over again. We should use the same approach that Cocoa does (reusable GUI components)
- SingAlong 17y agoI guess the author refers to prototyping as in getting something basic working rather than UI prototyping. So in that case, thumbs up to HAML and SASS/LESS (whichever you use). I love Balsamiq. I got a lot of UI ideas done easily with it. Was worth a lot more than the $79 I paid. I thought I was the only one using haml to write my HTML for static sites. I just completed a static site for a friend and I didn't know about the static site servers mentioned in this blog, so was using $ haml mypage.haml mypage.html to get my output each time. Kudos for tipping everyone on the statis site servers.
- jeromegn 17y agoI was definitely talking about an interactive prototype of the actual design, not wireframes. It's the step I usually consider when passing on the design to the development department. Sometimes there's much more needed to explain than what a static mockup or interactive wireframe can.