ReachView before V2.x.x was open source and can still be run on Reach modules, but many features for Reach RS are not implemented in that version. We plan to support custom apps by releasing an API somewhere this year.
Any modification to Reach/Reach RS app will break with an OTA update.
thank you for your reply. Can you please provide some more clarification about the planned API?
My goal is to keep all the current ReachView functionality but add to this some custom functionality. I assume that the ReachRS can only serve one web application at a time. In order to add custom functionality will it be necessary to reproduce the current ReachView app (via API) so that the custom functionality can be added? If this is not the case can you please describe how custom functionality would be implemented?
Will it be possible to change the data sent out over the Bluetooth interface (based on added functionality)?
Our current plan is that we will expose all functions with an API, so you will be able to push settings and get status info. Making ReachView user-extendable is not a an easy task.
It is possible to send different data to Bluetooth, but if BT is taken by sending NMEA it is not possible to alter the stream.