The following case study is part of a design challenge. I am not in any way affiliated to Grab or any other companies/individuals mentioned in this article. The design decisions and assumptions taken in this case study are solely based on publicly available information.
Imagine that Grab is introducing food delivery service in Philippines (like FoodPanda). You are tasked to design the driver app for motorbike drivers. Here is a rough outline of how the process is like:
I used to loathe designing error states, and it was always in the aftermath. My go-to solutions used to be to use system default designs to make sure I hit all the edge cases. I loved to work on the core happy path but ignore the other non-core user journeys. Often I would hit a roadblock. I have to go back to my core flow which I meticulously designed to include the new use cases I stumbled upon. This cost me a lot of time and a lot of iterations.
I have improved a lot in anticipating unknown future use cases. In this blog, I share my process and how I approach designing for edge cases early in my design process. …
API stands for Application programming interface. According to Wikipedia, it is a set of clearly defined methods of communication among various components. A good API makes it easier to develop a computer program by providing all the building blocks, which are then put together by the programmer.
If UI is for humans who interact with the face of a software, API is for programmers who interact with it behind the scenes to make the software functional.
Here’s what Jared Spool, a founding figure in design industry has to say about APIs in relation to designing screens.
As a designer, our primary role is to act as a bridge between users and stakeholders, providing necessary contexts, identifying core needs, and crafting best solutions to get the job done. …