Beyond Aesthetics: What a Visual Language Actually Does
Graphic user interfaces are built from the same raw materials a writer assembles into prose: fonts, colors, shapes, and symbolic elements like icons. When those materials are organized into a deliberate, unified system, they become a visual design language — the medium through which a product communicates with its users. And like any language, it only works when everyone involved speaks the same version.
That was the challenge facing the design team at Fantasy in 2016. Tasked with building the interface for Huawei’s mobile operating system (EMUI 5), they discovered the client had no coherent visual language of its own. Instead, Huawei had been shipping a customized Android skin shaped by multiple teams — UX, interaction, visual, and graphic designers — each working from their own internal assumptions. The result was an OS that felt inconsistent to users and was nearly impossible to iterate on internally.
Despite the wide range of skill sets producing the work, there was no shared framework for making decisions. That inevitably led to a jumbled user experience and a design pipeline where integrating changes was cumbersome and slow. The project was, in effect, a Tower of Babel — not for lack of talent, but for lack of a common tongue.
Why a Unified System Matters
When an entire product team adopts one visual design language, projects move with greater clarity and speed. But the benefits extend well beyond the development pipeline.
Consistency Across Platforms
Digital products face fewer physical constraints than industrial design, which gives designers wide latitude to experiment. That freedom comes with risk: without guardrails, each screen or component can drift toward its own ad-hoc solution. For companies shipping across multiple devices and platforms, that’s a particularly acute problem.
The solution is a set of defined, reusable components and styling patterns that can be deployed consistently. A disciplined system makes it far easier to roll out a polished product across a sprawling family of devices — a critical requirement for a company like Huawei.
Memorable Brand Identity
Users naturally remember products with a distinct visual voice. Much of today’s mobile software, however, looks strikingly similar, making one product easily confused with another. Establishing a definite visual identity — the colors, typefaces, imagery, and motion that give a product personality — is a goal design teams should state explicitly.
That is what builds brand recall. If the same visual principles are followed rigorously across the entire ecosystem, users begin to recognize the product even without a logo.
Clarity and Focus
For the Huawei OS project, the Fantasy team made clarity a core objective. Instead of piling features and controls onto each screen, they adopted a minimal approach. By actively reducing the number of elements per view, they produced an interface that was more focused and less visually crowded, creating a calmer and more efficient experience for users.
A Practical Innovation Channel
In a crowded smartphone market, marketing can only do so much to differentiate one product from another. Companies pour resources into novel features to spark consumer interest, but visual design is one of the fastest and most economical opportunities to change a product’s character in a way users perceive right away.
Building a Visual Design Language: A Case Study in Process
Creating a visual design language (VDL) is a complex, multi-stage effort. Treating it as a product itself — with research, ideation, testing, and implementation — is the most reliable way to ensure it meets the needs of both the brand and its users. The following outlines a systematic approach, illustrated through a major mobile OS redesign project.
Phase One: Research and Discovery
The UI Audit
Consistency is a primary goal of any shared design language, making a thorough audit of existing visuals essential. The process begins by deconstructing the entire interface into atomic elements: colors, shapes, shadows, lines, and transitions. Dissecting the current design this way reveals how individual components interact to create a cohesive whole. Once the audit is complete, all components — buttons, navigation bars, icons — are grouped into distinct categories, providing a foundational inventory for the new system.
Defining User Perception
A successful VDL requires aligning brand identity with user perception. To achieve this, it is crucial to categorize the target audience and create detailed summaries for each segment. These summaries should contain demographic data, user values, and expectations. For instance, one target group might be characterized as urban and suburban dwellers aged 30–64, driven by efficiency and productivity, and looking for tools that contribute to a sense of order and personal organization. Such profiles provide clear reasoning behind every design decision.
Competitive Landscape Analysis
Analyzing competitors with strong design languages helps identify strategic opportunities. Evaluate each competitor’s language to pinpoint its distinguishing strengths and weaknesses. For example, one major platform may be praised for its scalability and standardization but criticized for iconography inconsistencies. These analyses can be plotted on a matrix that defines four major strategic directions: design that is empathetic and tailored to the user, novel design that uses innovative patterns, commonplace design that relies on conservative styles, and heavily standardized design for all.
Plotting competitors on this matrix highlights market gaps and clarifies a new language’s positioning. This process typically yields a set of clear opportunities, such as:
- Scalable Design Language: The new system must work seamlessly across hardware and third-party developer ecosystems.
- Unique Design DNA: The visual identity must be distinct from the major players in the market.
- Bold Yet Timeless: The language should feel current but be built to last.
User Requirements for Interaction
User research often reveals critical friction points with existing interfaces. A common complaint in older mobile systems was the placement of key interactive elements at the top of the screen—an area difficult to reach on increasingly large displays. Presenting this data to the engineering team is a vital step to assess the technical feasibility of moving primary controls to the bottom of the screen, an area that is far more ergonomically friendly. Securing this confirmation early in the process allows you to define new standards for element placement with confidence.
Phase Two: Ideation and Vision
Creating a Design Philosophy
When designing a language intended for worldwide use, you must consider the psychology of perception and the cultural neutrality of shapes and forms. Finding the right philosophical foundation is a challenge best tackled collaboratively. Leading to a focus on a philosophy of organic design, which draws inspiration from nature to create harmony between the user and the digital environment. This translates into a design system where visual elements like buttons, icons, and shapes adopt smooth curves and natural forms.
Motion as a Defining Feature
Motion design plays a dual role in mobile UI: it is functional, providing feedback for user actions, and it is emotional, making the interface feel alive. A robust motion design philosophy prioritizes creating “magical moments” that surprise and delight users, as initial impressions are crucial for product adoption. Every animated transition should be evaluated for the functional and emotional benefit it brings to the end-user experience.
Phase Three: Design, Testing, and Iteration
Establishing Visual Semantics
Efficient visual communication relies on a strong semantic framework, where components have clear meaning. To achieve this, two rules must be internalized by the design team:
- There are no random visual elements in a visual language. Every element serves a purpose.
- There should be no isolated units in a visual language. Every unit should be a part of a greater whole.
Iterative Review and Refinement
Great design never happens in a first attempt. The design process is necessarily iterative. Proposed solutions must be evaluated by placing new screens side-by-side with previous iterations on a board. This allows the entire team to visually identify what requires additional polish. These informal design reviews are where the pros and cons of distinct solutions are discussed, ensuring the final direction is the strongest collective choice.
The Role of Pattern Libraries
Pattern libraries, style guides, and written design principles form the foundation of a shared design system. They ensure that any team member—new or existing—can work on the project while maintaining consistency. The initial UI audit is invaluable here, as it has already categorized the key components into an accessible toolbox that can be used by everyone involved in the implementation process.
Validation Through Rapid Testing
For a flagship project, validating the design language with users as early as possible is non-negotiable. The build, measure, learn cycle is highly effective. By incorporating the new visual language into functional prototypes and testing them both internally (dogfooding) and externally with real users, the team can gather crucial feedback to understand what works and what doesn’t, long before the final release.
The Implementation Challenge
A common reality in large-scale corporate projects is the disconnect between the design team and the final implemented product. Often, a significant number of proposed solutions are not implemented properly by the engineering team, or are dropped entirely. When the designers who created the language are not part of the implementation loop, the engineering team often takes the path of least resistance, compromising original design solutions to fit technical constraints.
Overcoming this requires a senior manager who champions the design vision and is willing to fight for it. A well-documented instance is the macOS minimize animation, which engineers initially claimed was impossible to build. The insistence of the company’s leadership on keeping that feature resulted in one of the most memorable and praised transitions in the product, proving that when product leadership pushes back, great UX outcomes are achievable.
Design Language as Product
A robust visual design language has a dramatic impact on user experience. It reduces friction by making interfaces predictable and creates delight through considered details. This pairing of form and function is the essence of excellent user experience. Treating the visual language as a by-product that requires its own iterative product lifecycle—with validation at every step—establishes a new ecosystem that creates harmony across different product teams.
