> Intro:
>
> We see all of the time the assumption that parity should be found across native and web platforms. We assume that we’re building the same product regardless of surface, but we don’t consider each platform's strengths and how we should be leveraging them better.

This is: *an attempt to draw a distinction between native and web platforms, considering what they’ve been best at historically.*

### Native apps: For using

* Interactivity: Native apps should emphasize interactivity, where users are actively engaged in performing tasks, manipulating content, or interacting with app functionalities.

* Utility and Productivity: Native apps should be built around specific utilities or productivity goals. Users don’t just consumer content; they create, modify and control it.

* Personalization: Native apps should leverage personalization to make the user’s interaction with the app more tailored an experience to better suit the user’s needs.

* Immediate and Quick

### Web apps: For consuming

* Information and Content Consumption: Websites traditionally have been used for reading, watching or listening to content (news, blogs, youtube, etc.)

* Accessibility: Websites are easier to access — just type in the url — so that makes it ideal for quickly finding information and consuming media.

* Interactivity and Engagement: While websites are often used for consuming content, we’re trending more app-based which is allowing us to blur the lines between native and web platforms and design with more parity in mind (tho the way we interact with native and web apps is still quite different and maybe that is worth discussing more — gesture based, context based interactions depending on the device you’re looking at your content on ?)

* Long Form and Complex

Native v Web (Rough Draft)

On Interaction

On Fluidity

On Flexibility

On Simplicity

On Design

Building Design Systems

Designing for Native vs Web

Component Documentation Example

Interactive Design Specialist

Atlas Web 🤝 Native Library merge

Year 0-2

1. Defined core primitives

2. Released v1.0 of Atlas for iOS and Android

3. Drove design and engineering adoption

4. Created and maintained system documentation

Milestone — 💠 Atlas Design System (Native)

Redesign of core user account screens on iOS and Android
- Rethought IA and UX to future proof scalability
- Built in tandem with a young and emerging design system to scale and iterate in shorter and faster cycles

Native Account redesign/launch

Atlas Component design decisions + on canvas documentation examples.

Storytelling: Atlas Row

Building v2.0 of Atlas, pushing Native-first practices and developing a new dynamic system for design and engineering to tap into as the needs of the system evolves.

Atlas 2.0

Migrated Figma color styles to variables and sync'd to GitHub to streamline design and dev parity between variables and tokens.

* Created scalable primitives variables (color, number)

* Created Atlas decision variables referencing primitives

* Promoted feature team adoption of Atlas variables and created a system for teams to make custom variables based on local requirements

Primitive + Decision Tokens

AtlasBot is an AI-powered design assistant that helps Experian's UX team make smart choices with Atlas components. It analyzes designs, offers tailored suggestions, and keeps the team's work consistent and efficient.

AtlasBot

Year 3

1. Continued growing/shipping new components and patterns

2. Full adoption of base, decision and component tokens

Dynamic Type Scale

Headless DS

Rebuilding components from native apps I regularly use in Figma and SwiftUI

SystemUI

Gradient_

Account Manager

Led the redesign of core app features and surfaces such as the dashboard, credit scores and reports and user account screens

Senior Product Designer

Lead Product Designer

* Maintains and enhances cross-platform Atlas component and pattern libraries in Figma.

* Works with cross-platform engineering teams to develop components based on detailed design specifications.

* Collaborates frequently with feature teams to solve real pain points while driving system adoption.

* Writes detailed design documentation to support both design and engineering teams as they use the Atlas system.

* Prioritizes accessibility and ensures inclusive experiences across all platforms.

Caleb Hill

2024