dsawler
Joined 16 years ago
Joined 16 years ago
Every night I go through my Inbox and decide what needs to get done tomorrow. I assign a 'tomorrow' date for those tasks in my Inbox. Then, I go to Google Calendar and timeblock when I'm going to complete those tasks. After I do this I journal about my day and come up with more things that I want to get done and the process repeats every day.
Your article talks a lot about the nuances of the app (prototyping animation, specifically) but I'm curious how you were able to distill the experience down to 2 primary use cases - did this come from research, data, customers saying this is what they intend to use the app for?
Did you test any of this with your existing customers? If so, how did you go about that process?
If I'm working on user research I need to understand the people (user groups) who use the product and how they use it. If I'm working on interaction design, I need to understand how each interaction takes place, what problem it's solving, what that means for the user, and how it effects anything else. If I'm working on visuals/graphics, I need to design the product/features/interactions in an aesthetically pleasing way that still targets the user groups.