Inspiration
Recall Rush was inspired by sites like Quizlet and other flashcard based applications like Anki, where students and users can do active recall by flashcards and memorization over time.
What it does
- Deck + Subject Organization: Create/edit/delete decks and subjects, assign decks to subjects, and color-code subjects/tags with a dedicated left sidebar for quick filtering and navigation.
- Quiz Workflow: Run quizzes per deck with typed answers, auto-grading, manual correct/incorrect override, confidence selection, and immediate progression through cards.
- Performance Analytics: Track recent, average, best, and average-confidence scores; view detailed history; and explore score trends in an interactive chart with hover details.
- Attempt Activity Tracking: See GitHub-style quiz-attempt heatmaps per deck (with labels and intensity by attempt volume) to visualize study consistency over time.
- Study Planning Calendar: Plan deck study by date using a calendar view, assign/remove decks per day, and manage day-by-day study schedules from a dedicated planning interface.
How we built it
We built Recall Rush first through a rapid prototype and then iterated through the product over time with changes and new features.
Challenges we ran into
One challenge we ran into was getting the API to work. As we did not have experience with using APIs directly with an AI before, let alone Google's AI Studio, it was a challenge to even get it working.
Another challenge we faced was coordinating our work so that each person was working on different features at a time to prevent merge conflicts in the GitHub repository.
Accomplishments that we're proud of
We are proud of us being able to work in a team where most of us have never been in a hackathon competition before. We have been able to collaborate despite this and create a viable working project as a result.
What we learned
We learned how to utilize APIs with Gemini API through Google AI Studio. We also learned how to cooperate within our project to not cause issues. In addition, we also had to learn to scope our project so that we did not run into problems with ideas for new features that were not able to be implemented in time.
What's next for Recall Rush
The next step for Recall Rush is a short answer evaluator. While Recall Rush works great with memorizing short terms, when an answer gets long, it can cause issues through a single piece of text not matching the answer causing issues. Another step is allowing users to edit the names of their decks once they have created them.
After that, creating a database and adding user accounts to store their decks and progress would be the next step to allowing users to access their decks from more than one device.
Built With
- next.js
- node.js
- tailwind
- typescript
Log in or sign up for Devpost to join the conversation.