Could be the “best” if...
I've been using this app and service for several years. The only part user
may need to pay for is when the calls are made from the app itself, when it needs to place a VIOP call to the destination number. This also means that the app needs data network in this mode and in the three-way call mode to trigger the second line call into user’s number, which would be joined with the incoming call to be recorded. Even with VIOP on the app’s side (in the first aforementioned case) the other end of the call is made via regular telephone network (in the U.S. and for the international calls), for which there is a cost and the app has to have balance deposited, from which the app subtracts for the cost of such outgoing calls which the user is recording. The rates for all destinations for such direct calls via the app are published in the app. Calls to the U.S. numbers are not free. The only way to avoid the costs in *this* app, is to use phone dialing apps offering better international rates and (!) the “calling card mode,” i.e., when the local number is actually dialed from your phone as a regular mobile call and then connected to whatever international destination. Such calls are never free, but the rates may be more competitive (note: I did not perform any rate or call quality comparisons for the international destinations between this and any other app, except for the U.S. numbers direct dial, so I am not commenting on the competitiveness of the international rates or call quality), but for the U.S. numbers, one can use Google Voice app, available on iOS but only available in the U.S.—not Google Hangouts, which uses VOIP at least on the user’s side, or bot. Google Voice makes calls via dialing a local number and DOES NOT charge for the U.S. calls, unlike *this* app for the outgoing U.S. calls. The only drawback with this approach is that the user would need to have this app call their number on the second line and have to three-way the call, in the same way as with all incoming call recording.
As far as the actual call recording functionality, the app does its job pretty good, even on the very long calls, however, for such a long calls, especially if the user is on the move, I would definitely recommend not using the app’s VOIP dialing since the stability of the call would directly depend on continuous and strong data connection.This dependency could be avoided — presumably the calls which one records are important and better not interrupted.
From this perspective of the call recording output, I would only have liked to have recordings in much higher quality.
The calls could be recorded with a higher sampling frequency and bit rate, to retain higher quality of the sound recording. Besides, this app doesn't offer long-term cloud storage of recordings — the recordings have to be soon downloaded to the user’s device for storage and further management and moving to a permanent storage like a cloud drive or computer, if desired. So there is arguably no reason for the app to worry about the file size, except for downloading it over the air to the user’s device. If you assume that this step would be done via Wi-Fi (and if there was an option in the app to enforce it) this should make the size of the MP3 file with the recording a non-issue. Users then can use any number of utility apps to condense the MP3 files to the size and quality of their liking on their devices afterwards.
At the very least, recording quality should be configurable.
(!!!) The main point of using an app like this is to be able to later discern the recorded conversation, including multi-participant meetings where speakerphones are used, which with the best recording quality could be a challenge. And this app records either via VOIP call or a three-way call, which already bring degradation of the sound quality (its not like this app supports LTE HD Voice...). So the quality of the sound recording should trump all other concerns and considerations.
As for the functionality of the managing recordings via the app’s Ui, the following are my strong suggestions to get this app on top of the competition:
1. Make the MP3 file name include all possible metadata about a recording. It could be added when the file is moved from the service back-end to the user’s device.
— If the call is made from the app, include the PHONE NUMBER which the recorded call was made to, otherwise use ”Incoming Call” as you do in the History Section of the app. But if the app accessed iPhone’s Call Log—i.e. ”Recent Calls”, which does have an API iOS—this app should be able to figure out what was the incoming number of the call based on the start of the recording and the timestamp of the calls in the call history of the phone.
And please display the phone number in the ”Recordings” tab in the app, with actual recording.
This would be the first most valuable productivity improvement the app can add, but the second one is close by:
—include in the file name the rest of the recording metadata, such as date, time, and length of the recording, all of which are available — it’s displayed with the recordings in the app’s UI, so this should not be a problem.
Please add to the app the ability to automatically copy MP3 files to the popular cloud services, such as iCloud Drive — only here it is meant as user-defined folder on iCloud, not the same as in #3 which refers to the internal app’s data. Although #4 can be used instead of #3, if all recordings metadata is embedded into the MP3 file name. Or Dropbox, Google Drive, One Drive. If you enable at least one if them, e.g., iCloud Drive (what's accessible via iOS native Files app), the ITTT app or the new iOS Shortcuts app, or many of the available workflow apps could be used to further customize management of the recording files. But this aforementioned minimum your app has to provide so that these tools can be used and to retain the recording metadata.
This a competitive field for many same apps