Connisewer

toilet page
route

Inspiration

wherever you are, there will always be times when you need to do your bussiness. During these times, even in familiar areas you might not know where the best toilets are at the moment. So, we thought of a way that allows us to get this information with ease, and that is resulted in Connisewer.

What it does

Connisewer is a web app that helps users find the best, clean toilets in their area.

Connisewer features include, but not limited to:

real-time reviews and rating, location, facility conditions and amenities
location-based searches
making a review, which has rating as well
interactive map

How we built it

First, We decided to make it with a seperate front-end and back-end, and since we have 4 people in our team we had 2 people working the front-end and 2 working the back-end. Then, we had a couple of stages in the making of this project, The front-end was first designed alongside deciding what technologies to use in it.

We thought about which database we were going to use and didn't really think about whether we were going to use a seperate back-end or not. In the end, we ended up choosing MongoDB for it's object oriented like database. Then there were several languages that were brought up for the backend like javascript and python, but also C++ and Java, However because we thought for it's compatibility and convenience, either javascript or python would be the best choice and since the backend team was not really fond of javascript, we ended up going with python.

We discussed on what features the web app would have but there was no definitive process in the making of it, there were also several features which were added either as a standalone feature or alongside some pre-decided ones.

The front-end mainly uses:

next.js
create-next-app
tailwind css

while the back-end mainly uses: Python and MongoDB.

Challenges we ran into

For the front-end the challenges were mainly in trying to interact with the back-end as we don't really have much experience with a seperated back-end. Now most of the challenges came from the back-end with Flask API and MongoDB. We were really unfamiliar with MongoDB in general and so that was a really big part of the challenge. Setting up the database, interacting with the database, querying, and manipulating the data were all the biggest challenges. However, the second biggest challenge was really deciding on what database structure we would be using, we were quite confused during production with a lot of changes happening to the database structure. Second, one of people in the back-end team was not really familiar with the flask API and so going implementing routes were a little bit of a challenge in the start but probably not as much when were implementing sessions and access tokens in the logins and user signups part of the projects, we weren't familiar with flask_session and JWTs

Accomplishments that we're proud of

the completed design of the front-end as well as making it work and interacting with the back-end
just the mere completion of success of implementation for the whole entirety of the back-end, the things were most proud of are probably in managing to arguably effectively interact with the database, and making the database work in the way we wanted it to.