Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

All Bluetooth chips come with SDKs and depending on your solution another API in the OS of your board. At that point clients don't need to know much about bt and from my experience don't care beyond "how do I make these bytes appear on the other side".

BT is massive but that's mostly BT classic which is slowly going away as more and more chips are BLE only which is saner. That's why we're adding isochronous channels to keep it interesting.



> Bluetooth chips come with SDKs and depending on your solution another API

Yup and a simple embedded version of a useful subset of that is (just counted) about 4000 non-comment non-blank lines _just_ for the header files.

And assumes you then understand what the API does which is probably less comprehensively documented than the underlying HCI spec.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: