The idea started when we were signing up for our classes this quarter at UCSB. We wanted a faster way to import our class schedules into our default calendar on our phones. That is how we came up with PlanR.

We have many features we hope to implement for PlanR. The application's main feature will be for class schedules in which PlanR will allow users to import an image of their schedule and convert that into events on their calendar. Other features for PlanR will hopefully include recognition of events in messages and emails or plans to attend events on social media, and integrating the events into user's schedule.

We want to give users the full experience of easy scheduling by implementing other APIs such as SMS, Facebook, Twitter and Gmail to create a wholesome application.

Our final product is simply our worst case scenario for what was planned for PlanR. We did not have enough time to work out implementations of the features we wanted such as social media events integration, messaging integration, and automatic scheduling. However, we did get a working application that takes in the user's schedule image, specifically a UCSB schedule, takes the information, and translates it into the user's calendar app as scheduled events.

We faced many challenges taking this project head on. One of them was learning the different APIs that we wanted to implement and trying to make them work throughout PlanR. Our ideas and concepts for PlanR could have been done, however, the implementation was more difficult than expected. In the end, we decided to scrap it and stick with our worst case scenario as our final product of the application.

Overall, we learned that a project as large scale as this should have better planning and execution as to when things should be done. We should have researched the different APIs earlier and learned how to use them concurrently in one application. Since we did not, we ended up with a product that could be heavily improved for the state that it is in.