The problem Unishop solves

When a student arrives to a new city for his studies (in Universities/Colleges), he/she faces a long requirement of stuff they might need to settle in the city/campus. Such may include essentials for living in a new flat, or modes of transportation, or certain books, or other recreational items like sportswear and Gym Essentials.
Our Web Application 'UniShop' will provide these students with a platform through which they can fulfill some of their needs in a cost-effective way. Similarly, other students or seniors can also make up a profit by selling their stuff which are unneeded while they leave their colleges.
You can argue that we have apps like OLX for such purpose but these apps are implemented on a national city-wide scale which makes it less efficient whereas our website will be based locally on the college level whereby students(seniors and freshers) can interact and go ahead with the transaction almost immediately. They can decide a meeting place and the mode of transaction on their own which provides a lot of flexibility and safety over apps like Olx and Quikr.
Each college will have its own set of students selling and buying items.(We have implemented it for 3 colleges as of yet but our product can easily be scaled up to accomodate multiple students and colleges across India).

Challenges we ran into

During the course of making this project, we ran into a number of problems but i'm proud to say that we managed to overcome all of them one way or the other and have a finished product at our hands with time to spare.
Our First hurdle was connecting to a database. We had started the backend on NodeJS initially but due to our lack of experience, we were unable to connect it to the database. Udipt had worked with Phpmyadmin before so we had to switch to php and start all over again which hindered our progress.
Debugging is an integral part of development and Stack Overflow is our go-to friend but it may become an huge issue if even stack overflow cannot debug your code. One such bug stood in our way while we were implemention google login button or google oauth2.0 .We had to scratch our heads for a couple of days and go through the entire github repo of the google-api-php-client to figure out that our php version was not compatible with the version of the apiclient we were using. (They need to do a better job at displaying error messages more precisely).