Mobile messenger and day analyzer application

INTRODUCTIONS First two paragraphs are for better underrating only. Two RPi Applications Multiple RPis will be installed at different locations to collect data from different sensors. There is two application will be installed at each RPi First application will gather data using sensors and store it in a SQLite database at the device. Second application will send this data to the Data Server. It will also read the data from the database, encode it as JSON and send it to the Data Server via a POST request. All data will be encoded and passed around in a JSON format. If data transfer is successful, the Data Server will notify the RPi by sending a status code back to it. If the Data Server successfully receives data, it will notify the RPi. Once that happens, the RPi will clear the local database before recording to it again. Data Server Data Server will be used to send and receive sensor data. Data Server is a Flask application, written in Python and uses SQLite for persistent storage. There are 2 things that the Data Server will do: 1. Receive data via a POST request, which it will then log to a database 2. Send data to a specific user when it receives a GET request from them The data it receives will come from deployed RPi-s. It will parse the JSON-encoded data that comes in and then log it to the database. The data from the database will be sent to the client upon request, once they open their Mobile Application, for example. The Data Server will return relevant data once it receives a GET request. The parameter of the GET request can be a username, key, or a special string in order to let it know which client is requesting the data. We can decide on that at any point. Data Server will also be used for checking for any danger. For example, if it receives a chunk of data and sees that the temperature or pressure is beyond reasonable limits, it will send a notification to the client's Mobile Application to let them know that something is wrong. Specific parameters for what is dangerous and what is not will be specified later. MOBILE APPLICATION we need to develop. (Android / iOS) Mobile Application will have 3 functions: 1. Receive notifications from the Data Server 2. Send and receive messages from the Customer to Contractor via the Messaging Server 3. Check the current status/measurements Once the application is opened, it will immediately send a GET request to the Data Server and to the Messaging Server. The Data Server will send relevant data for that user back to the Mobile Application, which will then process the JSON encoded data and do a number of calculations on it, for example, averaging, visualizing, etc. The Mobile Application can handle refreshing in two ways: 1. Automatic async requests to the Data Server and the Messaging Server every few seconds or so 2. Manual refresh button which will trigger another GET request to the Data Server and the Messaging Server The Messaging Server will do something similar to the Data Server, only it will log messages and not sensor data. However, it will tie Contractors to Clients in a restrictive manner. A certain client will be tied to a certain contractor and their relationship will be logged on the Messaging Server. Clients will not and should not be able to message each other or switch contractors, or even talk to other contractors. That will be done manually by us, as a way of providing support. In a nutshell, the Messaging server will simply log messages between bound clients and contractors. They can use the Mobile Application to send messages and pictures between each other. 1. POST requests will be used to send messages 2. GET requests will be used to get all logged messages from the server This process is pretty straightforward. Once someone sends a message, the Messaging Server will log the message to a database and then send the data back to both the client and the contractor in order to update the conversation. Also, needless to say, data should be fetched from the Messaging Server the same way it is with the Data Server, via POST and GET requests, and it will be done automatically whenever someone opens the Mobile Application, upon refreshing ,or every few seconds via async requests. Lastly, notifications will be sent to the Mobile Application through the Data Server and the Messaging Server. We can have multiple types of notifications, for example if there is a new message, or if there is something wrong, or even standard, timed messages that go off when something interesting or important happens. In short, the Mobile Application will communicate with both the Data Server and the Messaging server. Notifications will be handled by the aforementioned servers.