← ClaudeAtlas

cross-platform-app-development-skilllisted

Use when one Swift/SwiftUI product intentionally targets two or more of iOS, iPadOS, Mac Catalyst, macOS, watchOS, tvOS, or visionOS and needs shared-domain design, adaptive UI, capability boundaries, navigation, input, scenes, storage, or conditional compilation. Do not use for a single-platform feature or for non-Apple cross-platform frameworks.
fal3/claude-skills-collection · ★ 18 · AI & Automation · score 79
Install: claude install-skill fal3/claude-skills-collection
# Cross-Platform App Development Skill Share product behavior and domain logic while preserving each platform's interaction model. “Compiles everywhere” is a starting point, not proof of a good multi-platform experience. ## Stable baseline Primary examples use Xcode 15 and Swift 5.9 with these deployment targets: - iOS/iPadOS/Mac Catalyst 17 - macOS 14 - watchOS 10 - tvOS 17 - visionOS 1 The same architecture can support older systems, but APIs must be checked and gated at the real minimum. `NavigationStack`, `NavigationSplitView`, and `ViewThatFits` begin with the iOS 16/macOS 13/tvOS 16/watchOS 9 generation; visionOS starts at 1.0. OS 27-cycle APIs are beta relative to stable Xcode 26.6 and require explicit user intent, beta labeling, a stable fallback, and availability checks. ## Start with a target matrix Record this before generating code: | Target | Minimum | Window model | Primary input | Navigation | Persistence/sync | Key capabilities | |---|---:|---|---|---|---|---| | iPhone/iPad | project-specific | scenes, multitasking | touch, pencil, keyboard | stack or split | local and/or cloud | cameras, sensors, share extensions | | Mac Catalyst | project-specific | UIKit scenes/windows | pointer, keyboard | split/window-aware | iOS-compatible stores | Catalyst availability gaps | | macOS | project-specific | multiwindow, documents, menus | pointer, keyboard | split, tables, windows | sandbox-aware | commands, files, services | | watchOS | project-specific | glanceab