From 23503fd112f0d5b994d6c3792705bd20f3d0ff44 Mon Sep 17 00:00:00 2001 From: Zafar <78258915+Zafouche@users.noreply.github.com> Date: Thu, 19 Dec 2024 23:18:38 +0100 Subject: [PATCH 1/2] Update README.md --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index f0c69a2ff..576c6fd46 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,6 @@ # Unio The link to the Figma prototype can be found [here](https://www.figma.com/design/rlvqRyIsbdSyEbXu8Xp7yG/Unio). +You can also find the Architecture Diagram of the project [here](https://drive.google.com/file/d/1s9Xrv6akC5gjgEjS0Y1rrtqVNzkH11-n/view?usp=sharing) ## The problem being solved University associations, specifically the ones at EPFL, lack ways of interacting with their community. This can be seen through their single e-mail per semester allowance, or their use of the Instagram platform to communicate about projects or events, when only a small proportion of their audience sees it. Our project aims to resolve this issue by providing a single platform where campus associations can inform about, manage, and prepare their events. This would take shape as a social media-style application, where associations would be presented to users who could then choose to learn more about them, follow them (letting them know of future events etc.), or even join them. Once one has followed a few associations, their feed would then consist of their future events. As such, the core audience we aim for are students both on the user side and the association side. The application can be viewed as an extension of the EPFL Campus application, but it could also potentially be later adapted for non-university events. @@ -21,4 +22,4 @@ The following sensors would be used: - Camera access, so that users can upload pictures after events ## Offline mode -Most of the features, such as viewing associations, events, the map, would still work in offline mode, with the only difference being that the visible data would be out of date. Messaging, uploading pictures etc. would not work offline but there could be a queue system so that they are immediately uploaded when connectivity is re-established. \ No newline at end of file +Most of the features, such as viewing associations, events, the map, would still work in offline mode, with the only difference being that the visible data would be out of date. Messaging, uploading pictures etc. would not work offline but there could be a queue system so that they are immediately uploaded when connectivity is re-established. From 4673dda5db747e42f3ed17bd7a719968433c7388 Mon Sep 17 00:00:00 2001 From: Zafar Date: Thu, 19 Dec 2024 23:36:06 +0100 Subject: [PATCH 2/2] chore(nominatim-api-service): update user agent email to team email --- .../com/android/unio/model/map/nominatim/NominatimApiService.kt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/src/main/java/com/android/unio/model/map/nominatim/NominatimApiService.kt b/app/src/main/java/com/android/unio/model/map/nominatim/NominatimApiService.kt index ac9924984..633563812 100644 --- a/app/src/main/java/com/android/unio/model/map/nominatim/NominatimApiService.kt +++ b/app/src/main/java/com/android/unio/model/map/nominatim/NominatimApiService.kt @@ -11,7 +11,7 @@ import retrofit2.http.Query * Retrofit which can build the URL automatically thanks to it. */ interface NominatimApiService { - @Headers("User-Agent: Unio/0.3 (zafarderie@gmail.com)") + @Headers("User-Agent: Unio/0.3 (unio.epfl@gmail.com)") @GET("search") /**