Keep a clear focus on what your product does.
Digital products and services need to be constantly updated. This can arise inconsistency, overlapping or deprecation issues. A feature evaluation can reveal the need for creating, updating, merging or removing features.
How features are organised around your product.
Users must effortlessly know what your product can do for them; how to use it; and, most importantly, why should they choose it among the competence.
How users communicate with your product –and viceversa.
It is worth to rely on affordances, conventions, common patterns, natural copywriting and a robust interaction with error resilience.
How your product talks to your users.
The text is the soul of the user interface –UIs can work without styling, but won't do without text. As such, it needs to be consistent in tone and mood, except for some special context scenarios.
From a primitive version of your product to final markup.
It’s easier –and cheaper– to iterate and fix conceptual issues in the early stages of development instead of after launch.
I’m comfortable with digital design tools (Sketch, Adobe CC, etc), HTML5, CSS (+ pre processor tools), basic JS (vanilla and jQuery), microformats, accessibility, task runners, site generators, performance best practices, etc.
Test early and often.
Metrics only provide quantitative data at which you can only guess. User testing yields real life insights on what is wrong: inconsistent labelling, strange workflow, undetected bugs, etc.
Vetaminic, an online management system for veterinarian clinics.
Many different projects with XHTML and CSS2.1, but the Internet updates fast and now all those sites are either updated or down.