Splunk

Splunk Mobile

A shared foundation for Splunk on mobile.

My role
Mobile design lead
Project period
2019 — 2021
Platform
Mobile / Design systems
Focus
Mobile UX and a shared design language
01 / Problem

Give several mobile projects a common foundation.

I led four mobile projects and developed Splunk’s first mobile design system. The work also extended into illustration and product icons.

Give several mobile products one foundation to build from.Several mobile surfaces are held together by a shared design-system foundation.
Give several mobile products one foundation to build from.
02 / What exists today

Multiple mobile projects needed a shared design language.

The source records the four projects and the first mobile design system. It does not include a detailed inventory of the earlier components or a before-and-after interface comparison.

The mobile projects needed a common design language.Mobile product work, common patterns and visual assets are shown as related areas needing a shared foundation.
The mobile projects needed a common design language.
03 / What’s wrong

Product work alone does not create a consistent family.

Common layouts, icons and illustrations need an explicit foundation. That is the design concern behind this work; the archive does not quantify inconsistency or its effect on users.

A family of products needs more than individually designed screens.An individual screen is separated from the shared patterns needed across the wider product family.
A family of products needs more than individually designed screens.
04 / What I explored

Build the shared patterns alongside the products.

I developed the mobile design system, co-initiated an illustration project and helped unify product icons. The surviving record supports those contributions without documenting every iteration.

Build reusable foundations alongside the products.System patterns, illustrations and product icons appear as parallel contributions to the mobile foundation.
Build reusable foundations alongside the products.
05 / Low-fi architecture

Link shared foundations to individual mobile experiences.

This explanatory model connects the documented system, icon and illustration work. It does not add an unverified alert or incident-response architecture.

System flowHow the pieces connect
Inputs
  • Mobile UX
  • Product icons
  • Illustration language
The interaction
  1. 01Define reusable hierarchy
  2. 02Establish shared patterns
  3. 03Adapt to mobile contexts
Outputs
  • Shared mobile foundation
  • Four mobile projects
  • A connected visual language

A common foundation connects the screens without prescribing an undocumented workflow.

06 / Wireframes

Show how a shared language could reach the screen.

These are reconstructed mobile layout studies based on the documented scope. They are not claimed as original product captures or historical test prototypes.

Wireframe sequenceExplore the sequence
01 / 02

Build a common visual vocabulary

System study / Pattern libraryWireframe
Reusable hierarchy
Title
Content
Action
Component anatomy
Label
Value
Action
01This reconstructed board illustrates the documented design-system contribution, not a recovered library screen.

Reconstructed system study based on the documented mobile design-system contribution; no specific shipped workflow is asserted.

07 / Solution

A mobile system with a wider visual language.

The mobile language extends from interface patterns to visual assets.An explanatory mobile surface brings together shared patterns, illustration and unified icons rather than pretending to be an original screenshot.
The mobile language extends from interface patterns to visual assets.

The work established a shared mobile foundation, with illustration and product icons extending the language across the product family. Original project images can be added to the gallery when available.

08 / Research

The contribution is recorded; usability results are not.

The available material does not include a participant study or measured effect of the mobile system. Consistency, comprehension and reuse would need their own evidence.

These are evaluation questions, not recorded usability results.Open questions ask how consistency, comprehension and reuse could be evaluated for the mobile system.
These are evaluation questions, not recorded usability results.
09 / Outcome

The first mobile design system and a company-wide illustration standard.

The source records that the illustration project became a company-wide standard. My contribution also includes leading four mobile projects and helping unify icons; no delivery-speed or adoption metric is asserted.

The mobile foundation extended into a company-wide illustration standard.The first mobile design system, leadership of four projects and the wider illustration standard are shown as documented contributions.
The mobile foundation extended into a company-wide illustration standard.

Want to talk through the design decisions?

1ONICA FM

Choose a perspective. Access is approved personally.

Public mode is open to everyone. Other perspectives open by invitation.

Level 010 XP

100 XP to the next level

Your progress stays in this browser.