Here are all the useful guides for using AbleLib in your app.
Working with AbleLib requires you to obtain a licence key. Learn how to to get one here.
AbleLib tries to keep all the BLE related-terms under the same, AbleLib umbrella. The basic one is AbleDevice, which is automatically created and managed for you.
Scanning for nearby devices is trivial when AbleLib handles it for you.
Android requires that some devices are paired and bonded before you can use them. With AbleLib, it's a one-line operation.
Once everything is set up, you can communicate with a Bluetooth device. AbleLib handles all the errors, data transfer and retries for you, and - most importantly - makes your code clean and easy to follow.
You can persistently scan and communicate with devices while your app is backgrounded. AbleLib has the toolkit just for that - an Android service or an iOS restoration handler, whichever you need.
AbleLib supports peer-to-peer communication via sockets, which look and work identically on all platforms! You can even create server sockets, that manage channels and allow other devices to connect to yours!
AbleLib allows you to set up and run a local GATT server, allowing you device to behave as if it was a BLE peripheral. Declaratively set your services, characteristics and descriptor and manage incoming requests.
Bluetooth actions in general are heavy on phone's battery, and their operation sometimes needs to be customized to allow for best user experience. AbleLib allows you to customize its quality of service to one best suited to your needs.
AbleLib is built with testability in mind, exposing its main components as interfaces/protocols. This makes it dead easy to inject your own custom or mock functionality seamlessly into any part of the AbleLib ecosystem.
Also, be sure to check out the demo apps: