-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
7cc5112
commit 2cf15b0
Showing
1 changed file
with
190 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,16 +1,196 @@ | ||
| # flutter_project_template | ||
| # CAT304 Project: cuzVcare Mobile App | ||
|
|
||
| A new Flutter project. | ||
| ## Problem Statements | ||
| Volunteering organizations and volunteers often struggle with managing and tracking events effectively. With disparate systems for event registration, attendance tracking, and rewards, both volunteers and organizations face numerous inefficiencies and challenges such as: | ||
|
|
||
| ## Getting Started | ||
| - **Low Discoveries of Event Information:** There are a lot of volunteers out there who are keen on participating these activities but due to there is no specific platform to host all these information at the same platform to ease discovery, many of them are not aware that these activities are going on. | ||
|
|
||
| This project is a starting point for a Flutter application. | ||
| - **Activities Signups and Participations:** Participants who are interested in taking part in the activities will sometimes forget the activity, date, time or the venue due to forgetful. Some of them who have signed up for the activity but are absent due to various reasons, which will result in the number of participants who have signed up is lesser than the number of participants who are actually turning up in the activities. | ||
|
|
||
| A few resources to get you started if this is your first Flutter project: | ||
| - **Difficulties in Conveying Messages:** In the event of unexpected issues such as rain, inevitable postponement of activities, change of activities details etc., announcements or updates such as the new date and time are difficult to convey to all the participants. Hence, a lot of them are not aware of the latest arrangements. Even if we can use phone calling to notify them one by one, it will be tedious if many participants is involved. | ||
|
|
||
| - [Lab: Write your first Flutter app](https://docs.flutter.dev/get-started/codelab) | ||
| - [Cookbook: Useful Flutter samples](https://docs.flutter.dev/cookbook) | ||
| - **Activity Records Management:** Mostly, all the activity records are either incomplete or not well documented. Even if the records are complete, they are not shared with others. This results in future activities do not having enough references and difficult to find solutions when necessary. | ||
|
|
||
| For help getting started with Flutter development, view the | ||
| [online documentation](https://docs.flutter.dev/), which offers tutorials, | ||
| samples, guidance on mobile development, and a full API reference. | ||
| - **Lack of Awareness and Motivation in Event Participation:** Even if some people have discovered the activity, there are very less of them who would like to join because they think these activities are wasting time. Some of them might feel that the event information provided is not attractive enough to motivate them to participate. | ||
|
|
||
| - **Vulnerability of Sensitive Information:** Most of the time, the organizers will collect the information of participants when they sign up for an activity. The information is not guaranteed to be safe and is at the risk of being stolen or exposed. | ||
|
|
||
| - **Lack of interaction platform:** The difficulty in coordinating and communicating effectively among volunteers due to a lack of a dedicated online platform for managing and organizing volunteer efforts. | ||
|
|
||
| ## Project Overview | ||
| Unsustainable cities and human settlements is one of the major issue in the current world and is particularly severe in poor countries. In around the world, pollutions, waste management, and natural disasters are prevalent issues and actions must be taken to mitigate it. However, volunteering activities, as one of the most effective mitigating methods, is lacking and not carried out profusely. One of the main reasons is because there is no focused, organized, secure and trustworthy communication hub to host volunteering activity information. We aim to reduce these issues by engineering a volunteer recruitment platform named “cuzVcare”. The platform aims to host all the event information on the same platform while motivate users in participating events, allow users to discover and sign up for the events they would like to join as well as enable the users to keep track the events they have signed up and bookmark the events they are interested to join. | ||
|
|
||
| cuzVcare is designed to streamline the management and participation of volunteering events developed as a mobile application which can be run on Android and iOS Operating Systems as mobile application has the highest volume of users in the current trend. This application can be used by anyone from any part of the world in order to create a more sustainable cities and human settlements as aligned with Sustainable Development Goals (SDG) 11. | ||
|
|
||
| The app serves as an efficient tool to encourage volunteering, making it easier for users to engage with local events and be rewarded for their contributions. | ||
|
|
||
| ## Key Features | ||
| - **Event Submission**: Organisers can submit their event details to be featured on the platform. | ||
| - **Event Tracking**: Users can track past volunteering events and view submission statuses (Pending/Approved/Rejected). | ||
| - **Event Signup**: Volunteers can register for events and check-in to track their attendance. | ||
| - **GPS Filtering**: Volunteers can find nearby events based on their location. | ||
| - **Rewards Redemption**: Volunteers can redeem their earned points for rewards from partnered organizations. | ||
| - **Chat and Notifications**: Seamless communication through notifications and chat for event updates and reminders. | ||
|
|
||
| ## Technologies Used | ||
| - **Flutter:** Cross-platform mobile application framework for building iOS and Android apps. | ||
| - **Firebase:** Backend-as-a-service solution for user authentication, data storage, and notifications. | ||
| - **Dart:** The programming language used for developing the app. | ||
| - **Figma:** Design tool used for creating the app's user interface and user experience designs. | ||
| - **Android Studio:** Integrated development environment (IDE) used for Flutter development and testing on Android devices. | ||
|
|
||
| ## Installation | ||
| This project is not open for public cloning or redistribution without prior written permission from the author as stated in . If you would like to access this project, please reach out to the repository owner to request permission. | ||
|
|
||
| Once written permission is granted, you will receive detailed instructions on how to install and run the system, including all necessary steps and dependencies. | ||
|
|
||
| ## Usage | ||
| Similar to the installation process, usage instructions will be provided only after written permission is granted to access this repository. Upon receiving access, you will be provided with step-by-step instructions on how to use this system/application, including on how to run the program, interact with it and exploring all the key features stated. | ||
|
|
||
| ## Screenshots | ||
| 1. **Onboarding Screen:** | ||
| <p align="center"> | ||
| <img src="readme-assets/01 Onboarding Screen.png" alt="onboarding screen"/> | ||
| <br/> | ||
| <i>Figure 1: Onboarding Screen</i> | ||
| </p> | ||
|
|
||
| 2. **Sign Up Screen:** | ||
| <p align="center"> | ||
| <img src="readme-assets/02 Sign Up Screen.png" alt="sign up screen"/> | ||
| <br/> | ||
| <i>Figure 2: Sign Up Screen</i> | ||
| </p> | ||
|
|
||
| 3. **Log In Screen:** | ||
| <p align="center"> | ||
| <img src="readme-assets/03 Log In Screen.png" alt="log in screen"/> | ||
| <br/> | ||
| <i>Figure 3: Log In Screen</i> | ||
| </p> | ||
|
|
||
| 4. **Create Profile Screen:** | ||
| <p align="center"> | ||
| <img src="readme-assets/04 Create Profile Screen.png" alt="create profile screen"/> | ||
| <br/> | ||
| <i>Figure 4: Create Profile Screen</i> | ||
| </p> | ||
|
|
||
| 5. **Home Page Screen:** | ||
| <p align="center"> | ||
| <img src="readme-assets/05 Home Page Screen.png" alt="home page screen"/> | ||
| <br/> | ||
| <i>Figure 5: Home Page Screen</i> | ||
| </p> | ||
|
|
||
| 6. **View Event Detail:** | ||
| <p align="center"> | ||
| <img src="readme-assets/06 View Event Detail.png" alt="view event detail"/> | ||
| <br/> | ||
| <i>Figure 6: View Event Detail</i> | ||
| </p> | ||
|
|
||
| 7. **View Event Ticket:** | ||
| <p align="center"> | ||
| <img src="readme-assets/07 View Event Ticket.png" alt="view event ticket"/> | ||
| <br/> | ||
| <i>Figure 7: View Event Ticket</i> | ||
| </p> | ||
|
|
||
| 8. **View Joined Events:** | ||
| <p align="center"> | ||
| <img src="readme-assets/08 View Joined Events.png" alt="view joined events"/> | ||
| <br/> | ||
| <i>Figure 8: View Joined Events</i> | ||
| </p> | ||
|
|
||
| 9. **View Bookmarked Events:** | ||
| <p align="center"> | ||
| <img src="readme-assets/09 View Bookmarked Events.png" alt="view bookmarked events"/> | ||
| <br/> | ||
| <i>Figure 9: View Bookmarked Events</i> | ||
| </p> | ||
|
|
||
| 10. **View All Rewards:** | ||
| <p align="center"> | ||
| <img src="readme-assets/10 View All Rewards.png" alt="view all rewards"/> | ||
| <br/> | ||
| <i>Figure 10: View All Rewards</i> | ||
| </p> | ||
|
|
||
| 11. **View Redeemed Rewards:** | ||
| <p align="center"> | ||
| <img src="readme-assets/11 View Redeemed Rewards.png" alt="view redeemed rewards"/> | ||
| <br/> | ||
| <i>Figure 11: View Redeemed Rewards</i> | ||
| </p> | ||
|
|
||
| 12. **Create Event Form Part 1:** | ||
| <p align="center"> | ||
| <img src="readme-assets/12 Create Event Form Part 1.png" alt="create event form part 1"/> | ||
| <br/> | ||
| <i>Figure 12: Create Event Form Part 1</i> | ||
| </p> | ||
|
|
||
| 13. **Create Event Form Part 2:** | ||
| <p align="center"> | ||
| <img src="readme-assets/13 Create Event Form Part 2.png" alt="create event form part 2"/> | ||
| <br/> | ||
| <i>Figure 13: Create Event Form Part 2</i> | ||
| </p> | ||
|
|
||
| 14. **View All Chat Messages:** | ||
| <p align="center"> | ||
| <img src="readme-assets/14 View All Chat Messages.png" alt="view all chat messages"/> | ||
| <br/> | ||
| <i>Figure 14: View All Chat Messages</i> | ||
| </p> | ||
|
|
||
| 15. **Send and Receive Messages:** | ||
| <p align="center"> | ||
| <img src="readme-assets/15 Send and Receive Messages.png" alt="send and receive messages"/> | ||
| <br/> | ||
| <i>Figure 15: Send and Receive Messages</i> | ||
| </p> | ||
|
|
||
| 16. **View User Profile:** | ||
| <p align="center"> | ||
| <img src="readme-assets/16 View User Profile.png" alt="view user profile"/> | ||
| <br/> | ||
| <i>Figure 16: View User Profile</i> | ||
| </p> | ||
|
|
||
| 17. **Edit User Profile:** | ||
| <p align="center"> | ||
| <img src="readme-assets/17 Edit User Profile.png" alt="edit user profile"/> | ||
| <br/> | ||
| <i>Figure 17: Edit User Profile</i> | ||
| </p> | ||
|
|
||
| 18. **View Notification:** | ||
| <p align="center"> | ||
| <img src="readme-assets/18 View Notification.png" alt="view notification"/> | ||
| <br/> | ||
| <i>Figure 18: View Notification</i> | ||
| </p> | ||
|
|
||
| 19. **Side Drawer Menu Screen:** | ||
| <p align="center"> | ||
| <img src="readme-assets/19 Side Drawer Menu Screen.png" alt="side drawer menu screen"/> | ||
| <br/> | ||
| <i>Figure 19: Side Drawer Menu Screen</i> | ||
| </p> | ||
|
|
||
| 20. **About Us Screen:** | ||
| <p align="center"> | ||
| <img src="readme-assets/20 About Us Screen.png" alt="about us screen"/> | ||
| <br/> | ||
| <i>Figure 20: About Us Screen</i> | ||
| </p> | ||
|
|
||
| 21. **Log Out Screen:** | ||
| <p align="center"> | ||
| <img src="readme-assets/21 Log Out Screen.png" alt="log out screen"/> | ||
| <br/> | ||
| <i>Figure 21: Log Out Screen</i> | ||
| </p> |