Below: Q&A with David Keegan a software engineer who in his spare time develops apps and shares his lessons learned on his brand new site InScopeApps. He has been raving about Verify ever since he started using it to get quick feedback on design and functionality of his apps.
What do you do?
Ia''m a geek, specifically a software engineer that started InScopeApps to develop and share apps and any lessons learned along the way. Ia''m obsessed with interface design. I found that ita''s sometimes hard to know if users comprehend my designs and understand what the product does and how it works. I found Verify to be a great solution for soliciting quick design feedback from users.
How has Verify helped so far?
Verify gets my questions in front of a larger audience then Ia''ve ever had access to before. The feedback is also so focused that it makes it easy to take action. Ia''ve used Verify on two specific projects where I've made improvements based on data collected:
- Improved the design of InScopeApps: The size and prominence of the download button was increased because people reported that it wasna''t immediately clear how to download a product. I am also redesigning the layout of the product information based on responses from Verify tests.
- Improved upcoming app called RockStar: I did a series of tests for RockStar to refine the label of a checkbox because it was clear from tests that the checkbox wasn't descriptive enough.
Which test do you use most in Verify? Why?
My favorite Verify test is the label test. This test allows you to place markers on key parts of the design. People then describe the marked items in their own words which really lets you know if the design is connecting with them or if ita''s unclear. These tests have revealed problems and ideas I would not have otherwise thought of or changed.
Anything else you'd like to add?
Thanks ZURB for creating such an awesome tool and allowing me to share my experiences with it!
