BeActive

Inspiration

The problem we are trying to solve through BeActive is one we ourselves faced as college freshmen. As an anecdote, there was a talk on economic justice organized by the Philosophy department that one of our team members couldn't go to because they didn't know it was happening. This was because the only way it was being propagated was through a flyer on the second floor of the humanities building. There's an unfortunate communication gap between people who are truly interested in going to events about causes they believe in and those who work to organize these events. Bridging this gap for ourselves and all the people around us is the inspiration.

What it does

There are two interfaces to the web app. The first interface is concerning event organizers who can make a post about their event and specify the title, date, time, description, and other information depending upon how they want to present it. The second interface is for those browsing for events to go to. They can filter through events based on the tag (type of cause) they are interested in. They can show their interest and see others who have shown interest in attending the event. They can also post questions and talk about the event with other people in the discussion section of the post.

How we built it

The web app heavily relies on Vue js and apart from that it uses quasar for the UI elements. In addition to this, it uses scss and typescript for implementing certain components.

Challenges we ran into

This was the first hackathon for most of us, so it both fun and tiring. We were all working on components differently so when we merged in the end it was a bit of a problem and took some time. We also learned some of the technologies that we used to build the app as we were building it, so that was challenging too.

Accomplishments that we're proud of

We ended up sticking till the end and finished our first hackathon project. We had a lot of fun doing it and learned a lot.

What we learned

We spent a lot of time planning before we wrote the first line of code and that saved us a lot of time and issues while actually writing the code. So we learned about the importance of having a fleshed-out map of what, how, and when to do stuff.