Nothing to hand? Load the — hardcoded colors, fixed point sizes and bare tap gestures — the , where the styling is right but the structure is not, or the , which should come back sound.
Paste the SwiftUI
A view, a screen, a component library file, or all of it. The instant prescan reads it for free while you type and lists what it mechanically found: hardcoded Color(red:) values, fixed .system(size:) fonts, deprecated NavigationView, blanket ignoresSafeArea, UIScreen.main.bounds sizing, a plain VStack inside a ScrollView, bare onTapGesture controls, frames under the 44pt minimum the HIG gave at the time of writing, image-only controls with no accessibility label and tab bars past five tabs - plus the View structs and the SF Symbol, accessibility, font and color counts in your paste.
The AI reviews it
A sound/refactor/rework verdict; severity-ranked findings, each quoting the code it concerns and carrying corrected SwiftUI; a twelve-item checklist, drawn from the Human Interface Guidelines as they stood in February 2026, scored pass, fail or not-observable against your paste; and an honest health check across layout and adaptivity, typography and Dynamic Type, color and dark mode, navigation and structure, and accessibility. Every prescan hit is confirmed or explicitly set aside — including the false positives.
Take the rewrite and go
Your own code refined — same screens, same intent, semantic colors and fonts, SF Symbols, real Buttons with accessibility labels, NavigationStack, lazy containers, larger touch targets, safe areas restored — shown as a line diff against your own paste so you can see exactly what moved, with a one-click “use as input & re-review” loop that compares the next run against this one. Plus a downloadable Refined.swift, the ordered next steps, the findings as CSV, review history on your account, and Markdown or JSON export.
Derived from the @wshobson/mobile-ios-design skill (MIT).
Is HIG Lens made by Apple, or affiliated with Apple?
No. HIG Lens is an independent tool published on SkillSafe and derived from the open-source @wshobson/mobile-ios-design skill. It is not affiliated with, authorised by or endorsed by Apple Inc. “Apple”, “Human Interface Guidelines”, “SwiftUI” and “SF Symbols” are trademarks of Apple Inc., used only to describe what the tool reviews.
Does passing this review mean my app will be approved by App Review?
No. This tool makes no prediction about App Review, and a clean result is not an approval signal of any kind. App Review applies the App Store Review Guidelines, which are a separate document from the Human Interface Guidelines and are assessed by Apple against your built, submitted app — not against a paste of source code.
How current is the guidance? The HIG changes with every OS release.
The rules, thresholds and checklist in HIG Lens reflect the Human Interface Guidelines and SwiftUI practice as of February 2026. They are guidance as of that date, not settled fact. This app runs under a strict content security policy and cannot fetch the live guidelines, so it cannot tell you when a rule has moved. Always check anything load-bearing against the current Human Interface Guidelines at developer.apple.com, which govern.
What does the free prescan do, and does my code leave the browser?
The prescan is pattern matching that runs entirely in your browser: it flags HIG smells such as hardcoded colors, fixed font sizes, deprecated NavigationView, ignored safe areas and small touch targets, lists the View structs it found, and never sends anything anywhere. The paid review is different — pressing Review it sends your code to the SkillSafe API, and so does the live price estimate that updates as you type.
What do I get back, and can I apply the fixes directly?
A sound/refactor/rework verdict, a five-area design health check, severity-ranked findings each quoting your code and carrying corrected SwiftUI, a twelve-item checklist, a reconciliation of every prescan hit, and a full refined rewrite of your file. The rewrite is shown as a line diff against your own paste so you can see exactly what moved, each finding has a Copy fix button for the snippet alone, and Use as input & re-review loads the rewrite back into the form for the next pass.
Does it cost credits, and what happens if I run the same code twice?
Runs are metered and priced per run; the estimate shown before you press Review it is the amount reserved, and you are charged only what the run actually uses. The prescan, the diff, the exports and replaying a bundled example cost nothing. Running the same code again is treated as a deliberate new review and is billed as one — it is not silently deduplicated against your earlier result.