In many urban areas in the US, the number of people per day who go outside and appreciate local stores, restaurants, museums, and landmarks has significantly dropped over the past twenty or so years. We hope to make an app that is able to somewhat alleviate this stress on the physical and mental health of residents. In addition, we hope to bring back money to local art institutions such as orchestras and museums, which have felt the rise in popularity of online entertainment.

What it does

Where-you-at is an augmented reality web app which should encourage people to travel and visit local 'hotspots' by awarding them points and cosmetics for visiting and sharing pictures. In reality, it allows users to create quests and to complete them for points.

How we built it

We built it the initial algorithm using HTML, JavaScript, and Python while implementing Jinja and Flask. We then implemented CSS in order to make the web application visually appealing. Additionally, we attempted to utilize Google Maps API in order to add location functionality; currently, the algorithm is capable of finding a user's current location.

Challenges we ran into

We ran into a lot of challenges. None of the team members had written backend code before and it was particularly difficult to develop a fully functioning log-in system. From there, we had difficulty marking quests as completed; while they can be easily removed from the database, it is necessary to identify which listed quest was selected as complete. Similarly to identifying the quests, it was difficult to access the value field of individual quests, making adding a user's points complicated. In terms of Google Maps, there were many issues with geolocation, and we often found ourselves "in the middle of the ocean." Our frontend developers were also new to HTML/CSS, and therefore had trouble linking pages and generally establishing a functioning HTML/CSS webpage.

Accomplishments that we're proud of

We are proud of having completed a quasi-functioning product in which users are saved in a database, meaning that there are multiple 'accounts' on our platform. While we were unable to implement passwords at this point, registration with a username is noted and, should one enter the same username again, they will log into the original account rather than creating a new one (two accounts cannot have the same username). We were also able to create quests and have them listed on the website, as well as have points update in real-time. Furthermore, we are proud of our frontend development as we have little experience using HTML/CSS, and are certainly proud of successfully implementing the Google Maps API.

What we learned

We learned both frontend and backend web development through this project; accordingly, we all feel more comfortable using HTML/CSS/JavaScript and will definitely be delving deeper into web development soon! Additionally, we learned how to work with APIs and how to better debug our code (there were a lot of problems).

What's next for Where U At?

The future for Where U At? involves the further implementation of Google Maps API in order to track users and verify that they have reached a 'hotspots.' In that way, there will be further verification as to whether a quest has truly been completed (if you're putting in the effort to trick the application to think you're somewhere else... you probably shouldn't be using it). Additionally, we are looking to better integrate our front and backends and to cumulatively improve the design/ aesthetic of the overall application. Moving into our backend, we will improve quests in that they will be removed from a user's home screen once they are completed, and that points will be (accurately) added. Lastly, our original concept involves the interaction of 'clients' and 'users.' Clients will have a separate login which will allow them to create quests for desired hotspots; these quests will then appear for users in the relevant area.

Share this project: