Comments on: Rapid Web-App Prototyping http://samhowat.com/rapid-web-app-prototyping/ Hi, I am Sam Howat. I design websites and smart, useable web applications for everyday people. Welcome to my personal website. Mon, 23 Aug 2010 07:25:36 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Sam Howat http://samhowat.com/rapid-web-app-prototyping/comment-page-1/#comment-1751 Sam Howat Mon, 12 Jan 2009 19:52:14 +0000 http://samhowat.com/?p=82#comment-1751 It's true. I have alot of experience with moving between dev / design teams and it's something I plan on discussing / writing about more in the future. It's great because right now, I'm spending more time playing that roll directly as we work on our apps, and I'm actually recording it and developing our process. It’s true. I have alot of experience with moving between dev / design teams and it’s something I plan on discussing / writing about more in the future.

It’s great because right now, I’m spending more time playing that roll directly as we work on our apps, and I’m actually recording it and developing our process.

]]> By: Josh Kendall http://samhowat.com/rapid-web-app-prototyping/comment-page-1/#comment-1750 Josh Kendall Mon, 12 Jan 2009 19:38:01 +0000 http://samhowat.com/?p=82#comment-1750 Great post Sam. I'll have to bring some of these ideas up at the next meeting at my day job as I can see us only getting better by coming up with a better process (at the very least it would save me some headaches). "Often, the dev team gets handed a prototype with a whole bunch of pretty features. Pretty features that have to be made… it can be a nightmare. " Been in that exact situation before, it's even worse when the pretty features are called one thing, but they really mean something else. Case in point, someone wanted an accordion menu. I know what an accordion menu does as they all pretty much act the same way. Turns out they wanted it to look like an accordion menu, but not be one (even though I was constantly told accordion menu). A Photoshop file and a description doesn't exactly show functionality, having a live example is always helpful. Great post Sam. I’ll have to bring some of these ideas up at the next meeting at my day job as I can see us only getting better by coming up with a better process (at the very least it would save me some headaches).

“Often, the dev team gets handed a prototype with a whole bunch of pretty features. Pretty features that have to be made… it can be a nightmare. ”

Been in that exact situation before, it’s even worse when the pretty features are called one thing, but they really mean something else. Case in point, someone wanted an accordion menu. I know what an accordion menu does as they all pretty much act the same way. Turns out they wanted it to look like an accordion menu, but not be one (even though I was constantly told accordion menu). A Photoshop file and a description doesn’t exactly show functionality, having a live example is always helpful.

]]>