-
Notifications
You must be signed in to change notification settings - Fork 0
macOS Compatibility
The deployment target is macOS 11.0. Do not raise it to resolve availability errors. Use the best implementation on macOS 12 and later when it improves the product, with a scoped macOS 11 fallback that preserves core data and interaction semantics.
Screen-Remote/MacOSCompatibility.swift centralizes current wrappers: window sizing bridges, app-aware runtime localization, compatible background/overlay helpers, text selection and monospaced-digit fallbacks, and URLSession download fallback. if #available and visual alternatives should remain in this compatibility layer rather than spread through feature views.
- Check the API's macOS availability before integrating it.
- Add or extend a named compatibility wrapper near related wrappers.
- Keep feature code on the unified wrapper.
- Compile/check both the macOS 11 path and the current-SDK path.
Core functionality cannot be removed on macOS 11; modest visual differences are acceptable. Native SwiftUI/AppKit integration belongs in the app, not in Android or dadb code.