Pocket's contact mic bypasses OS limits
This is Pocket’s clearest hardware edge because the device hears the call from the phone’s physical vibrations, not from software permission inside the phone. iPhone call recording is now built into iOS 18.1 in some regions, but it happens inside Apple’s own Phone app flow with consent prompts and saved recordings in Notes. Third party apps mostly get microphone access, not a reliable feed of both sides of a regular cellular call, so a contact mic creates a capture path software alone cannot match.
-
Pocket’s setup is simple in practice. The user snaps the device to the back of the phone, presses one button, and the contact mic picks up both speakers through the chassis without turning on speakerphone. That matters for private calls in public places where blasting audio out loud is awkward or impossible.
-
The market split is becoming clearer. Native OS tools and meeting apps are absorbing on screen conversations, while hardware survives in the leftover category of offline calls and in person conversations. That is why Pocket and Plaud both center dedicated devices, onboard storage, battery life, and physical microphones rather than just another recording app.
-
Android’s developer docs show how restricted call audio access is for normal apps, with call related permissions reserved for default phone or assistant handlers in many cases. Apple also keeps call recording inside its own first party experience with mandatory audio notices, which reinforces how little room third party software has to recreate the same workflow cleanly.
The category is heading toward a sharper divide. Software will own scheduled and on screen conversations because it is free and bundled, while hardware will win where capture has to happen beside the phone, not inside it. Pocket’s future depends on turning that narrow but real recording advantage into the default tool for calls, field work, and face to face conversations.