Welcome to our new “The basics of” series. In this series we’re going to tackle all the questions related to mobile design, mobile QA and testing. We’ll be looking at issues both big and small–nothing shall be overlooked. (Psst! Make …
Waldo Blog Articles.
To hamburger menu, or not to hamburger menu? That is the question. Sure, the mobile design community has made some questionable decisions over the years. But so far, 2019 has seen a lot of exciting mobile app releases and significant …
In 2007, Apple changed the game with the release of its first iPhone. Soon, installing applications on our mobile devices became the norm. Fast forward 10 years and the mobile app industry is thriving. In 2017, there were 178 billion …
We recently shared how a few of our favorite apps mastered clean and simple customer onboarding by practicing empathy and designing with their customers in mind. We took a high-level look at their onboarding flows and what we love most …
Over-complicated UX or UI is one of the biggest mistakes we see mobile app creators make. Too many apps try to fit in too many features. Or worse, they ask their users to do the heavy lifting. At the end …
This is part two of a two-part interview. Read part one on developing mobile QA processes for customer reliability. Last week, we shared part one in our interview with Square. We discussed how they create mobile QA processes that ensure …
This is part one of a two-part interview. Read part two here. Mobile QA can be a complex topic, as each product team is testing for something different. That said, learning standards and processes from other app and product creators …
In past articles, we’ve talked about how manual QA takes a lot of resources, and of course, a moderate amount of frustration. We’ve also walked through specific examples of how waldo.io saves mobile developers time and money they used to …
Imagine your product team is in the planning stages of building a new feature for your mobile application. You brainstorm all potential use cases, starting with your general use case. That is, the problem you built your app to solve …