Nowadays, images are an indispensable part of the web. However it wasn’t always like that. Only in 1993 the Mosaic browser would introduce images along with content in web pages. Some formats, like GIF and JPEG, already existed in that time and others like PNG and SVG, would only appear in the 90s. Images are used for multiple purposes, like showing pictures, branding, illustrations, charts and many other things.
Continue Reading

Building a product is no easy task. It’ll take months of planning, design and engineering work, but with dedication, hard work and the right professionals by your side, it can be accomplished. However, how can you know if you’re building the right product? Dedication and hard work alone won’t be enough. There’s another factor to consider on the equation: if it solves a real problem for real people. Many startups often decide to go straight to the building phase and end up missing some important steps of the product development process, such as validating their business idea with potential customers and analysing the market. Let’s go over some things to take into account when setting a product strategy.

Continue Reading

If you are not considering the user experience when designing a new mobile application, it’s time to start thinking about it. One of the most important things to have in mind when you design a mobile app is making sure that it is useful and intuitive for the users. If it’s not useful, it won’t have a practical value. At the same time, if the application is useful, but it takes too much time and effort to be used, people won’t engage with it.

Continue Reading

Defining the personas that represent the audience of a product is a very important step of the design process. There are many methods out there to help us figure them out. But the question is: do we empathize with them the way we should?

Continue Reading

As a software developer, I know how hard it is to contain the urge to start coding as soon as we can. After the first sprint planning, our fingers – uncontrolled, hungry creatures – want to start smashing the keyboard, translating our ideas into code fastly and furiously.

Despite how great we feel while developing, it’s always a good idea to take a step back, especially when building something that could be used by many different users – like an API is. A. In this post, I’ll show you why and how to design a properly-thought API.

Continue Reading

By definition, user engagement is exactly what the name suggests. For a mobile app to work well, users should understand its main value proposition to then keep using it repeatedly until it becomes an essential part of their life.

According to eMarketer, nearly 200 billion apps will be downloaded in 2017. In contrast, currently about 25% of downloaded apps aren’t used more than once. Creating an engaging user experience is increasingly becoming essential as brands develop their mobile presence and hope to meet user expectations. Based on this data, how can we change the upcoming scenario for 2017? By tracking user engagement metrics and using these to create solutions to possible problems.

Continue Reading

When developing an interface, I used to be really attached to the visual part–perfect layout, distributed weight of objects, adequate alignments and counted pixels. I had been considered once an overly-meticulous designer, always checking thoroughly if the developer was implementing the project with a high fidelity to the delivered mockups. Until then, I thought this was enough to be a good professional–after all, Design should be all about visuals

This line of thought, established by previously working at companies where accepting crazy estimates was part of the job and the main goal was to please clients (the ones who were paying) made me forget what Design is really about: methodologies, tests and process. Following the latter vision makes you leave aside personal taste, opinions and assumptions to focus on metrics and the real client: the end user. Not always what we believe is the most pleasant look leads to the best results, and that starts to make sense when you have a logical explanation powered by metrics.

Continue Reading

Smartphones have been in the market for a while now. After some comings and goings of different players, Android and iOS were established as the main contenders and now represent almost 99% of the global market share. Because of that, virtually any new app idea will focus on these two platforms.

In this article I’ll be talking about the main differences and similarities that every designer should consider when designing UX and UI for iOS and Android. You can be starting from scratch or already have a published app that needs to be adapted for the other platform. For both cases, I’ll be constantly linking the platform guidelines, as they are the main source of reference when designing a new interface.

Continue Reading

If you’re either a UI designer or a developer, you’ve probably heard of Sketch in the past years – or maybe you’re even using it. Sketch has become a very popular software and broadly used by UI designers. In this article, I’ll show some steps of my workflow when creating and exporting assets to mobile or web applications.

I hope that this article will be useful for designers starting to use Sketch or developers who need to export assets from a Sketch file. If you’re already experienced with Sketch, you’ll probably be familiar with most of the things I’ll be presenting, but you can still get some good insights from this article.

Continue Reading

A common way to describe a product development process is with the Design – Front-end – Back-end stack. This approach takes into account the disciplines involved on the process, and though it helps making things understandable, the distinction enforces the idea that the process is linear and phase-dependent.

This linear flow can also be defined as the waterfall model, and it’s rather common in the web industry. All pages are designed upfront, then a set of mockups are handed off to be translated into front-end code, and then, after all of that, the back-end logic is created. This causes an isolation of professionals on each phase, which leads to a series of implementation issues, mostly due to the difficulty of foreseeing all details and use cases on the early stages.

It also leads to the notion that there’s “my work” and “your work”. It’s not rare to hear developers saying: “Designers can’t touch my code!” or designers complaining that “The front-end developer messed up my layout!”. This creates barriers to the process. As obvious as it might sound, everyone is working towards the same goal: building outstanding products. And a more collaborative process is the way to achieve that.

Continue Reading