A

Adherent

be a part of your city truly, get instant updates of everything happening around you.

The problem Adherent solves

We all are different, experience various things happening around us but we stick together. We are all a part of a greater community. As humans, we've the tendency to share, someway to help others.
We all reside in a city but we rely on our locals news networks and friends to get to know about events happening around us. To cutdown the delay in the updates to reach us, our team came up with Adherent.
Adherent is a community network for cities. When you join, you have instant access to everything happening in your city all at once.
With both an app and a web-app, everything becomes more accessible to the user. We can look at the weather updates of a region in our city, we can get the latest information about all the events, important updates and news stories right on your feed as they're happening live.
The user can search for a specific locality and get info about the area right from home. With every post the user makes, the device automatically detects the region they're in and posts the update with the region specified.
With security in mind, the server doesn't store any geolocation data of the users.
This is how Adherent works, a platform to connect the users of a city.

Challenges we ran into

In a span of 36 hours, the main thing to achieve was the UI, with two technologies involved in frontend, Flutter and ReactJS, it was a challenge for the team to pull off the design in time. With the UI complete, the backend developer started working on the django framework to build the server, building the model and creating API endpoints for the frontend developers.
With django, the hurdle was the hosting, we managed to host it on heroku server.
With react, each component had to be responsive, with bootstrap it was slightly easier, then creating custom hooks to work with the geolocation and server API was a long process.
With 4 members working, we had multiple branches for each dev, on pull request creation, we had merge conflicts, so we took backups and fixed them.

Discussion