Other Should we create a new Bluetooth/IoT Library using the community


Licensed User
Longtime User
I am a fan of BASIC (for over 35 years) and am deeply hands-on involved in Bluetooth Technology.

I was responsible for one of the first Bluetooth easy-to-use modules back in the early 2000s.
Since then, I have developed many BT modules and then 3 years ago started working on a BLE module, the culmination of which is www.lairdtech.com/bl600

This latest BL600 module has embedded BASIC which we call smartBASIC which was developed from scratch and I was the lead engineer on that too.

It is an implementation of BASIC that runs in less than 2K of ram.

Like B4x, smartBASIC is extensible and the BL600 module has a very rich set of functions that expose BLE functionality.
We also have a new dual mode module BT900 that has both classic and low energy extensions.
Give the modules BL600 or BT900 a go and you will be able to create any smart peripheral you want, including ones with custom services.
Both modules have the same BLE extensions to make it easy for our customers to migrate from one to the other.

Imagine, recreating a similar API on B4x !!

I have over 30 years of 'C' experience but very little experience of Objective-C or for that matter Java.
I also have 14 years of embedded Bluetooth experience and to make it so that it is easy to use.
It means, I can help define the API by 'creating and owning' the .h file that specifies the API and the community can write the code behind it and we manage the process via GitHub.
By defining the API based on field experience of our BLE module, we will ensure the API does not paint itself into the corner and in fact will be future proof so that when IoT using BLE explodes in a big way late next year we will be able to enhance the api for that too.

If a core set of contributors are up for it, I am prepared to sit down and create the 'spec' by writing the .h file.

Some will say, how do we test it ?

Two options :

One is to use iOS apps like 'LightBlue' which allow the phone to become a peripheral device - but it slightly limited.

The other is to get your hands on the Laird BL600 or BT900 module devkit -- I make no promises but depending on the level of interest I will see if I can negotiate a discounted price with my management for contributors.

I think this is an exciting win/win/win proposal for all, and that includes Erel :)

I look forward to your feedback.