Comments on: All hail the user http://aaronstaves.com/2008/02/06/all-hail-the-user/ Not quite extinct! Mon, 12 Apr 2010 15:39:37 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Welcome to Planningville - Population++ » AaronStaves.com http://aaronstaves.com/2008/02/06/all-hail-the-user/comment-page-1/#comment-21 Welcome to Planningville - Population++ » AaronStaves.com Sun, 10 Feb 2008 08:29:36 +0000 http://aaronstaves.com/2008/02/06/all-hail-the-user/#comment-21 [...] by a recent comment on my last blog, I've taken David up on the webpage wireframe and prototype tutorials he found. [...] [...] by a recent comment on my last blog, I’ve taken David up on the webpage wireframe and prototype tutorials he found. [...]

]]> By: Aaron http://aaronstaves.com/2008/02/06/all-hail-the-user/comment-page-1/#comment-20 Aaron Fri, 08 Feb 2008 17:06:46 +0000 http://aaronstaves.com/2008/02/06/all-hail-the-user/#comment-20 Thanks for the comments David! As usual, you seem to have some awesome insight into this topic. Assuming I can get a good handle on those wireframe/prototype builders, I will most likely be implementing those in my next task. I possibly might try them out first on some non-work related projects, but it definitely seems like it's worth a look. Creating all that test data using dojo.data may even lead to some bug fixes before they make it to the live server. which would be... amazing. Thanks for the comments David! As usual, you seem to have some awesome insight into this topic. Assuming I can get a good handle on those wireframe/prototype builders, I will most likely be implementing those in my next task. I possibly might try them out first on some non-work related projects, but it definitely seems like it’s worth a look.

Creating all that test data using dojo.data may even lead to some bug fixes before they make it to the live server. which would be… amazing.

]]> By: David Snopek http://aaronstaves.com/2008/02/06/all-hail-the-user/comment-page-1/#comment-19 David Snopek Fri, 08 Feb 2008 16:45:37 +0000 http://aaronstaves.com/2008/02/06/all-hail-the-user/#comment-19 Your ideas intrigue me, how may I subscribe to your news letter? I found some interesting articles on make "live" wireframes and prototypes. This one is basically, about how interface designers can make HTML/CSS wireframes which will get passed to developers (so, basically, you could pass this to yourself!): http://www.developertutorials.com/tutorials/ajax/ajax-wireframing-approaches-7-11-23/page1.html This one is about taking the wireframes and making them into a prototype (basically, like a wireframe except the buttons/links do stuff, only they don't connect to the server at all): http://www.developertutorials.com/tutorials/ajax/a-designers-guide-to-prototyping-ajax-7-11-23/page1.html The process I would envision using these techniques would be like: (1) There is a new interface to design. You make some wireframes until you've got all the bits you like worked out. (2) Then you make a prototype out of the wireframes and show it to the support staff. (3) They play with it and give comments. You adjust the prototype accordingly. (4) Once goodness is achieved, you can implement it and have it actually change things on the server. Dojo Data would be a great asset in this process, because the prototype can have all kinds of fake data which can be modified like real. Assuming the cost of working on the prototype (ie. time spent) doesn't get too high, this would allow you to have all "customer" expectations documented in a very concrete form before making the full commitment of implementing it. Anyway, just some random ideas.. Might be overkill in most situation. Keep it real, homes! Your ideas intrigue me, how may I subscribe to your news letter?

I found some interesting articles on make “live” wireframes and prototypes. This one is basically, about how interface designers can make HTML/CSS wireframes which will get passed to developers (so, basically, you could pass this to yourself!):

http://www.developertutorials.com/tutorials/ajax/ajax-wireframing-approaches-7-11-23/page1.html

This one is about taking the wireframes and making them into a prototype (basically, like a wireframe except the buttons/links do stuff, only they don’t connect to the server at all):

http://www.developertutorials.com/tutorials/ajax/a-designers-guide-to-prototyping-ajax-7-11-23/page1.html

The process I would envision using these techniques would be like:

(1) There is a new interface to design. You make some wireframes until you’ve got all the bits you like worked out.

(2) Then you make a prototype out of the wireframes and show it to the support staff.

(3) They play with it and give comments. You adjust the prototype accordingly.

(4) Once goodness is achieved, you can implement it and have it actually change things on the server.

Dojo Data would be a great asset in this process, because the prototype can have all kinds of fake data which can be modified like real.

Assuming the cost of working on the prototype (ie. time spent) doesn’t get too high, this would allow you to have all “customer” expectations documented in a very concrete form before making the full commitment of implementing it.

Anyway, just some random ideas.. Might be overkill in most situation. Keep it real, homes!

]]>