Some bugs you find by reading code. Some you only find by sitting there, actually using the thing, with a slightly baffled look on your face. Voice notes gave me a run of the second kind.
It started with a report that sounded alarming: recordings were silent. No sound at all. I sat down expecting to find something broken in the actual recording logic: a permission not granted properly, a file not writing, something structural. Instead the recording was completely fine. The audio was just quietly routing itself to the earpiece speaker (the tiny one at the top of the phone you'd normally hold up to your ear for a call) instead of the main speaker. Technically audible. Practically silent unless you happened to have the phone pressed right up against your head. One line fixed it: tell the audio session to default to the actual speaker.
That one was almost funny once I found it. The next one was more useful to have found at all. On Android, the record dialog had no way to actually hear a take back before sending it. You got a duration counter and that was it. No play button, nothing. Which meant the only way to know if a recording had actually worked was to send it and ask the other person, which is a terrible way to build confidence in a feature. Built proper playback into the dialog itself: you record, you can actually listen back, then decide whether to send it or try again. Should have been there from the start, honestly.
While I was in there rebuilding that dialog, I noticed the recording gesture itself didn't match between platforms. One was press-and-hold, the other was tap-to-start, tap-to-stop, and nobody had decided that on purpose, it had just drifted apart somewhere along the way. Worth catching, because little inconsistencies like that are the kind of thing a user notices even if they couldn't tell you exactly why something feels off switching between their phone and their partner's.
And then, right at the end of all that, a properly nasty one: a rare situation where tapping send twice, fast, could actually send the same voice note twice. Only reproducible if you were quick about it, and only really findable by deliberately trying to break it rather than using the app normally. Fixed by making sure the app locks itself the instant you tap send, rather than a moment later. Small difference in timing, real difference in outcome.
None of these were the kind of bugs you spot staring at a screen. They're the kind you only find by actually pressing record, over and over, on two phones sat next to each other on a desk, being annoyingly thorough about something most people would just ship.
