Implement communication protocoll between App and plotter

[gruvw]

Application development

I made a ton of progress on the application this week (on top of the specifications for this particular task). Here is a summary of all the additional features:

• [X] remotes state management with saved devices
• [X] see which remote is offline/online (check device type + matching MAC address)
• [X] ability to refresh remote state from remotes overview
• [X] make most of the layout details configurable (colors, sizes, spacing, ...)
• [X] remotes are sorted in overview by online remote first then by mac address
• [X] full implementation of the communication protocol with the plotter (with remotes state management)
• [X] ability to reconfigure the IP address of an offline saved remote
• [X] easy and accessible user interface for using configured remotes
• [X] click on remote buttons will dispatch correct requests based on predefined protocol
• [X] visual feedback for outgoing requests (loading + outcome)
• [X] implement fake request responses for testing the plotter protocol locally
• [X] reorder/edit remote buttons page
• [X] rename saved remotes
• [X] remove configured saved remotes (with confirmation dialog)
• [X] setting up a new remote with same MAC will update the remote's config
• [X] import export remote config as serialized text (easier to exchange remote config)
• [X] import remote config data validation (avoid app crashing and need to wipe state on wrong config import)
• [X] add a custom remote button page (with feedback buttons + setup and teardown procedure)
• [X] mapping of custom remote "joystick like" accessible controls to set up new custom button
• [X] test custom button press request before registering new button
• [X] make application body scrollable on all applicable pages for short devices

The goal of this application's design is to be very simple to use, especially for people using alternative devices to control their smartphone (disabilities). Therefore, I went with large contrasted squared buttons for all the common uses of the application (regular "every day" users). I also tried to keep the configurations screen as simple and as intuitive as possible while not striving directly for full accessibility there, as it is harder to implement and also external help will be required anyway for configuring the devices.

For the record, you will also find below a few screenshots of the app (before my presentation/demo today at 5PM):

With that being said, the application is almost finished (feature wise): I opened two new tasks that are the last two features missing in the app #39 and #40 (that I plan to implement in the coming week, to be discussed in our meeting together this afternoon).

As far as this task is concerned, I feel like the requirements for it are fulfilled (as we defined them in our previous meeting). Tell me if I missed anything or if you are expecting something else to be added on this task. Otherwise, I will consider it as done :)

[gruvw]

Public Web Demo Version

Additionally, I spent some time this morning to deploy a public WEB based demo version of the app, so everybody can easily access it and use it with our remote plotter to try it out.

The demo is hosted directly on GitHub, and I added a CNAME record to a subdomain of my website to easily access it under the following URL: https://hh.gruvw.com (hh for Helping Hand).