Easy Voice Recorder Reviews and Gratitude

The Brighthand team wrote an excellent review of Easy Voice Recorder Pro over at Brighthand Smartphone News & Reviews. I am thankful to them for the great review, and I’m also thankful to all of our users who leave great feedback, help us out when there’s issues or bugs, and provide great suggestions and feedback.

We greatly appreciate the support, and let us know how we can continue to make your recording experience even better in the future!

Download links:

Easy Voice Recorder

Easy Voice Recorder Pro

Tags:

6 Responses to “Easy Voice Recorder Reviews and Gratitude”

  1. Kula December 4, 2012 at 11:43 am #

    Hi, I tried your app and find it very useful.

    Can you tel me how you test your app in different platforms or handsets to make it versatile. Thanks.

    • Kevin December 4, 2012 at 2:45 pm #

      Hi Kula,

      Glad it’s helping you out. 🙂 I have the Nexus S, Galaxy Nexus and Nexus 7, and I use all three devices to do my testing. This helps me test on various screen sizes, and provides a lot of coverage. It depends on the app you want to make; if you want to make a standard app that doesn’t interface much with the hardware, I think this will provide you with decent coverage. You’ll just need to use the emulator to round out your testing to make sure your app works on earlier versions of Android.

      If you interface with the hardware, things get more difficult. Android is a fragmented ecosystem, and there are a lot of buggy devices out there, and devices with strange quirks. For example, for a recording application, Android “guarantees” that 44100Hz and only 44100Hz will work. On some devices, this means that 22050Hz might work, but on other devices it might not work. On some of the devices where it doesn’t work, not only will it not work but trying to use 22050Hz will also crash the systems driver, forcing the user to reboot the phone. Making things worse, there are a few older phones out there that don’t support the “guaranteed” rate of 44100Hz.

      One thing you have to keep in mind with Android is that there are a LOT of people out there using old handsets. The new phones support all kinds of fancy stuff, but the reality of the matter is that more than half of the market is still using Gingerbread and earlier, and very few people are on Jellybean. If you want to target as many people as possible, it’s important to support these older versions of Android, at least until a particular old version reaches 5% or less. I don’t think you need to support 1.5 or 1.6, but 2.2 and above is definitely still important as of today.

      It’s also difficult to control for all of these variables, and users will also use the app in ways that you don’t expect or support, but they will still be surprised if it doesn’t work. For instance, phone call recording might work fine on one phone, and the user might be surprised when it no longer works when they switch to another phone. 😉 So some of your testing and feedback will necessarily have to come from your user base.

      So, to wrap up everything, I definitely recommend a combination of a few devices and emulators, and I highly recommend a non-Nexus device that is very popular, such as the Motorola Droid RAZR or Samsung Galaxy SII. If you can’t get a hold of such a device, get a friend who has one to help you out. 😉 You don’t necessarily want the “latest & greatest”; it’s better to have something representative of what the majority of your customers will actually have in their pockets.

      Let me know if you need any further clarification. 🙂

  2. Kula December 6, 2012 at 7:08 am #

    That was really a good lesson. It is good to learn from a successful app developer 🙂

    One more thing, did you use Jake Wharton’s viewpager library for your tabs in your recording app?

  3. Kula December 7, 2012 at 9:00 am #

    But there is a bug named Issue #240. How did u fix it? Your tabs works fine even on Collapsed Tab Navigation.

    • Kevin December 7, 2012 at 4:50 pm #

      Hmm, I actually have no idea about that one. I believe that Jake prefers not to fix bugs that are part of core Android, so I actually forked Action Bar Sherlock to add in a couple of my own patches:

      https://github.com/Digipom/ActionBarSherlock

      Not to criticize Jake in any way of course — he’s done the community a tremendous service in bringing ActionBarSherlock to us. This fork fixes the issue with the share action provider not working if there’s only one intent, which is also present in core Android.

Leave a Reply

*