Platform Integration

10 documents

App Intents

Expose key app actions and data as App Intents so Siri, Shortcuts, Spotlight, widgets, and the system can invoke them.

swiftiosmacos

Background tasks

Apps that sync data, process uploads, or maintain state SHOULD use platform background execution APIs rather than relying on foreground presence.

iosmacosandroidwindowsweb

Deep linking

All significant feature points and views MUST be deep linkable using the platform's native URL/deep link mechanism:

kotlinswifttypescriptwebwindows

Handoff and continuity

Apps available on multiple devices SHOULD support continuity features so users can start work on one device and resume on another.

iosmacosandroidweb

Notifications

Apps SHOULD use the platform notification system for timely, actionable alerts that respect user preferences.

iosmacosandroidwindowsweb

Scriptable and automatable

Components and flows SHOULD be scriptable where the platform supports it:

csharpioskotlinmacosswiftwebwindows

Search integration

App content SHOULD be discoverable through the platform's system search, enabling users to find content without opening the app.

iosmacosandroidwindowsweb

Share and inter-app data flow

Apps SHOULD participate in the platform's share and inter-app data exchange mechanisms to integrate with other apps and workflows.

iosmacosandroidwindowsweb

Use AppKit and UIKit, not SwiftUI

Use AppKit (macOS) and UIKit (iOS) for all UI. Use SwiftUI only where Apple requires it.

iosmacos

Widgets and glanceable surfaces

Apps with time-sensitive or frequently checked data SHOULD provide widgets and glanceable surfaces on platforms that support them.

iosmacosandroidweb