Here's a good article on HomeKit: http://www.eetimes.com/document.asp?doc_id=1327267&_mc=NL_EET_EDT_EET_review_20150801&cid=NL_EET_EDT_EET_review_20150801&elq=b50dbce98eb74bd289cd4502ea841759&elqCampaignId=24189&elqaid=27320&elqat=1&elqTrackId=c63c3131d4974e4c81b595d34af817b2
It's my understanding that the auth chip is only used to verify that the end-device is Apple-compatible.
Detailed discussion of which types of non-iOS applications are supported within the Apple ecosystem may fall a bit outside of the scope of the forum, but we'll see what others have to include on this subject.
We support HomeKit via a separate SDK that is handled (distributed and supported) outside of the main forum here.
If you are interested in obtaining access, please update your profile to reflect the name of the company (and email address; free email services violate our registration policy) your MFi license is registered under and send an email to GregG_16. He will then verify the account vs. the Apple MFi DB and provide the necessary access.
thanks for your prompted response. I must admit that I'm already aware of these details.
What I'm not so sure about is the user-experience aspect of it.
My understanding is that it would be possible to "program" your iOS device to interact with your end-device.
And my question is whether this type of programming can be done *without* any iOS specific code.
( I.e. maybe some sort of WSDL ? ).
I'm aware that this question might be beyond the scope of this forum.. but I'm just trying to figure out
"what is means to be an Apple MFi" device in the Apple ecosystem.
( I'm trying to see if that would be the "thing" that would make a better user experience or not.. )