Inspiration
For our idea we brainstormed for more than an hour before deciding on a product that could solve a problem all of us have experienced, the pain of dealing with all 300 job applications sent you've out this year. We wanted something to manage all of that was as little effort from the user as possible.
What it does
Our app grabs job listing information after you've applied or shown interested, then records it and displays it to you in an easy to digest form. It takes application data (by URL or manual input), and saves it into a local database for recall.
How we built it
Our main stack was React Native, wrapped with Expo. We wanted to build an app that was multi-platform so anyone can use it. Javascript was the main scripting language and Github helped us coordinate throughout the development period.
Challenges we ran into
React turned out to be a major misstep for a group of our skill level. Parts of the project that we planned to be done with in an hour took 7, and there were many, many errors during every hour. While Expo is a great tool for rapid development, many of those features were unappreciated until much later due to our experience. Storage was another major issue, with several technologies tried before seeing any success.
Accomplishments that we're proud of
The app launches! We've been on a roller coaster of emotion going from complete confidence, to absolute misery, and here and back and again. Storage was one of the biggest win once it was finally working, and seeing the design come alive with data was extremely gratifying!
What we learned
React is hard! Many of use learned a lot of Javascript, and a wide range of it as well! Github was also something fairly new to most of us, and we've all improved our collaboration skills while working on a project for so many hours.
What's next for InternApp
OCR was a major selling point in our idea, we envisioned a camera option and you can take a picture of your PC screen after finishing a Linkedin application, for example. This was cut due to scope, and time restraints. We'd also love to upgrade to a more scalable database in future revisions. MongoDB was mentioned a lot, but we didn't want to try too many new technologies at a time.
Log in or sign up for Devpost to join the conversation.