{"id":537,"date":"2010-04-06T11:01:31","date_gmt":"2010-04-06T10:01:31","guid":{"rendered":"http:\/\/www.setfiremedia.com\/blog\/?p=537"},"modified":"2010-04-06T11:01:31","modified_gmt":"2010-04-06T10:01:31","slug":"when-to-ask-for-user-details","status":"publish","type":"post","link":"https:\/\/www.setfiremedia.com\/blog\/when-to-ask-for-user-details","title":{"rendered":"When to ask for user details"},"content":{"rendered":"
When should you ask for information from your users? I recently came across two online apps that illustrate the right and the wrong way to resolve this question. <\/p>\n
Firstly, we have Mockflow<\/a>, an online wireframe tool. Includes versioning, collaboration etc. So, if you’re wondering what this application’s like, how do we find out? They have a pretty good video on the homepage, that’s nice enough. And if you take the tour, you can see some screen shots that outline some of the functions of the site. Very nice.<\/p>\n But if I want to try it out, what do I get?<\/p>\n Hooray, another sign up form. Those never get dull. <\/p>\n Contrast this with Dabbleboard<\/a>, another online collaborative working tool. Here’s the homepage:<\/p>\n
\n<\/a><\/p>\n
<\/a><\/p>\n