The first post from Creative Review that I’ll be reviewing is “Designer vs Developer #20: How Chrome was designed 10 years ago”:
In the post, Mustafa Kurtuldu (a Google Design Advocate) speaks to Darin Fisher (VP for Google Chrome) about the process of designing a web browser and the evolution of Chrome during its 10 years of existence at the time of this post (2018).
The era before Chrome’s creation, most browsers were either cluttered and overloaded with information that diverged users from their tasks or were lagging and sluggish. Chrome was creating to replicate what Google did for search engines – focus on content. The designers and developers focused on four key factors when creating Chrome: Simplicity, Speed, Security and Stability.
Simplicity focused on the streamlined UI design and experience. Speed was about how quickly the browser responded when a user performed an action. Making sure that users would receive instant responds to their commands, without lagging or glitching, Chrome worked on a multiprocessor architecture, so if the user clicked to close a tab, it would simply close.Security was making sure that users feel safe on the web, protection from viruses or fake sites, and giving users control. Finally, Stability of the browser, ensuring that it wouldn’t randomly crash.
Darin (the developer) also mentioned that starting with the Windows version meant his teams could focus on building a great browser without thinking about any cross-platform issues.
Overall the post focused on the success of the launch of Chrome and how it stood out against other browser of the time.
The second post from that I’ll be reviewing is “Designer vs Developer #21: Getting started with UX research”:
This post was inspired by a conversation between Jenny Gove (a UX researcher at Google) and Mustafa Kurtuldu looking at the steps to take to conduct User Experience research.
The post explains how designers/developers dipping their toes in UX research for the first time should go about focusing their attention. You should focus on looking at what works best for your products and what doesn’t and the best way to start is by asking people that you know to use your products while you observe. Then you should slowly transition into testing users that are closer to your target audience.
The post then breaks down UX research into 3 stages. The first stage is before you even develop your product, its a learning phase where you learn about the needs of your users and the context which they would use your product. The goal here is to gain knowledge to determine what needs building. The learning phase helps us understand the challenges the users face so we can start to solve their complexities. The post gives the example of if you are developing a wireless charger, you should see how people charge their phones, understand their routine and understand their struggle therefore finding where you can accommodate those struggles and create a solution (creating a wireless charger).
The second stage is the iteration phase where you are looking for ways to improve your product. The post explains that you should set up a space where users will feel comfortable while testing your product. They recommend you bring two researchers, (for taking notes and speaking with the user). This is so one researcher can build a rapport with the user while the other taking notes so you can have a free-flowing conversation. You should ask the user to attempt to complete different tasks with your product and gauge how they react and interact with the product then ask follow up questions to find out their thoughts and opinions as a user.
The final stage is benchmarking, where you track the ongoing metrics (like usefulness or satisfaction) that are important to the success of your product. You may track how user react after the launch of your product, if they are still satisfied with the product or if they have things they aren’t pleased with or their opinions have changed since your initial research. Then from there decide on further improvements you can make.
This concludes my review of the Designer vs Developer posts, I wanted to include this video that was also in one of the posts that I found particularly interesting: