PUBLIC EXAMPLE · STATIC ANALYSIS ONLY

From finding to revision.

A deliberately constrained SwiftUI control panel, analyzed by the same rules as your source. No account or repository permission needed.

Original fixture

60/100 static score

3 configured rules matched · 1 Swift file scanned

import SwiftUI

struct CaptureControls: View {
    var body: some View {
        VStack {
            Text("Ready to capture").font(.system(size: 14))
            Button("Capture") { }
        }
        .frame(width: 600)
        .ignoresSafeArea()
    }
}

Revised fixture

100/100 static score

0 configured rules matched · 1 Swift file scanned

import SwiftUI

struct CaptureControls: View {
    var body: some View {
        VStack {
            Text("Ready to capture").font(.body)
            Button("Capture") { }
        }
        .frame(maxWidth: .infinity)
        .padding()
    }
}

What the analyzer found

high · CaptureControls.swift:9

A fixed width may overflow a resized scene

Review this constraint. Prefer flexible maxWidth or a container-relative width; verify small windows and large text before changing it.

high · CaptureControls.swift:10

Content extends beyond safe areas

Limit this modifier to decorative backgrounds. Verify interactive content respects each safe-area edge independently.

medium · CaptureControls.swift:6

Fixed font size needs Dynamic Type review

Use semantic text styles or UIFontMetrics. Test accessibility text sizes and wrapping.

What changed—and what remains unverified

The revision removes the fixed width and safe-area override and adopts a semantic text style. A score of 100 means no configured rule matched this fixture. It does not mean the app works on a device.

Both snippets are educational fixtures, not a working camera app. The Capture action is intentionally empty. They have not been compiled or run in Xcode here; there are no device screenshots, runtime assertions or verified fix claims.

Reproduce the static result

The public repository includes these exact fixtures and a test that checks the scores and findings. The report is generated from the analyzer rather than stored as a fabricated customer result.

View the public source fixtures ↗

Recommended next tests · not run

Open the controls in the narrowest supported container.
Use the largest accessibility text size and a long translation.
Show the keyboard and confirm the primary action is reachable.
Implement capture, then verify state across supported transitions.

Get findings from your own source.

Public repositories need no GitHub connection. Private repositories require explicit access. Sign in only when you are ready to submit.

Explore the free layout lab first ↗