Inspiration

We started EduMind AI after noticing a simple problem with online assessments. Students usually receive a score after completing a test, but the score does not always explain what they should study next.

For example, two students can both score 60%, but their actual difficulties can be completely different. One student might struggle with normalization while another might have problems with transactions or indexing.

This made us think about a different approach: instead of treating the test result as the final output, can we use it to decide the student's next learning step?

That question became the starting point for EduMind AI.


What it does

EduMind AI: Adaptive Personalized Learning Intelligence analyzes a student's assessment performance at the topic level.

A student takes an assessment, and the system examines their responses to identify:

  • Strong topics
  • Topics that need improvement
  • Repeated mistakes
  • Learning priorities
  • Progress between assessments

The platform then recommends what the student should focus on and generates targeted practice questions and explanations based on the identified learning gaps.

For example, if a student studying DBMS performs well in SQL but struggles with normalization and indexing, EduMind AI does not simply display the overall score. It prioritizes those weaker areas for further practice.

The learning cycle is:

Assessment → Analysis → Gap Detection → Recommendation → Practice → Reassessment

The objective is to help students answer a question that ordinary test systems often leave unanswered:

“What should I learn next?”


How we built it

We built EduMind AI as a full-stack web application.

The frontend was developed using React and Vite, with interfaces for assessments, results, recommendations, and progress tracking.

The backend uses Node.js and Express.js for handling authentication, assessments, responses, performance processing, and communication with the AI services.

We use MongoDB to store student profiles, questions, responses, topic-level performance, and assessment history.

The AI component is used for generating personalized practice questions and explanations according to the student's identified learning gaps. The application also processes structured assessment data to determine topic-level performance before creating recommendations.

We added visual analytics so students can compare their performance across topics and see whether their weaker areas are improving over multiple assessments.

We focused on making the system a complete working cycle rather than building an isolated AI feature.


Challenges we ran into

One of our main challenges was deciding how to identify a genuine learning gap.

A single incorrect answer does not necessarily mean that a student does not understand an entire topic. We therefore avoided making recommendations based only on one mistake and instead considered performance across related questions and topics.

Another challenge was keeping AI-generated content relevant. If a student is struggling with normalization, generating a completely unrelated question would defeat the purpose of personalization. We therefore provide the relevant topic and learning context when generating practice material.

We also had to decide which features were realistic to complete within the hackathon timeline. We had several ideas, but instead of creating many incomplete features, we concentrated on completing the core learning cycle.


Accomplishments that we're proud of

We are proud that we turned a simple idea about personalized learning into a working full-stack prototype.

Some of the things we successfully brought together are:

  • Topic-level assessment analysis
  • Learning-gap identification
  • Personalized recommendations
  • AI-generated practice questions
  • AI-assisted explanations
  • Student progress tracking
  • Visual performance analytics
  • Frontend, backend, database, and AI integration

More importantly, we were able to connect these components into one continuous workflow.

A student can take an assessment, understand their weak areas, receive targeted practice, and return for another assessment. That complete loop is the part of the project we are most proud of.


What we learned

This project taught us that adding AI to an application is not simply about connecting an API and displaying its response.

The useful part is deciding where AI actually adds value.

We learned how assessment data can be converted into meaningful learning information and how that information can be used to personalize the next activity.

Technically, we gained experience in connecting a React frontend with backend APIs, storing assessment history in MongoDB, processing structured performance data, creating interactive analytics, and integrating AI-generated content into a full-stack application.

We also learned an important product lesson: a feature can be technically impressive but still not be useful unless it solves a real user problem.


What's next for EduMind AI

Our current version focuses mainly on assessment-based personalization. The next version could make the learning profile much richer.

We want EduMind AI to eventually consider:

  • Long-term learning patterns
  • Previous mistakes
  • Learning pace
  • Question difficulty
  • Preferred learning formats
  • Improvement trends
  • Teacher feedback
  • Course and syllabus progression

We also want to introduce a teacher dashboard where educators can see common learning gaps across a class without having to manually inspect every student's test.

Another planned direction is a dynamic difficulty system, where the difficulty of the next question changes according to the student's demonstrated mastery.

Our long-term vision is for EduMind AI to become more than an assessment platform. We want it to act as a continuous learning companion that helps students understand where they are, what they need to improve, and what they can do next.

The goal is simple:

Don't just measure learning. Use the measurement to improve it.

Built With

Share this project:

Updates

Submission history