Few lines describing your project.

• 📝 Table of Contents
• 🧐 Problem Statement
• 💡 Idea / Solution
• ⛓️ Dependencies / Limitations
• 🚀 Challenges
• 🏁 Getting Started
  • Prerequisites
  • Installing
• 🎈 Usage
• ⛏️ Built With
• ✍️ Authors
• 🎉 Acknowledgments
• Resources

Team O noticed the inefficiency in Foothill's current LCR Learning Resources Center). We all have experienced that feeling of being stuck in a homework question. It would be absurd to book a 30-minutes appointment to resolve this problem. Even the drop-in session can feel very awkward if we only ask a single question. Most of the time, we ended up guessing or searching the answer online without fully comprehending the topic. Owl Tutor aims to resolve this problem by connecting the Foothill community and enable these questions to be answered in a community-driven discussion forum.

The app has 3 main features: dashboard, appointment, and forum. The dashboard is presented in the main page and acts as a to-do list for the students. The dashboard allows students to get an overview of their days/weeks. The appointment features presents a user-friendly and easy-to-use interface that connects students with tutors pertaining to a particular subject. Lastly, the forum is a discussion space where students and tutors are able to answer course-specific questions. The app is personalized for each user as it utilizes Canvas API integration that provides almost all the data we need

Owl Tutor uses React Native (frontend) and Firebase (backend) as well as Canvas API. Additionally, presentation video is made through canva.com

There are a lot of problems that we ran into such as Canvas API implementation. Canvas API documentation was vague with some of its components not working properly. One major problem, however, was the authentication system. In order to access the OAuth2 system, it requires a devkey which can further complicate the data structure and implementation. Another problem we ran into is processing data format output. The user ID for canvas students has more than 16 digits of number and is outputted as an integer. As a result, an integer overflow occurs and the user id outputted does not match the actual one. Other challenges include UI/UX design, presentation, and time managements as Team O only consists of 2 members. A less technical challenge include academic integrity for app usage.

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

• nodejs
• yarn

A step by step series of examples that tell you how to get a development env running.

yarn install

yarn start

• React Native - Mobile App
• Firebase - Backend
• Expo - Runtime

• @oliverchou - Idea & Initial work
• @christopher-kusmana - Video, Paperwork, Idea, UI/UX Design

See also the list of contributors who participated in this project.

• Hat tip to anyone whose code was used
• Inspiration
• References

• devpost link