-
-
Skill-Issue's key features.
-
A screenshot of Skill-Issue running on the MacBook Neo and the iPad.
Inspiration
As students, we're often time and money constrained. We wanted an app that would quickly find us a partner who we could learn from, however tutoring is expensive. So instead of paying for tutoring with money, why not pay by tutoring the tutor? Everyone gets to learn together!
What it does
A user would sign up, describe the skills that they can teach and the skills that they'd like to learn. Our AI would then match them with another Skill-Issue user, who can teach them the skills they want, but also learn from them. This meeting would be automatically setup via Google Meet, with details sent to each user's Gmail.
How we built it
We first brainstormed our own individual ideas, then created a plan of features we wanted to implement via MoSCoW prioritisation. We utilised Google's Antigravity to iterate fast, adding features, fixing bugs and polishing to our best ability.
Challenges we ran into
Our biggest challenge was absolutely differentiating our app from those that already existed in the market. We decided on 2 key differentiators; deep Google integration and Skilliton. Google has an extensive ecosystem of products and userbase, so we chose to capitalise on it. Skill-Issue directly connects to Google Meet, and sends matched users an email containing the booking details, making it quick and simple. Our anxious mascot, Skilliton, helps ease users and liven the app a little, since we understand that meeting up with a completely random stranger can feel daunting.
Accomplishments that we're proud of
We're so happy with how the final app turned out. The Google integrations turned out quite well, giving our app real utility that users would absolutely appreciate. The app itself is adaptive to mobile, tablet and web views, which is great for accessibility and really making it universally available.
What we learned
We learned that planning is absolutely crucial, especially when attempting spec-driven development. Without a concrete plan, time is wasted on fixing guesses, rather than actually contributing towards our vision. It's also very important to listen to everyone's concerns, since our project truly is a collective representation of our teamwork during UNIHACK.
What's next for Skill-Issue
A native mobile app based on Expo/React would be a great next step, since phones are becoming more and more practical for real productivity. We'd expand into creating educational resources that could be used as a starting point for our users. If this were to become a commercial project, we'd also look into monetisation strategies such as subscriptions or gamification techniques like streaks/XP to try and build user retention.
Log in or sign up for Devpost to join the conversation.