From Student Friction to Product: Founding the BrainBash Learning Engine
How I founded BrainBash to solve fragmented exam revision for undergraduate students, and the technical decisions behind building an offline-resilient study platform.
The Real-World Friction
During my university journey, an inescapable challenge emerged every semester: examination periods were accompanied by sheer panic. Course past questions were scattered across paper handouts, unofficial WhatsApp groups had conflicting answer keys, and students had no way to test themselves under real exam constraints.
Instead of accepting the status quo, I decided to build **BrainBash**.
Engineering for Low-Bandwidth Campus Conditions
Campus Wi-Fi in emerging markets is notoriously unreliable. If a student loses internet connection mid-way through a 50-question mock exam, losing their progress destroys trust.
We implemented client-side state resilience: - Test questions, options, and explanations are preloaded in indexed client memory. - Every student answer selection is immediately persisted to `localStorage` and cached in React Context before syncing to the cloud. - If the network drops, the timer continues uninterrupted, and answers sync automatically once connectivity restores.
Product Outcomes
By designing for the realities of the end-user rather than ideal Silicon Valley internet conditions, BrainBash became a trusted study companion for students across campus departments.
As an engineer, founding BrainBash taught me that technical excellence is meaningless without deep empathy for how your users interact with software in the real world.