One of our team members recently visited a national park and saw how inefficient and outdated their tour system was. After talking, we soon realized that this inefficiency was also present at OU with their campus tour system. Normally, when a OU tour is at capacity the student is handed pieces of information and sent on their way. We thought that this process could be improved. Our project is supposed to be a system that allows for prospective student to get all of the information they need for a full tour on their phone as they maneuver around campus. We planned on accomplishing this through the use of AR, text-to-speech, and geolocation. As our team changed over time, we scaled it back significantly but are still very proud of what we accomplished.

What it does

Mobile Guided Tours makes tours that are normally generic and hard to hear, and turn them into relevant, self-paced tours. We use Near Field Communication or NFC chips to provide a low profile way for users to be directed to more information about what they are looking at.

How we built it

We used various web templating technologies like Bootstrap to layout the front end of our website. We then used Google Cloud Functions, SQL, and Compute Engine to host a dynamic backend that allows adopters of Mobile Guided Tours to make adaptive tours at a moment's notice.

Challenges we ran into

We initially had several issues involving permissions and API keys associated with Google Cloud Platform. Though after taking to a mentor and some peers, we were able to get these issues resolved. In addition to this, we had to educate ourselves in a few different GCP hosting methods.

Accomplishments that we're proud of

We came into this hackathon with intentions of having a full 4 member team, but due to circumstances outside of our control, we forced to work at half capacity. This being said, our two person team rose to the challenge and made an end product that we are very proud of.

What we learned

We learned a lot about pushing our boundaries by opting to use technologies that were new to us. While at times it was stressful, it proved to be ultimately rewarding and educational. By losing a few of our expected team members, we could not fully realize our goals for the project but we got enough done to form a good foundation for what we believe could eventually grow into a fully realized project.

What's next for Mobile Guided Tours

Because of the way we built Mobile Guided Tours, if any other school, museum, or national park wishes to adopt our system, all we he have to do is reskin our front end and add another database to the backend. We would also like to continue to expand on the feature-set of the program and implement the various functionalities we were unable to get done in our limited time.

Share this project: