riddlemethis Surely since the recording feature is already implemented, a switch for automatic shouldn't be too cumbersome.
It might be instructive to code it up and report back how much code a baseline implementation is. But that's only the tip of the iceberg.
Recently there was a post about a situation where a user had inadvertently filled up device storage by accidentally leaving video recording on overnight. Luckily, restoring the device to usability was possible without a factory reset, but the situation was still a bit of a sticky wicket.
So automatic call recording, to be safely deployed to the masses, arguably needs a bunch of code to suspend its own operation if storage space is getting low. How low? Once that point is reached, how should the user be alerted? Should the user be alerted before automatic call recording is disabled? What if the user disabled notifications for the dialer app? How about folder structure? If a user is likely to collect thousands of recordings, should they all be dumped in one folder, or should they be split by year and month?
It would arguably be prudent to have some sort of carrier testing plan. The initial roll-out of call recording was complicated because the "record" button was off the bottom of the screen for some users whose carriers supported some optional in-call features that, apparently, the developers didn't encounter in their testing.
What looks like one simple toggle on the screen might have a lot of code behind it, and also a lot of testing work.