Skip to content

hackslash-nitp/Hostelite

Repository files navigation

Hostelite

A hostel management app using flutter where the complains of students and their exit or entry timing reaches directly to the administration.

GitHub code size in bytes GitHub last commit GitHub stars

My stars GitHub forks Languages

Top Issues Watchers

The app is being built using flutter, with Firebase as the backend, and also uses Google Maps API for tracking the current location of the Hostelite.

There are two types of Views for this app, signifying the two types of users:

  • Views for Students
  • Views for Hostel Administration

For Students, the following features will be integrated:

  • Report Issue to the administration
  • Mark Entry (requires the use of location tracking)
  • Mark Exit
  • View his/her daily records of entry/exit
  • Get alerted when outside the facility after a certain time and prompted to send an explanation to the administration
  • See Notices posted by the Hostel Administration
  • Change personal profile information

For Administration, the following features will be integrated:

  • See Complaints posted by the Hostelites, and mark them sorted, pending or rejected
  • See Alerts from the boarders who are outside after a specific time
  • See Entry/Exit Report of the entire hostel for a specific date
  • Post Notices for the Hostelites to view
  • Change personal profile information

Tech-stack :

android kotlin jetpack compose figma firebase

Screenshots of App

android android android android android android android android android android android

Interested?🤩 Check how you can be a part of it👇

Contributions Best Practices

Commits

  • Write clear meaningful git commit messages (Do read https://chris.beams.io/posts/git-commit/)

  • Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (More info at https://github.com/blog/1506-closing-issues-via-pull-requests )

  • When you make very minor changes to a PR of yours (like for example fixing a failing Travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterward so that you don't have an absurd number of commits for a very small fix.

  • When you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers and you'll also get reviews quicker.

Our budding maintainer and contributors:

Made with contrib.rocks.

If you 💓 this, do smash the ⭐ button!!

Thanks for visiting!!