Overview
A notice on a physical board reaches the students who walk past it. This app puts the same notice on their phone.
The constraint was the devices in the audience's hands: entry-level Android, unreliable campus wifi, tight data budgets. That ruled out a heavy client on day one.
- Role
- Sole engineer and designer.
- Year
- 2024
- Stack
- JavaScriptReactNode.js
Engineering
The decisions that mattered.
- 01
Built for low-end devices
Minimal client-side weight and aggressive caching, so notices load on entry-level hardware over intermittent wifi.
Design decisions
Why it looks and behaves the way it does.
I designed this as well as built it. These are the interface calls I made and the reasoning behind each one.
Newest first, nothing clever
No categories, no filters, no personalisation. For a notice feed, reverse-chronological is the right answer, and anything on top of it adds interaction cost for no return.
Readable at arm's length outdoors
Type sizes and contrast were set for bright sunlight on a cheap screen, which is where students read this.
Outcomes
What shipped.
- Notices delivered without a noticeboard visit
- Usable on entry-level Android and campus wifi