Ming;
The key is the “iOS: Supported Bluetooth profiles”, identified on http://support.apple.com/kb/HT3647.
These Bluetooth profiles are available to all iOS developers, without any requirement for a MFi license.
These are “Bluetooth v2.1+EDR” profiles (what Jeff is calling “classic Bluetooth”)… not Bluetooth LE.
Bluetooth devices that implement these “iOS-supported” profiles can communicate with relevant iOS facilities on an iOS device. This allows communications between the Bluetooth device and built-in apps included with the iOS operating system. However, these “classic Bluetooth” profiles don’t allow allow any direct communication between the Bluetooth device and user-developed apps.
With CoreBluetooth, Apple has provided a mechanism for iOS apps to communicate directly with Bluetooth LE devices, but this is independent of the “Bluetooth v2.1+EDR” (“classic Bluetooth”) functionality.
If you want to develop a Bluetooth accessory that requires performance or features that can’t be accomplished with Bluetooth LE, and that must communicate directly with a user-developed iOS app, then the accessory must be developed and manufactured under a MFi license agreement.
Regards,
Mark
From: ming huang [mailto:email@hidden]
Sent: Tuesday, November 20, 2012 10:17 AM
To: Mark Davis; email@hidden; email@hidden
Subject: RE: iOS6 access to SMS, email, and call notifications using Bluetooth Smart / BLE
Hi,
Now I got confused about the point 5:
- Mark clearly stated that if you are a iOS 6 developer and not a MFi licensee, you can use MAP.
- Previous emails by other people stated, but not specifically said, that if you are not a MFi licensee, then you cannot use MAP.
Would you please confirm which of my two understandings is correct?