Inspiration

What it does

The InspirationThe inspiration for this project came from a simple, personal observation: the gap between "having a plan" and "executing a plan." As an engineering student, my desk was often covered in sticky notes, and my phone was full of generic reminder apps. However, none of these tools understood the nuance of a student's life.I realized that we don't just need a list of tasks; we need a navigational system. Much like a GPS calculates the best route based on traffic, I wanted to build a tool that calculates the best study route based on deadline "gravity" and task complexity. I applied Design Thinking—starting with the "Empathy" phase—to understand the cognitive load students face when balancing technical subjects, lab reports, and language fundamentals.How I Built ItI approached the development as a Full-Stack challenge to ensure a seamless connection between the user interface and the underlying logic.Frontend: Built with React, focusing on a clean, distraction-free UI. I used a modular component structure to allow for a "Roadmap View" and a "Deep Work" dashboard.Backend: A Node.js and Express server manages the logic, specifically the algorithm that ranks tasks.Database: I utilized MongoDB to store user-specific task data and resource links, ensuring that study materials stay attached to their respective assignments.Logic: I implemented a Weighted Priority Algorithm to determine which task should be tackled first.$$P = \frac{(W \times C)}{D}$$Where:$P$ is the Priority Score.$W$ is the Weight (importance) of the assignment.$C$ is the Complexity (estimated hours/effort).$D$ is the Days remaining until the deadline.Challenges FacedOne of the biggest hurdles was Data Overload. Initially, the dashboard was too busy, which defeated the purpose of reducing anxiety. I had to go back to the "Ideate" and "Prototype" phases of Design Thinking to strip away non-essential features, eventually landing on a "One-Task-at-a-Time" focus mode.Technically, managing State Persistence across the various views (Calendar vs. List vs. Focus Mode) required a robust state management strategy. Ensuring the algorithm updated in real-time as deadlines approached without lagging the UI was a significant debugging journey.What I LearnedThrough this project, I moved beyond just writing code to solving a problem. I learned:Iterative Development: Your first version will be messy; the magic happens in the refinement.User-Centric Logic: A feature is only "cool" if it actually reduces the user's stress.Technical Integration: Connecting a frontend to a database taught me the importance of clear API documentation and data security.Student Task Navigator is more than an app; it is a reflection of my journey to master my own workload and help my peers do the same.

How we built it

Challenges we ran into

Accomplishments that we're proud of

What we learned

What's next for Productivity: The Student Task Navigator

Built With

  • apis
  • cloud-services
  • databases
  • frameworks
  • platforms
Share this project:

Updates