Core Bluetooth, nearby interaction, accessories, and connectivity
Nearby hardware is an unreliable distributed system with radio state, discovery, pairing, transport framing, firmware variation, permission, and physical proximity.
Design the capability
- Model unavailable, unauthorized, powered off, scanning, discovered, connecting, ready, reconnecting, failed, and disconnected states.
- Bound scan duration and filter by service. Stop work when the feature or app lifetime ends.
- Bluetooth characteristic updates are transport chunks, not guaranteed application messages. Define framing, versioning, checksums, and retry.
- Keep Core Bluetooth, Nearby Interaction, and accessory APIs behind capability adapters with deterministic protocol fixtures.
Validation boundary
No Bluetooth radio, nearby token exchange, accessory program, entitlement, firmware, packet trace, or physical-device recovery test occurred.
Series navigation
- Previous: Part 103: Video capture, editing, playback, and streaming architecture
- Next: Part 105: HealthKit, WorkoutKit, and health-data design
- Series index: Zero to iOS Hero