Showing posts from August, 2012

Five (5) cool new HTML5 text-level semantics elements

HTML5 adds to our web pages the new structural semantic elements like <header>, <aside>, <nav>, <section> and many other, which are pretty awesome. But what even more exciting are the new text-level semantics elements which change text visually without extra (and sometimes complex) coding. Below are the overview of five of them. Unfortunately only Chrome browser supports them in full today. 4 out of 5 work in Opera. Firefox and Safari support fewer, Internet Explorer 9 is on last place, and hopefully this will be changed in upcoming IE 10. Refer to the table of supporting browsers at the end of the post. 1. The "mark" Element The <mark> tag is used to highlight or reference a run of text due to it's relevance in some other context. You can incorporate this tag into the search results page on your website or blog to enable your visitors to more quickly find the content they search for. 2. The "progress" Element If y

Is it a problem of objective, or shoud UX designer know how to code?

Communication, understanding, and right message are very important from the beginning. What I learned: have a strong and clear objective. Deliver it to right people. Preface: I applied for UX Designer position in a large company. Then was given a call from HR, and during the conversation I mentioned that, yes, I can write the code on JavaScript. Follow up was the scheduling of a phone interview. Phone ring… I was asked to open a link with some code editor window in browser. And the first question on the interview, which apparently appeared to be a strictly technical and coding interview, was: - Are you familiar with JavaScript? Ok, write the code to implement event handling in JavaScript as if no implementation of event handling existed in JavaScript . - Uh, what? What exactly in your mind? - I want these two functions: function addEvent(element, eventType, callback) function fireEvent(eventType) - Ok, we can create our own object and make these two functions be a public

My Approach To Design

Here is my objective of what I do designing things, what makes me creative, productive, and helps to deliver an awesome result: I am seeing myself as a pixel perfectionist with developer/technical background, and with the ability to understand the intersections of disciplines from multiple perspectives bringing the big picture to the table I approach design with a simple, fun, and intuitive mindset. I enjoy conceptualizing and designing clean interfaces. I love simple, usable interfaces and appreciate the hard work that goes behind creating them. I love to see my work come to life in front of a large audience. I subscribe to the Less Is More (minimalistic) design philosophy. I solve complex problems and drive company’s products experience forward. I design simple experiences that delight users. I am taking business requirements and translating them into customer experience requirements. I visualize them. My goal is true innovation to help end users with sincere empathy.