Notify 🤩🔥

Available on Playstore

Events

Problem Statement :

Whenever we try to attend events like interviews, exams, marriage, trips, catching a flight, train. The most issue which people face is "not able to reach on time and missing out"

Solution :

● We will get the information regarding the event and notify the user. The information which we will get includes starting point, destination point, name of event, description, date, and time of the event.

● Through the above information, we will notify the user which will help the user to reach the destination on time.

● We will handle the traffic-related issue and calculate the time required to reach the destination. Which will solve the problem of "not able to reach on time and missing out"

Tasks

Problem Statement :

People use task manager and used to note down the task which they want to complete. The problem is, very often people forgot to remember what task they have to do now.

Solution :

● Very often, people used to forget the task, which results in "not completing the task on time." ● We will help to complete the task by notifying the user based on the user's requirements.

Goals

Problem Statement :

Not having the relationship between task and goal which they want to achieve. People often do task which is not related to achieving the goals.

Solution :

● We will map the task to the goal which will help the user to achieve the goals and be more productive. ● We will show the progress bar, status and predict whether you will be able to achieve your goals on time if you complete the task, the way you are doing it.

Links

🔗Open-Source Library

• Glide
• Firebase
• Google Map
• Jetpack
• Circular ImageView
• EazeGraph

Things we used while making this application

• GitHub
• Firebase
• Recycler View
• Retrofit Library
• API
• Gif ImageView
• VideoView
• Fragments
• Retrofit Library
• Autoslider and Loti Animation
• Eaze Graph
• Google Maps Place API

Tech Stack ✨

• Android Studio
• Kotlin

Architecture

This app uses MVVM (Model View View-Model) architecture.

Clone this Repo To Your System Using Android Studio✨

• Step 1: Open your Android Studio then go to the File > New > Project from Version Control as shown in the below image.
• Step 2: After clicking on the Project from Version Control a pop-up screen will arise like below. In the Version control choose Git from the drop-down menu.
• Step 3: Then at last paste the link in the URL and choose your Directory. Click on the Clone button and you are done.

Clone this Repo To Your System Using GitBash✨

• Open Git Bash

• If Git is not already installed, it is super simple. Just go to the Git Download Folder and follow the instructions.

• Go to the current directory where you want the cloned directory to be added.

• To do this, input cd and add your folder location. You can add the folder location by dragging the folder to Git bash.

• Go to the page of the repository that you want to clone

• Click on “Clone or download” and copy the URL.

• Use the git clone command along with the copied URL from earlier. $ git clone https://github.com/Kingbond470/Notify

• Press Enter. $ git clone https://github.com/Kingbond470/Notify

Congratulations, you have created your local clone from your remote Github repository.

Open Android Studio. Go to File > New > Project From Version Control. Copy the link of this repositary. Paste the link in Url Box of Android Studio window and click on "Clone" button.

Let's See

Event

Task

Goal

Settings

Feature of Custom Calendar

Dependencies

// Material UI
implementation 'com.google.android.material:material:1.5.0-alpha03'


// Firebase Google Authentication
implementation 'com.google.firebase:firebase-auth-ktx:21.0.1'

// Firestore
implementation 'com.google.firebase:firebase-firestore-ktx:21.5.0'
implementation 'com.firebaseui:firebase-ui-firestore:6.3.0'
implementation 'com.google.firebase:firebase-storage:20.0.0'

// Import the BoM for the Firebase platform
implementation platform('com.google.firebase:firebase-bom:29.0.0')
implementation 'com.google.firebase:firebase-database-ktx'

// Also declare the dependency for the Google Play services library and specify its version
implementation 'com.google.android.gms:play-services-auth:19.2.0'

//Navigation component
def nav_version = "2.3.5"
implementation "androidx.navigation:navigation-fragment-ktx:$nav_version"
implementation "androidx.navigation:navigation-ui-ktx:$nav_version"

// Retrofit dependency which will be used to make network calls
implementation 'com.squareup.retrofit2:retrofit:2.9.0'

// GSON library which is used to convert POJO to JSON and vice versa
implementation 'com.squareup.retrofit2:converter-gson:2.9.0'

// okhttp library used to observe the api call logs on LogCat
implementation 'com.squareup.okhttp3:logging-interceptor:5.0.0-alpha.2'

//Glide
implementation 'com.github.bumptech.glide:glide:4.12.0'
annotationProcessor 'com.github.bumptech.glide:compiler:4.12.0'

