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.
- 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.
Visual Variables and Animation Diagram are available!
The layout of HTML Patterns contains the following:
- web view of the HTML markup and CSS
- source view of the HTML
- source view of the CSS
textarea of HTML and CSS are editable to immediately update and reflect the changes on the web view.
One thing that gets in the way is that the stylesheet of the site gets applied to the content in the web view. The favorable behavior is for it to appear unstyled by default and only the CSS in the source view will affect it.
- Contain the web view in
- Reset the style by targeting the parent selector of the web view container
Each of these solutions are not without quirks. I will do a quick follow up as I test for the best solution in this situation.
As far as HTML Patterns is concerned, I settled with #1 – the original solution. Although
style scoped is only supported by Firefox, the important thing is that the HTML markup is seen and it is interpreted in the web view. An advantage for Firefox users – they will get to see the style in the web view, too.
Regarding resetting the style of elements in a specific container, the CSS property
all and its value
initial, again, is only supported by Firefox. What I did was to manually reset each property that was previously set by the HopScotch stylesheet.
iframe srcdoc works best in bringing back the style of the content to browser default but it’s hard to control when it comes to live-updating the CSS (aside from the fact that, again, only Firefox supports that attribute).