Why I built Voino
In a lecture or meeting, I want to follow the discussion instead of typing the whole time. Afterward, useful points can get lost in a long transcript. Voino turns captured words into notes I can review and a visual board I can edit.
What it does
Voino is a Flutter Android prototype. Tap the mic to capture an editable live transcript, or type and paste text instead. The default note extractor uses rules, not AI. Review its key points against the transcript, then make a board with editable cards, arrows and shapes. Listening, notes, board editing and text export stay free.
How I built it
I used Flutter and Dart, speech_to_text for Android speech recognition, and a custom hand-drawn board. RevenueCat's purchases_flutter SDK connects the Android Test Store to the voino_pro entitlement. Test Pro gates board JSON save, copy, open and pasted import. It is sandbox billing only, with no real charge. The public repository is MIT licensed.
Challenges and what I learned
Speech recognizers revise interim results and can stop at device-imposed session limits. I worked on transcript stitching, visible microphone state and a type/paste fallback. Notes stay editable because recognition and rule-based extraction can miss things. Building the board also meant handling selection, shapes, pan and zoom on a small screen. Testing the real phone mattered more than a desktop preview.
Demo and current limits
The video is recorded on an Android phone and shows live transcript capture, rule-based notes, board editing and drawing, plus the RevenueCat Test Store unlock. It does not demonstrate JSON save or open, so those paths are not claimed as verified in the video. The app is not published on Google Play or another store. There is no account-based history or cloud sync. Android device speech may use its vendor's online service; this is not a claim of fully offline recording. The repo has optional AI work, but this submission's recorded flow uses rule-based notes.
What comes next
Verify board-file save/open and restore on the physical phone, improve capture reliability and mobile board controls, then review production signing and billing before a store release.
Log in or sign up for Devpost to join the conversation.