UX/UI Design: Foundations to Practice · Mobile-First and Responsive Design
Performance as a Design Consideration
How quickly a design actually loads and responds is not purely an engineering concern separate from design; the specific design choices made directly affect real-world performance, and a beautifully designed but genuinely slow experience fails users just as thoroughly as a poorly designed fast one.
A person's actual, felt tolerance for waiting depends heavily not only on the genuinely objective, measured loading time but also on whether the interface provides some form of meaningful visible feedback during that wait, echoing the system status principles covered in Module 8; a design that shows a visible, structured placeholder of what content will eventually appear tends to feel meaningfully faster to a real person than an equally long, objectively identical wait spent staring at a completely blank, unresponsive screen.
- Perceived performance depends on visible feedback during a wait, not just objective loading time; a structured placeholder feels faster than an identical wait spent on a blank screen.
- Specific design choices, like large uncompressed images or elaborate animations, carry real performance costs a static visual evaluation never surfaces until the product is actually built.
- A design tested only on fast office internet can perform noticeably worse for real users on slower mobile connections, making throttled testing genuinely important for mobile-first products.
- A well-designed mobile experience deliberately anticipates slow, interrupted, or offline connectivity, offering informative messaging and possible offline functionality rather than assuming always-reliable connection.