Closed hsalameh closed 7 years ago
@zugaldia This is the first attempt at the mobile app. It is very basic but in working condition. I added it as separate mobile app from the one you added. I called it mobile1.
Warning: for the time being, please stay close to the robocar when using this app and be ready to jump in and disconnect the power if the motors got stuck on the "on" position. It happened to me.
I think we should switch to websockets instead of a rest api because with web sockets, the robocar can detect a loss of connection to the app, and immediately set the speeds to 0, thus avoiding a crash (a physical one). With the rest api, this is not possible, and there is always a chance that the robocar will get stuck and keep moving until the power is disconnected.
This is the first attempt at the mobile app. It is very basic but in working condition. I added it as separate mobile app from the one you added. I called it mobile1.
Bravo. I'll check it out and plan a path to merge it inside the existing mobile
app.
I think we should switch to websockets instead of a rest api because with web sockets, the robocar can detect a loss of connection to the app, and immediately set the speeds to 0, thus avoiding a crash (a physical one).
This looks like a very decent reason to switch to websockets :)
Created a mobile app that can control the robocar via the "api/speed" endpoint