Hi, I’m Brian Dys — a photographer from the inside looking out · a composer entangled in electronic music · a UX designer · a spouse, a parent, & everything in between.
About Snippet
0
Comment
October 2008
It was a very early morning at 10 a.m. I was half asleep, half awake when a phone call jolted me from sleepiness. The signal inside the apartment was so weak that I went outside to answer the call. It was an invitation from Chikka for an interview.
A mere seven months ago, I resigned from a night-shift job and ventured onto the mountains – equivalent to working freelance without a clear business plan. The offer from the other line was a real wake-up call for me to set focus once again into designing for the web. The position being offered was quite new to me – User Interface Designer. I said that as long as it’s on a senior level, I was interested.
Web products need to be supplied with a Technocal Document. Its content are the basic specifications of a mobile app or website in the following aspects:
Filled-up by developer
- Programming Language
Filled-up by product developer
- Browser Version Support
- Mobile Version Support
Filled-up by front-end designer
- Mobile Response
This document aids all team members involved in the project by providing with a preview of each team’s specifications. It also puts in context the capabilities and limitations of the product.
Consider this scenario:
- the mobile app is in its Behavioral Testing stage
- the tester is informed that the mobile app is supported under a very old version of Android
- the tester ensures that the mobile app is tested on all key versions of Android
The same goes for websites wherein each team member knows that the product will not be supported in IE versions 8 and below.
A UI Review is a testing methodology conducted by a designer (UI/UX/Front-end) on web products prior to Usability Testing.
The first aspect to be reviewed is visual design and the second is usability.
This is conducted primarily to ensure that the obvious negative findings in a Usability Testing are lessened.
Consider this scenario:
- a working mobile app is available for testing prior to production (launch)
- a designer will conduct a UI Review
- the reviewer will take note of visual design inconsistencies and usability difficulties
- the designer will revise the design based on the findings
- the mobile app is ready for Usability Testing
It is recommended that a UI Review is conducted on a working product rather than on a prototype or mock-up because this puts the reviewer in the context of actual usage and not just a replicated one.
User Research
- Input – research and requirements; output – design artifacts, actual product
- How did we come up with the problem and solution?
- Have one solution and validate with users
- Set target users; create personas
- Continuous user research
- Improve the product for both the business and the users
UI Review/Usability Testing
- Refer to Components Masterlist
- Refer to Usability heuristics
- Create metrics
- Create activities and tasks
- Create directions on how to assume a persona
I’m in the process of letting go/disposing of/getting rid of/selling stuff that I no longer need around the house. In line with this activity, I signed up for two online shops, namely: OLX and Tackthis. Both offer free registration so I went on to set up my online shops.
Just a disclaimer, this blog post does not intend to rigorously compare the two services – I would simply like to document my experience as a user/seller – specifically the noticeable stuff whether positive or negative. Also, this could be an ongoing piece of “review” as I go along with this new adventure of garage selling on the internet.
We’re working on two projects that we’d like to share with you – Visual Variables and Animation Diagram – both of which aim to bridge communication between visual and front-end designers working on web projects.
Check back on Monday for updates.
10/8/2014
Visual Variables and Animation Diagram are available!