Is there any chance thas this library will reach stable version?

[arbonvata]

It has been on alpha mode for a while now.

[philips77]

Hi,
My point is not to change the API too much after it reaches stable version. I'm trying to migrate some of our apps and libraries to find any potential issues and possible API improvements.
Some APIs that work in one scenario may not be sufficient in another. Looking at the lib, I'd say the BLE-related API should not change anymore, but I'll know for sure when I migrate the nRF Blinky (in progress) and nRF Connect Device Manager (not started). The latter one uses "connect on call", rather than "connect before" so I'm intersted how well the migration will go.

Anyway, the only possible API change I see now is related to logging, something like adding a log listener instead of relying on SLF4J. That way users can choose desired log level and we could use lazy logging for better performance. Also, as of now, if you have multiple peripherals connected, the logs are a mix of everything.

If would gratly help if you could start migrating your projects or at least experimenting with this alpha and help finding any issues. Much appreciated!

[cullub]

Also interested. We're developing a new Kotlin app and will be choosing a BLE library in the next couple weeks. I don't think I can sell using this library if it's not marked stable though, regardless of how stable it actually is

[arbonvata]

Also interested. We're developing a new Kotlin app and will be choosing a BLE library in the next couple weeks. I don't think I can sell using this library if it's not marked stable though, regardless of how stable it actually is

use kable library.
I do not know what nordicsemi is doing. They had a good library (version 1.x)
which they made obsolete or so. The 2.x job has been on progress for quite long time now.
The second version is also quite heavy to use compare to the first one

[philips77]

Version 1 had some flaws:

• Most of the implementation in a single file,
• Callback-based
• Very difficult to maintain and track bugs, as there were tons of different flags
• No option to mock a connection or add tests
• Only for connections, no scanning / advertising

We aim to fix all of it in v2, but this will take time... sorry :(
We hope to complete the migrations soon and have enough confidence in the API that we will make a stable version.
Just to emphesis, the behavior (BLE) of the lib seems stable already, but we're still polishing some API. For the foreseable future I can only see the logging part changing.

But anyway, Kable is already ready for multiplatform.

[cullub]

Understood, thanks for your work! This is shaping up to be a really clean BLE solution, and that's on a platform where clean and bluetooth are oxymorons.