ios-interface-polish

Files (1)

• SKILL.md

SKILL.md (first lines)

# iOS Interface Polish

Polish is usually not a big redesign. It is a series of small corrections that remove friction and visual hesitation.

## Use This Skill For

- screens that feel flat, noisy, or slightly awkward
- controls that work but do not feel tactile
- cards, rows, sheets, and grouped settings that need refinement
- SwiftUI interfaces that feel web-shaped instead of iOS-shaped

Use after the screen works. For information architecture, feature requirements, accessibility compliance, or motion behavior, use the corresponding specialist skill first.

## Polish Rules

- make spacing feel intentional, not evenly distributed by default
- keep nested corner radii visually related
- align icons and text optically, not only mathematically
- use semantic hierarchy before adding more color
- prefer one clear emphasis point per section
- keep shadows soft and sparse
- use tabular numbers for changing totals, prices, and stats
- make touch feedback subtle and consistent
- preserve the motion decisions already established by `ios-motion-and-microinteractions`

## Common Fixes

- reduce visual clutter before adding styling
- turn hard dividers into whitespace when the layout can support it
- tighten row layouts so labels and values read as pairs
- remove one-off font weights, opacities, and radii that weaken consistency
- make exits calmer than entrances

## Native Feel Checks

- does the screen still feel clear in dark mode?
- do large numbers stay aligned while changing?
- do grouped sections read like Apple settings, not dashboard cards?
- does pressing a control feel acknowledged immediately?
- is animation fast enough that it never feels like waiting?

## Avoid

- decorative gradients on utility screens
- thick borders everywhere
- overusing haptics
- scaling or bouncing every interaction
- using visual polish to mask unclear behavior or inaccessible interaction

From phrypy/ios-app-playbook, MIT.

More from phrypy/ios-app-playbook