Personal product · 2026 · In testing
Loggr, your logbook finished
Turns a Nigerian student's handwritten SIWES logbook into a school-format report, then helps them defend it and build a CV.
- Role
- Product designer and builder. I designed it in Figma and built it with Claude Code.
- Tools
- Figma, Claude, Claude Code, Gemini, Supabase, Vercel, Paystack (test mode)
- Platform
- Mobile-first web app
100%
of six handwriting styles read correctly in Gemini tests
Test result
98.5 to 100%
of characters read from real logbook photos
Test result
24 s to 9.5 s
payment, tap to unlocked, on slow 3G
Test result
190+
automated tests on every change
Test result
The problem
Nigerian students on SIWES (industrial training) keep a handwritten logbook. At the end, they have to turn it into a typed report in their school's exact format, defend it in front of a panel, and later write a CV. The tools that exist only take typed input, don't connect the report, defence and CV, and some write the student's work for them.
What I designed and built
- Handwritten logbook to report: the student photographs their logbook pages, Loggr reads the handwriting, and it builds a report in their school's format as PDF and Word.
- Defence and project prep: slides built from the student's own report, a speaker script, likely panel questions, and "Loggr Coach" practice with spoken answers and honest scoring.
- CV and resume builder for anyone, not just students: templates, checking a CV against a job advert, cover letters and a LinkedIn helper.
- Daily logbook companion: typed or voice notes each day become entries, so the report almost builds itself.
- Also: a Chapter 2 organogram, a supervisor comment link, free GPA and sample size calculators, referrals, a Season Pass, Paystack payments (card, bank transfer and USSD) and a welcome video with an AI voice.
Principles I designed by
- Honest by design. Loggr never invents work, data or results, and never writes the student's project. Every sentence in a report has to trace back to the student's own entries.
- Built for cheap Android phones and slow data. I test at 360px with Android's own fonts (Noto and Roboto), and open the Word files in WPS Office, because that's what students actually use.
- Plain language for first-time users.
Test results
These are measured results from my own testing, not usage numbers (there are no real users yet).
- Six handwriting styles were read 100% correctly in Gemini tests. On real logbook photos, 98.5 to 100% of characters were read at the photo size I chose after comparing three sizes.
- On slow 3G, the time from tapping Pay to the report unlocking went from about 24 seconds to 9.5 seconds.
- 190+ automated tests run on every change.
How I work with Claude Code
I write detailed briefs, then review every build frame by frame. That's how I caught problems before any student did:
- slides silently dropping a student's points
- PowerPoint files that would show a "Repair?" warning in Microsoft PowerPoint
- text overflowing on Android fonts
- invented sentences appearing in the report
- a referral credit that could be used twice
Where it is now
Loggr is in testing and isn't launched yet. There are no real users, testimonials or revenue yet. Next, 2 to 3 students will test it, and I'll update this page with what I learn.
