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.
Designer and Frontend developer
I'm helping to reduce the scope of what we're building to fit in the narrow deadlines we got; designing flows and interfaces; and coding the front-end (FXML + CSS2.1) for a suite of biometric-related applications built with JavaFX.
Designer & Frontend developer
Rankia asked me to tidy their design and front-end codebase after years of inconsistent iterations. I laid the foundations to give uniformity to the design by creating a live HTML+CSS style guide, which made backend developers happier and code faster. I also cleaned up the HAML templates and stylesheets, greatly reducing the size of the CSS files.
Designer & Frontend developer
My role as a UX designer and front-end developer covered many different areas where I had to coordinate with stakeholders and developers: from early sketching to pre-production prototypes; from desktop only to responsive design; from landing pages to newsletters; from R&D to production design and code; from performance audits to copywriting.
Designer & Frontend developer
This was my first _profesional_ side-project. I defined the flows and interfaces and implemented them with the Twig templating engine. I discovered how hard it is to keep a project up and running, and about timeframes and commitment.
Frontend developer
During my Master in Multimedia Development I started working at a professor's agency as a front-end developer. Here I started to share with my co-workers the importance of accessibility, semantic markup, microformats and compatibility (oh, good old IE6 days...).
Proof reader
I got the opportunity to work where the dreams are built. Although it was a job not related to design, I learnt a lot about many topics by being part of a multinational team in a multinational company, where I ensured that the games were properly translated into Spanish.