Skip to content
design:os / apple

Native SwiftUI · iPhone / iPad / Mac

Layered kit on main

From component
to complete screen.

One considered design language.
Reusable layers. Unmistakably native.

Explore the kitSee real screens
Actual native kit captures showing reusable screen compositions across Apple platforms
Built with the kit. Captured natively.Historical adcf88a · View evidence
Framework
SwiftUI + Swift 6.2
Minimum platforms
iOS 17 · iPadOS 17 · macOS 14
Package dependencies
Zero external
License
MIT, open source

A shared visual language

The details belong together.

Images, surfaces, type, and actions share a system. Navigation, input, focus, and presentation stay native.

Geometry

Soft corners.
Precise relationships.

Continuous image corners and genuinely concentric insets. Nested radii follow the actual padding, rather than a collection of unrelated values.

Read the corner contract
Appearance

One theme.
Every surface.

An opt-in editorial style shares palette, typography, and metrics. System, light, and dark choices stay coherent across the app’s screens and presentations.

Explore the application style
Interaction

Full-pill actions.
Real native controls.

Capsule styling follows the height of real buttons, including multiline labels. Your app owns actions, disabled state, routing, and data.

Explore ownership boundaries

Swift Package Manager

Start with the
right revision.

The layered kit is now merged into main. Pin the reviewed source below, or browse all 142 current native previews in the complete component catalog. The six overview images retain their historical adcf88a source.

Read the kit guide

Already using the core library? Keep the main quickstart.

Package.swift · reviewed sourceView source ↗
.package(
  url: "https://github.com/jangtrinh/design-os-apple.git",
  revision: "1898ce28861d642f57dccd88fd57afcbe3be5bb9"
)

// Add this product to your app target:
.product(name: "DesignOSApple", package: "design-os-apple")

Swift 6.2 and an Apple SDK are required to compile SwiftUI. No DESIGN:OS maintainer tooling is required by consumers.

A composition system

Build up. Keep ownership clear.

Begin with a semantic component. Reuse a composition. Choose the shell and screen type that fit your app.

  1. 01

    Primitives

    Finite geometry, media clipping, and adaptive placement.

    3 new internal helpers
  2. 02

    Semantic components

    Meaningful media, identity, labeled values, and status.

    4 new public APIs
  3. 03

    Composites

    Reusable groups with caller-owned content and action slots.

    11 new public APIs
  4. 04

    Shells

    One clear container, scrolling, and safe-area policy.

    9 new public APIs
  5. 05

    Screen types

    Named task hierarchies assembled from the same lower layers.

    18 new public APIs

42 additive public APIs, plus 4 native or existing-component recipes. Historical additive counts describe the adcf88a source, not complete app flows. Inspect the machine-readable index.

Your app stays your app.

  1. Choose the surface. Start with the screen family that matches the task.
  2. Inject the style. Apply the shared app style once at a product boundary.
  3. Connect real behavior. Supply your models, native controls, routes, and actions.
See the existing core library’s first SwiftUI view

This core example is kept in parity with Getting Started. It is not a demonstration of every kit layer.

import DesignOSApple
import SwiftUI

struct AccountList: View {
  var body: some View {
    List {
      DesignOSListRow {
        Label("Profile", systemImage: "person.crop.circle")
      } title: {
        Text("Account")
      } subtitle: {
        Text("Manage identity and sign-in")
      } trailing: {
        Image(systemName: "chevron.forward")
          .foregroundStyle(.secondary)
      }
    }
    .designOSProfile(.default)
  }
}

Full main-branch setup instructions ↗

A visible proof boundary

See what passed.
Know what it proves.

Evidence is bound to a revision. It describes this run, not a promise that every scenario or reference state is finished.

Native UI execution

CalorieCam 10/10 and kit 9/9 on each of iPhone, iPad, and Mac. All eight jobs passed in CI run 38087127370.

Source-bound captures

108 family captures retained from native execution. The gallery selects from those artifacts; asset provenance records source filenames and transformations.

Package verification

173 reported package tests, with the genuine high-contrast fixture skipped. Portable documentation checks complement, rather than replace, Apple SDK verification.

Research coverage

393 reference states mapped. This is a research inventory, not 393 completely rebuilt or visually accepted screens.

Read the proof & provenance notes

Before you build

A few good questions.

What is Apple Design OS?

Apple Design OS is a zero-dependency SwiftUI design system for iOS, iPadOS, and macOS. Its layered kit adds reusable semantic components, composites, shells, and screen types while keeping native controls and application state in the consuming app.

Which platforms and toolchain does it require?

The package requires Swift 6.2, iOS 17 or later, iPadOS 17 or later, and macOS 14 or later. It uses Swift Package Manager and has no external package dependencies.

Is the layered kit available on main?

Yes. The layered kit was merged into main in PR 3. The component catalog is pinned to tested revision 1898ce28861d642f57dccd88fd57afcbe3be5bb9; merged main has the same source tree. Use main or pin that revision. No version tag is claimed.

Does the catalog show every component and state?

The catalog lists 99 source entries and 160 token values. It displays 142 native iPhone images across 71 visual entries, with light and dark previews. The remaining source helpers have explicit coverage notes. Selected previews do not establish complete behavior or every state on every platform.

What has been verified, and what is still open?

Native CI run 38157622095 passed all 23 workflow jobs at revision 1898ce2. The reviewed capture set contains 360 isolated components, 108 screen-family fixtures and 42 dedicated text-field states across iPhone, iPad and Mac. The overview images retain their historical adcf88a provenance. Live services, physical-device behavior, complete accessibility acceptance and performance remain outside these claims.

The DESIGN:OS ecosystem

Intent to implementation.

Independent tools for managing design intent, working in Figma, and publishing the work.

DESIGN:OS CLIMulti-runtime design CLI for Claude Code, Codex & Antigravity ↗Knowledge BuilderMultimodal knowledge compiler with UKMC.v1 contract & epistemic gate ↗Figma Plugin & CLILive canvas bridge for AI coding agents on Figma Free ↗SVG Animation EngineDeterministic vector animation & 1080p 60fps video pipeline ↗3D Blender AgentMechanical parts generation with embedded Three.js CAD viewer ↗OPAH ONE249g indoor drone showcase with scroll-scrub kinematics ↗GitHub Pages Engine9-tier zero-dependency scaffolder with SEO, AEO & GEO ↗Agent TeacherEvidence-graded pedagogy library and curriculum tree runtime ↗Origami CADParametric packaging dielines, spot-color PDFs & 3D fold previews ↗Voice UX & AI Agent ArchitectureFull-duplex barge-in FSMs & sub-500ms voice specs ↗Code2FlowLocal-first codebase-to-user-flow audit CLI across 7 UI frameworks ↗Generative UIStreaming interactive visual runtime with morphdom & WebGL ↗

Keep going

Start small. Use the parts that earn their place.

Add the package