S2_IF
The purpose of this feature is to give users the possibility to share an event quickly. For this we use QR codes that automatically open the view of a specific event. This can be done by means of the device's camera.
This functionality can be seen in the QR icon to the left of the logo and in the main part of the application (To read QR codes). In order to share an event, a code is generated when accessing the event details. This allows to link the QR with the event.
The type 2 question that we answer with this feature is: What are the last events I attended in the last month?
To answer this question we show all past events that the user joined sorted by date from the most recent to the oldest. In addition, we show the event detail to see the event information. However, the functionality of the "join" or "leave" button is removed since these are events that have already happened.
To answer this question...
For this feature Hive app sends notifications when the user's device, with their explicit consent, enters a predefined geographical area around Uniandes, utilizing location services and geofencing technology. This feature tracks the user's proximity to Uniandes and triggers notifications accordingly, requiring responsible data handling, privacy protection, and battery optimization to ensure an accurate, user-friendly, and ethically sound experience. It is context aware due to the fact that takes into account the surroundings and the user's location
In this feature we do a simple implementation of a login with a username and password to know which user is entering the application. Here we do checks for both empty and non-existent user or incorrect information as you can see in the images. On the other hand, it allows an unregistered user to go to the account creation section.
Note that no information related to the application will be shown to a user who is not logged in.
In the profile view we make requests to the backend of the application to access the user's information and display it. We obtain the user detail and show information related to the account with which the session started (name and email). On the other hand, we show the user's participation by means of the number of total events in which the user has participated.
In the activity view, closely related to the user's history, it allows to see the active events to which the user has subscribed sorted by date from the most recent event to the most distant event.
In this feature we use 2 services from the application backend. Get active events of a user sorted by date and get the detail of an event.
With this we can give the user an easy way to access the registered events to see their information, share it or simply decide not to participate in the previously registered event.