I have a couple suggestions for visual improvements.
Right now, I think it is not always clear if the app is receiving telemetry data. I think a clear indication of the current state of telemetry would be nice. As far as I can see we can distinguish these three states:
No bluetooth/usb connection
Bluetooth/usb connected but no telemetry received
Telemetry is received.
I was thinking a sort of stoplight indicator would be easy to read.
Additionally, a loss of telemetry (transition from state 3 to 2 or 1) could be indicated by red blinking telemetry values, like in the INAV lua telemetry script.
Finally, the connect/disconnect, replay and settings buttons could be moved to a hamburger menu in the top right corner. You don't need these options multiple times per flight and you don't want to hit disconnect accidentally in-flight. Misreading "CONNECT" as "CONNECTED" when you are in fact not connected (and vice versa) can also be confusing if you have a lot of other things going on.
I have a couple suggestions for visual improvements.
Right now, I think it is not always clear if the app is receiving telemetry data. I think a clear indication of the current state of telemetry would be nice. As far as I can see we can distinguish these three states:
I was thinking a sort of stoplight indicator would be easy to read.
Additionally, a loss of telemetry (transition from state 3 to 2 or 1) could be indicated by red blinking telemetry values, like in the INAV lua telemetry script.
Finally, the connect/disconnect, replay and settings buttons could be moved to a hamburger menu in the top right corner. You don't need these options multiple times per flight and you don't want to hit disconnect accidentally in-flight. Misreading "CONNECT" as "CONNECTED" when you are in fact not connected (and vice versa) can also be confusing if you have a lot of other things going on.