To structure our app we used the following diagram:
- We placed the authentication information inside a component, which keeps user data, such as login, register and logout.
- The system is able to send small form's to the user, in order to keep a constant real-time update on certain queues.
- Inside the FEUP GUI component, we placed all the visual interface which the user can see and interact.
- The request component keeps information about queues state, available capacity and queue prediction/history information about a certain place. We can also order the queues by distance from the user (nearest will come first!)
- There are some external services that help our app receiving information about capacity's, such as parking lot and library, our app will fetch this data externally, and display it to the user. Also we will use google maps API to retrieve GPS positioning of the user.
- We will use a package which contains all information about a small chat, that users will use to send humanly messages about a queue. Also there is a report feature in order to keep a highly trust rate.
- System Logic receives all information from the packages above, and coordenates it with the FEUPQ server
- For our final delivery there were some changes, initially we wanted to create a small chat that could allow users to interact and send real-time written reports so other users could see. This feature was not implemented due to time/reliability.
- There was also a feature that consisted in the system sending us some notifications so we could manually report the status of a facility that we were in a few moments ago. Due to time it was not possible also to implement
To develop our app, we used the Flutter technology. For the API's, we are using Google Maps API for GPS information.
- Our app will be used in the users smartphone (FEUP Community Phone), from there it will interact with the FEUPQ Server
- The FEUPQ UI will be developed in flutter and also interacts with the Logic Services such as Dart.
- We'll still have the external services, which were briefly described on the logical architecture.
The main menu already integrated with the UNI app looks like this:
The project ended with this visual interface, there was a improvement on functionalities but there is still some room for more improvement