This project started from something I kept seeing in my own school. During parent–teacher meetings, many parents stood near teachers with their phones open, asking basic things like, “Where do I check attendance?” or “How do I download the fee receipt?” It happened so often that I realized it wasn’t about parents “not knowing technology” — the apps simply weren’t designed for them.
One moment that really inspired me was when a parent said, “Everything is here, but nothing tells me what to press.” That made me understand that the real problem is design, language, and confidence—not intelligence. This is what led me to build a solution that explains confusing school portal pages in simple, friendly steps.
While working on this idea, I learned how important user empathy is. Designing for someone who feels anxious using apps forced me to think differently and break tasks into very small steps. I also learned that accessibility is not just about adding features; it’s about removing stress.
To build the project, I first listed the main issues parents face: English-heavy text, too many buttons, confusing layouts, and fear of “pressing the wrong thing.” I looked at real portal screenshots to understand what was unclear. Then I created an MVP concept: a helper tool that takes a screenshot and turns it into plain-language instructions, with support for local languages and voice guidance.
I did face challenges. One was making explanations simple without losing important details. Another was designing something that works for different kinds of parents with different struggles. I also had to stop myself from making the project too big and focus on a realistic MVP.
Overall, this project taught me how design can either include people or leave them out. My goal is to help parents feel confident and supported when using school apps — and to reduce the stress they often feel with digital systems that weren’t made for them.
Log in or sign up for Devpost to join the conversation.