Fundamentals 13 min read

Why Every Designer Must Master iOS HIG and Material Design

This article explains what the iOS Human Interface Guidelines and Google Material Design are, why they are essential for designers, and provides a practical roadmap for studying their design philosophy, basic rules, and component libraries across mobile platforms.

VMIC UED
VMIC UED
VMIC UED
Why Every Designer Must Master iOS HIG and Material Design

What are the two major design specifications?

iOS Human Interface Guidelines (iOS HIG) and Google Material Design are the classic system‑level design specifications that guide UI design for iOS, Android and cross‑platform products.

Why learn these two design specifications?

They provide high‑level design philosophy, systematic interaction knowledge, criteria for evaluating design solutions, and a source of creative ideas. For example, Material Design’s 3‑D space concept inspired a new interaction pattern in a Vivo game overlay.

How to study the two specifications?

First, read the original documents systematically to get an overview. Then break each specification into three layers: design philosophy (the abstract core), basic UI guidelines (navigation, gestures, visual layout), and concrete page components (bars, views, controls). Use the diagrams below as a guide.

Design Philosophy

iOS HIG emphasizes clarity, consistency, and direct manipulation, while Material Design focuses on material metaphors, depth, and meaningful motion.

Basic UI Guidelines

Both specifications cover navigation (hierarchical, flat, back‑button handling), gestures (tap, swipe, long‑press), color usage (iOS prefers restraint, Material Design uses vivid contrast), and motion (Material Design defines four animation patterns with recommended timing).

Page Components

Components are grouped into bars (top, bottom, side), views (content and temporary), and controls (buttons, switches, sliders). The article illustrates each category with screenshots of iOS HIG and Material Design examples.

Learning Tips

Read the specifications thoroughly at first, then treat them as a reference dictionary when designing. Apply the guidelines where appropriate, but also consider context‑specific solutions and innovate beyond the standards when they add value.

Conclusion

The two system‑level specifications provide design philosophy, interaction knowledge, decision‑making criteria, and creative inspiration. Study them systematically, use them as a reference, and balance adherence with innovation to create superior user experiences.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

Material DesignUI/UXiOS HIG
VMIC UED
Written by

VMIC UED

vivo Internet User Experience Design Team — Designing for a Better Future

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.