It all depends on what you are developing/have developed, the want and need for this app/technology, and how bad someone else wants it along with the target market.
I like the topic of this thread because this very same thing has happened to us (as a company). As the sole electronics engineer and developer at my company, we manufacture standard static LED scoreboards and video/virtual scoreboards out of LED signs.
We have scoreboards of all sports, controlled by tablets or "consoles" running on raspberry Pis, as well as full video displays with virtual scoring, head shots, quick hits/plays that can be shown with a touch of a button, as well as live Ad sequencing, sponsor playlists, etc that you see going on professional sports stadiums. The beauty of all of this? B4X powers it all!
Our entire architecture is powered by B4X, with the exception of the LED Driver cards running a microcontroller, I wrote that using a different compiler (BASCOM-AVR) but the syntax is similar. (Had to invent a protocol to get those two systems to talk to one another. B4X and BASCOM). I wrote that firmware long before B4J and B4R. (late 2012)
As I said, I think its all about the target market and who wants it bad enough. Even with that, Another company offered us 1.4M USD (only a year into business, as a startup) plus earnout. They were fully aware of the source code being in BASIC, as well as B4X. They did not care.
We turned it down because we were only a year old at the time, and thought we could grow and be worth alot more. And this was well before I had developed the video scoreboard architecture. We only had static standard LED digit scoreboards at the time.
It turned out to be the best decision as we have grown alot in the years since and worth exponentially more as we have increased sales volume, and service/support angles. And then with the invention of "ABMaterial" and MQTT Libraries, it has broadened our horizons even more for our customers, such as the ability to distribute live scores from our controller app, through to our client apps, and customers via a web portal.
Heck, even with the MQTT library, I took advantage of it so coaches/officials can control the Play Clocks, as well as the main clock from the field back to the controller tablet! I think B4X and this stuff is all badass as it gave us the ability to "get the job done" with relative ease.
As I said, it all depends on what it is, the market, and who wants it bad enough.
That is my 2 cents. If anyone cares to, here is a link to our facebook and the projects we have done: https://www.facebook.com/majordisplay/
I like the topic of this thread because this very same thing has happened to us (as a company). As the sole electronics engineer and developer at my company, we manufacture standard static LED scoreboards and video/virtual scoreboards out of LED signs.
We have scoreboards of all sports, controlled by tablets or "consoles" running on raspberry Pis, as well as full video displays with virtual scoring, head shots, quick hits/plays that can be shown with a touch of a button, as well as live Ad sequencing, sponsor playlists, etc that you see going on professional sports stadiums. The beauty of all of this? B4X powers it all!
Our entire architecture is powered by B4X, with the exception of the LED Driver cards running a microcontroller, I wrote that using a different compiler (BASCOM-AVR) but the syntax is similar. (Had to invent a protocol to get those two systems to talk to one another. B4X and BASCOM). I wrote that firmware long before B4J and B4R. (late 2012)
As I said, I think its all about the target market and who wants it bad enough. Even with that, Another company offered us 1.4M USD (only a year into business, as a startup) plus earnout. They were fully aware of the source code being in BASIC, as well as B4X. They did not care.
We turned it down because we were only a year old at the time, and thought we could grow and be worth alot more. And this was well before I had developed the video scoreboard architecture. We only had static standard LED digit scoreboards at the time.
It turned out to be the best decision as we have grown alot in the years since and worth exponentially more as we have increased sales volume, and service/support angles. And then with the invention of "ABMaterial" and MQTT Libraries, it has broadened our horizons even more for our customers, such as the ability to distribute live scores from our controller app, through to our client apps, and customers via a web portal.
Heck, even with the MQTT library, I took advantage of it so coaches/officials can control the Play Clocks, as well as the main clock from the field back to the controller tablet! I think B4X and this stuff is all badass as it gave us the ability to "get the job done" with relative ease.
As I said, it all depends on what it is, the market, and who wants it bad enough.
That is my 2 cents. If anyone cares to, here is a link to our facebook and the projects we have done: https://www.facebook.com/majordisplay/
Last edited:
