Have you ever noticed your iPhone displaying different call screens—one with buttons, the next with a slider? You’re not imagining it; Apple’s dual design is a thoughtful approach tailored to real-world usage patterns.
Let’s learn the intention of this design decision.
By the end of this article you will understand exactly why Apple uses two different call screens and what that decision reveals about designing for context over convention.
Apple’s Context-First Design
Before designing any interface, understanding the varied conditions under which users interact with it is critical. Contexts include physical environments like pockets or desks, user states such as locked or unlocked devices, and tasks from quick glances to focused use. This awareness ensures designs adapt seamlessly, preventing errors and enhancing usability.
Apple’s iPhone shows two different incoming call screens depending on whether the phone is locked or unlocked.
When unlocked, you see two buttons to accept or decline the call.
When locked, you get a slider that says “slide to answer.” This design is intentional and solves real user experience challenges.
How does Apple improve the experience with these two different screens?
For locked screen context, there is a slider that exists to prevent an accidental answering or rejecting of calls. Phones in pockets, bags, or on hand when locked could easily have their buttons pressed by mistake. A sliding gesture requires a deliberate action in the x-axis, which can greatly reduce the chance of button dialing or unintended call handling.
On the other hand, when the iPhone is unlocked and actively in use, Apple switches to tap buttons for accepting or declining calls. This matches user context: tapping is faster and more convenient when you are already interacting with the screen. It optimizes for efficiency without risking accidental inputs.
User Experience Principles Used in Apple’s decisions
Hick’s law: Simplifying choices based on context reduces cognitive load.
Fitt’s law: Big, closer targets (buttons) are easier to tap when the phone is in use.
Error Prevention: Designing in the context of use with different states significantly reduces the possibility of error.
None of these principles were applied in isolation. They were applied together, to a specific context, to solve a specific problem.
Context Is the Design Brief Most Teams Skip
All those funky UIs you see, often fall short when it comes to real-life user experience. Every element of the screen must own its position and serve a benefit or solve a need for the user. Next time, before you start thinking about how to design your next screen, think about where this experience will take place. Is it at home? Is it while you are commuting on the bus, where you have only one hand available to use your phone? Spend more time thinking and less time designing.
The change is already here
Most people building products right now will miss what's coming.
The patterns are already here. How AI products fail. How behavior is replacing interface. How the best founders build. How the next generation of products gets made.
I write about them every Wednesday. Be the first to know.
Get it free in your inbox → futureofproduct.com