Crispio

Crispio started as a simple to-do list project, part of a web development course I was doing back in Class 12th. But I was never someone to leave a course project as it is — I always liked adding new ideas on top, and this one ended up becoming something much bigger than a basic to-do app. It turned into my first proper full-stack project, complete with social login, user profiles, and a fully working PWA (Progressive Web App) that could be installed directly from the browser, just like a native app.

At that time, I was quite interested in how social media apps work, and that thinking naturally found its way into Crispio. I added profiles to what was originally a plain to-do list, and to make that meaningful, I introduced different visibility levels for tasks. Public to-dos could be seen by anyone following the user, while exclusive to-dos were visible only to people selectively shared by the author. All of this appeared in the follower's "following feed" — much like how posts show up on a social media timeline, except here the "posts" were tasks.

This kind of setup can be genuinely useful for trainers and mentors, who could assign tasks to their students either publicly or privately, much like posting an assignment on a social feed. I made sure the entire UI was complete — no button or CTA was left unconnected — and all core functionalities, including to-do creation, updating, task assignment, and authentication, worked properly end to end. For a first full-stack project, getting everything functional and polished was, honestly, a big milestone for me.