//Coroutines
implementation("org.jetbrains.kotlinx:kotlinx-coroutines-android:1.5.2-native-mt")
implementation "org.jetbrains.kotlinx:kotlinx-coroutines-android:1.5.0"
implementation "org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.0"

// Coroutine Lifecycle Scopes
implementation "androidx.lifecycle:lifecycle-viewmodel-ktx:2.3.1"
implementation "androidx.lifecycle:lifecycle-runtime-ktx:2.3.1"

// ViewModel and LiveData
def arch_version = '2.2.0-alpha01'
implementation "androidx.lifecycle:lifecycle-extensions:$arch_version"
implementation "androidx.lifecycle:lifecycle-viewmodel-ktx:$arch_version"
implementation "androidx.lifecycle:lifecycle-livedata-ktx:$arch_version"
implementation "androidx.lifecycle:lifecycle-runtime-ktx:$arch_version"

// Architectural Components
implementation "androidx.lifecycle:lifecycle-viewmodel-ktx:2.3.1"

// Kotlin Extensions and Coroutines support for Room
implementation "androidx.room:room-ktx:2.3.0"

// Room
implementation "androidx.room:room-runtime:2.3.0"
kapt "androidx.room:room-compiler:2.3.0"

//Dagger - Hilt
implementation "com.google.dagger:hilt-android:2.28-alpha"
kapt "com.google.dagger:hilt-android-compiler:2.28-alpha"
implementation "androidx.hilt:hilt-lifecycle-viewmodel:1.0.0-alpha02"
kapt "androidx.hilt:hilt-compiler:1.0.0-alpha02"

//lottie
implementation 'com.airbnb.android:lottie:3.2.0'

// circular imageview
implementation 'de.hdodenhof:circleimageview:3.1.0'

//animation
implementation 'pl.droidsonroids.gif:android-gif-drawable:1.2.22'

//about
implementation 'io.github.medyo:android-about-page:2.0.0'

//google maps
implementation 'com.google.android.gms:play-services-maps:18.0.0'
implementation 'com.google.android.gms:play-services-location:18.0.0'

//chart library
implementation 'com.github.lecho:hellocharts-library:1.5.8@aar'


// For Card view
implementation 'androidx.cardview:cardview:1.0.0'

Contributing to Notify

We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:

• Reporting a bug
• Discussing the current state of the code
• Submitting a fix
• Proposing new features
• Becoming a maintainer

We Develop with Github

We use github to host code, to track issues and feature requests, as well as accept pull requests.

We Use Github Flow, So All Code Changes Happen Through Pull Requests

Pull requests are the best way to propose changes to the codebase (we use Github Flow). We actively welcome your pull requests:

1. Fork the repo and create your branch from main.
2. If you've added code that should be tested, add tests.
3. If you've changed APIs, update the documentation.
4. Ensure the test suite passes.
5. Make sure your code lints.
6. Issue that pull request!

Any contributions you make will be under the MIT Software License

In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.

Report bugs using Github's issues

We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!

Write bug reports with detail, background, and sample code

This is an example of a bug report, and I think it's not a bad model. Here's another example from Craig Hockenberry, an app developer whom I greatly respect.

Great Bug Reports tend to have:

• A quick summary and/or background
• Steps to reproduce
  • Be specific!
  • Give sample code if you can. stackoverflow question includes sample code that anyone with a base R setup can run to reproduce
• What you expected would happen
• What actually happens
• Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)

People love thorough bug reports. I'm not even kidding.

Use a Consistent Coding Style

• 2 spaces for indentation rather than tabs or use tabs
• You can try running npm run lint for style unification

License

By contributing, you agree that your contributions will be licensed under its MIT License.

MIT License

Copyright (c) 2021 Mausam Singh

   Permission is hereby granted, free of charge, to any person obtaining a copy
   of this software and associated documentation files (the "Software"), to deal
   in the Software without restriction, including without limitation the rights
   to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
   copies of the Software, and to permit persons to whom the Software is
   furnished to do so, subject to the following conditions:

  The above copyright notice and this permission notice shall be included in all
  copies or substantial portions of the Software.

  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
  SOFTWARE.

Contributors 🌸💯👏

Developed by

• Abhimanyu Mishra
• Murali Krishna Sundara
• Mausam Singh
• Rohit Sharma

Lessons Learnt📚

We built the project in two days during Masai Hackathon. #3 Rank

PS

Hard work beats the talent, when talent doesn't do the hardwork. I am new person in open source of Android Development, so please feel free to correct and make changes. #LookingForward