Late nights, design decisions, and code commits — the quiet, unglamorous work of building a school management app from the ground up in Karachi.
Building the Identity First
The first thing any product needs before it can exist in the world is a face — something that makes it recognisable and communicates its values before a single word is read. For School Connect, that meant building a visual identity that felt warm, trustworthy, and distinctly Pakistani, without leaning on tired design tropes.
Thanks to Canva, my ideas could finally take shape without the weeks-long back-and-forth that outsourcing design would have required. What once lived only in my head began to have a face — colours, letterforms, a logo that felt like the product it would represent.
I spent hours refining the right palette and typeface combination. My philosophy was specific: it had to communicate connection — friendly and warm, slightly informal, but still confident and intentional. Not the corporate blue of traditional school software. Not the aggressive brightness of consumer apps. Something in between. Something that could sit comfortably in a parent's hand at 7am on a school morning.
Why I Didn't Outsource the Design
I didn't hand it to a professional designer — at least not at this stage — because I felt the essence of what School Connect should feel like lived in my head and heart. A designer working from a brief would deliver something technically proficient but potentially missing the emotional core that made this idea worth building in the first place. The warmth had to come from within.
Building the Product, Feature by Feature
From there, development moved to Adi — my husband — who took on the engineering side of School Connect. He is fast, methodical, and most importantly, he listens. That matters more than it sounds. Many products fail not because the engineering is bad but because the gap between the person with the vision and the person with the tools is too wide.
Quietly, after the lights dimmed and the kids went to sleep, we started building. Step by step. Screen by screen. Feature by feature — attendance, then homework notifications, then fee collection, then the parent activity feed. Solving one problem before moving to the next, never skipping ahead.
It took weeks. But every feature that worked felt like proof that the whole thing could. The foundation was taking shape.
