• With the pandemic going on and people being secluded in their homes, it was inevitable that the people would lose their social skills. This included stage fright giving rise to an idea that stemmed from making a public speaking app that people could use to give small speeches in front of an audience and get feedback on how they did. The point of this was to help people grow more confident in front of others.
  • Since this hackathon targets solving social and economical problems we decided to target upskilling and reskilling the workforce and the people of our world. We wanted to create a project that could help people of all types and interest them to discover new talents that would prove to be helpful.

What it does

  • BeAce lets a user browse through the different types of skills that are available on the discover page.
  • The user can look through the videos and the images, learn from them, or even around their own passions. They can even like the post (using our symbol of '100' to support the person who had posted their talent)
  • Moreover, if they want, they can even choose to share some of the pictures they drew up, photos they took, songs they sang, and even create recordings of their own code to help others learn.

How we built it

  • We built BeAce using MIT App Inventor.

Challenges we ran into

  • Originally we were going to build this app using Java, but then our team member, who was supposed create the frame of the app, ran into some issues and we didn't get the frame done on time.
  • Luckily, both Ashita and Harshita started working on a backup plan in case the app was not ready.
  • Since it was already Friday when Ashita and Harshita started the backup plan, we had to work late into the night to have a finished project (they pulled a whole nighter as they did not sleep the entire night of Saturday)
  • Also working with MIT App Inventor itself was a challenge since it's set limited some of our features. One of these features being the number of screens we could have in our app
  • The set of MIT App Inventor also made it slow and tedious when creating new screens with the same format or even "copying code"; everything had to be done by hand showing the dedication we had to commit to the project.

Accomplishments that we're proud of

  • We are proud that we were able to complete the video and the app on time and turned it, despite the setbacks we were presented with.
  • We are happy that the app is what we had thought of earlier and accomplishes the given tasks.
  • We are also thankful that the app itself is well designed in terms of its appearance.
  • The fact that it fully completed is an accomplishment in itself.

What we learned

  • If there has been very little communication from a team member(s), it is usually a good idea to start on a backup option much earlier
  • Cohesively working is extremely challenging, and it takes heavy cooperation on both sides in order to create a meaningful project.

What's next for BeAce

  • In the future, we would like BeAce to be created on a different platform/use different software because the size of this app makes it not the fastest on MIT App Inventor
  • We would also like to add more skills to the app such as game development, dancing, and possibly even a page to show good research skills
  • We would also like to improve the graphical design of the app because right now it does not look as refined as other published apps
  • Lastly, we would like to make business partners, all around the world, that would be willing to invest in our project


Trisha was not able to contribute as much because of family reasons, and thus, she is also not present in the video.

Built With

Share this project: