Our app proposes itself as a centralized event maker and manager, allowing to prepare the spaces. The main organizers will have the ability to access a map of the location and place elements on it. This will allow the association's volunteers to know where every table, marquees and every other structure should be placed. Moreover, it allows to schedule events, to dispatch roles between all the volunteers and to assign them tasks. A true event manager. As a secondary feature, some parts can be viewable trough an AR simulation.
We intend to use Firebase cloud service, allowing to handle the management of different accounts containing each user's schedules. The map and information on the event will also be stored with Firebase. This will make each user able to see changes in real time.
The multi-user support will be supported by Firebase and using google accounts. This will give each user different permissions to modify or just see the event's layout depending on their given role in the association.
The camera will be used for the AR preview and navigation in the event. The GPS will be used to have better precision in the AR and to access a map of the event. The gyroscope will be used for the AR.
In offline mode, the app will display cached tasks and schedules for the organizers and let them access the event's map. The AR layout will also be cached. The app will also be able to load the event from a local file.
Code reviews should follow these guidelines. Don't forget to delete branches after merging in main.
- New feature: feature/feature-name (ex: feature/map-screen)
- Bugfix: bugfix/issue-number (ex: bugfix/issue-67)
- Improvements: improvement/short-desc (ex: improvement/refactor)
- Trying things: experiment/desc (ex: experiment/ar-view)
- Tests creation: test/what-is-tested (ex: test/map-gps-loc)
When creating an issue, make sure to clearly describe the issue and specify the correct labels/types/priority...
Follow the usual commit conventions, as seen in class. Add labels as done with issues.