Forms are one of the most basic forms of interaction of a website. But unlike seems, these elements can become a tremendous headache for the designer depending on the size of the page and fields.
These are only a few questions that should be taken into consideration when you are designing a form, and that can define the success or failure of a complex platform.
In these articles below covered some topics like, the alignment of fields, where put labels to facilitate the connection between…
Since dive in the field of User Experience always liked the idea of being able to measure my goals, test and prove not only with theories but with data, and that’s how I discovered the term Data-Driven Design.
In most projects, there are two types of data that can be extracted, quantitative data (numerical data: who, what, when and where) and qualitative data (non-numeric data: Why and How).
The ideal model of Data-Driven Design must include both types of inputs, quantitative and qualitative, and with the data obtained from the from correlation of this two fields it is possible to…
The front-end development is getting faster and faster complex, and the more complex the code easier to lose control and code readability, turning a devouring monster of hours of work and patience developers.
To solve the problem of complexity, very developers began working as modules, creating independent components that came together to form a complex system, so each component can be worked separately without causing a huge headache to the developer.
Browserify that allows us to write modules like…
One of the biggest myths of the design for the web is that users don't scroll the page and the main content must be the “first fold” of the website to use read, if the information is above the fold no one will read.
There are several techniques that can guide the user through the content, one of the best I know is the storytelling. With a good information architecture work and with a right user flow this myth can be defeated.
Security has always been a very important issue when it is developing a system or application, and as front end developer you definitely have to worry about this.
This article written by Mike West gives an introduction about CSP…
I never believed in a company working in teams for competence, where each team has responsibility to deliver a part of a product.
As a designer with background in technology, I see the collaboration of people with different expertise as a great way on create value in the final product.
The relationship between developers and designers can be very difficult, in this article written by Nick Schaden in InVision's blog he describes some of the problems that may exist in the relationship between these two characteristics of the product, and how to reduce this tension.
The first time I heard about “designing in the browser” was with the Andrew Clarke’s presentation “The Walls Come Tumbling Down”, I was surprised and intrigued how I could design digital interfaces without all the resources image editors like Photoshop provide to me. I made some tests and realized that it was simple and much easier, even more when you're thinking about responsive design.
In this article Brooke Kao describes step by step how she and her team worked designing direct in the browser.
At some time I've been researching methods to make the CSS I write more modular and scalable, and of all that I've been studied and tested, BEM (Block, Element, Modifier) seems to be the most flexible and easiest to use, whether in a great team or even on a small project, BEM can help you to avoid headaches!
In this great article by Joe Richardson and Robin Rendle, with the help of some collaborators, they describes the BEM methodology with clear examples to understand what it is and how to use the BEM in your daily projects. A great article for anyone who is thinking of using the BEM but do not know how to start.