OS Agnostic Client

  • 1
  • Question
  • Updated 2 years ago
  • Answered
  • (Edited)
I believe its been a while since this topic has come up.  I just thought I'd bring it back to the surface to see if there has been any changes in philosophy.  I'd love to see the client able to be compied and run across multiple platforms.  While the Windows 10 release is really a much better product than anything they have done in the past, I feel far less comfort in my ability to guard my personal information than ever before.  This makes me wish I could move to some flavor of Linux and ditch the Washington based conglomerate forever.  If I could get general releases of the client software from FRS that would run on Linux, I'd sure be a happy camper.

Does anyone know why FRS has tied their client software to tightly to the Windows OS?   Would it have really been that much more difficult to produce an OS Independent Client?

My first thought when Maestro was announced as running Windows, was that FRS had locked in to running their client on the Windows OS forever.  Now that I've had time to think about it a bit further, I don't think that really locked them into anything.  If they wanted to, an OS agnostic client could be developed and placed upon the Maestro just as easily as on any other Windows, Linux, or OS-X driven device.

I then though that many other developers were using the SDI Waveform API and possibly working on clients that would work on other platforms.  The problem with this as I see it is that they will always be way behind the most recent software release from FRS.  So, independently developed client software for cross platform functionality is really rather a poor solution.  They'd constantly be re-engineering the software and an added expense and substantial delay in time. It would be much better coming directly from FRS!

I'm not a software developer.  My intent is not to bash previous corporate decisions.  I'm just curious about the likelihood of FRS producing an OS Agnostic Client in the future.  Is the development overhead really that much grater than developing for only the Windows environment? 

Once again, I'm not a software developer.  I have no idea whats so ever as to how hard this would be to do but isn't relying on calls to forms like .net (just to name one) which are maintained and developed by MS somewhat a moving target!  I would think writing your own code and not have to deal with arbitrary changes made by the OS developer a huge step forward in stability, security, independence and general public acceptance of a product that is cross-platform-independent.

Once again, I'm not trying to stir up trouble, I'd just like to know if this is something that is extremely difficult, or is it something that is within the prospects of future FRS development.

Norm - W7CK
Photo of Norm - W7CK

Norm - W7CK

  • 745 Posts
  • 151 Reply Likes

Posted 2 years ago

  • 1
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9129 Posts
  • 3453 Reply Likes
Official Response
Does anyone know why FRS has tied their client software to tightly to the Windows OS? 

It was a business decision. Desktop OS market share and the real and significant expense to develop, test and document software products were the drivers.  By Windows having a vast majority of market share, creating our initial client software to run on Windows provides the greatest exposure to ham radio market for our radio products (our revenue generator) with the most efficient utilization of our resources, which are not limitless.


Would it have really been that much more difficult to produce an OS Agnostic Client?

Yes. It is more difficult, timely and costly to develop, document and test cross-platform apps using a single code base.