Dear Brian, I can't get anything out of this kind of suggested facts. I would also like to explain to you why.
First you make assumptions, which you then present as facts (DGT collecting mails, etc.) in order to then complain about the content of the assumptions you have made.
As a developer, I am an advocate of the direct hardware API and when the concept of a cloud API was presented to me, I thought about possible restrictions. But in the end I came to the realization that it was an economical solution both for the 3rd party developers and for DGT.
With a cloud API, DGT can avoid or at least make it more difficult to grow wild. DGT has learned from previous projects. A cost factor that the end customer often ignores is support. A company must always include the follow-up costs in the calculation of a product.
When the DGT Pi came onto the market, the end customer could easily swap the SD card and use more engines and other features. A great thing for the end customer, but that also led to customers wrecking their DGT Pi or contacting DGT Support in the event of errors. That makes work. These are follow-up costs.
DGT has learned from this and made it more difficult to make changes at DGT Centaur. In the end, it's about DGT following a concept in its products. High quality products that are consistent and require as little support as possible. DGT prefers to invest the money saved in high quality.
Of course there are also other companies in the chess sector, that calculate exactly the other way around. Instead of investing money in quality, support is being expanded. Due to the poor quality, there are of course more support inquiries, but if a manufacturer produces its products extremely cheaply, it can ultimately be cheaper to exchange a product through support than to offer a higher quality in principle.
DGT has been so successful for decades because they focus on quality. This pays off in the long term.
But back to the cloud API. This also has the advantage that it can be easily expanded. Future products that use the same cloud API will be compatible with each other without a 3rd party developer having to change their code.
Here is a simple example. You program the Cloud API so that the LED on a field on the DGT Pegasus flashes. Now, at some point, a DGT board will come onto the market in which one field has 4 LEDs. As a 3rd party developer, you don't have to reprogram your code. The cloud API ensures that all 4 LEDs light up with your code on the new DGT board.
As I said, this is an exemplary example.
Benny