Get In Touch
This form does not yet contain any fields.

    Entries in Traceroute Pro (2)

    Thursday
    Dec092010

    Don't write down feature requests!

    While reading the great book from 37 Signals Rework I came across an interesting suggestion, "Don't write down feature requests." This seemed to go against my natural instincts to write down all suggestions, because if some wants it, I should put it in right?

    Well as Traceroute Pro went out to the public and I started hearing back from users, I didn't listen to the suggestion and started writing down all the feature requests. "I think there should be a dancing unicorn in the background to entertain me while I wait for the results." Err ok...

    So needless to say after getting a few crazy requests, Jason's words started to resonate with me.

    What I've found is that the best way to approach it is to just read all requests, and then throw them away. If they are good ideas and valid suggestions, you will hear them a few times and they will stick.

    I used this approach with the latest update for Traceroute Pro. No it doesn't have that dancing unicorn, but it does have the ability to save sites to your favorites and maintains a full history of your past tests.  These are two of the most requested features that I heard from my users and after I implemented them, I couldnt imagine having created the application without them.

    Monday
    Nov082010

    iPhone Niche App: Ad Supported or Premium Download?

    It was my day off and I was traveling to a wedding with my wife out of state when I received an emergency page from work, customers were reporting that they were unable to access our web sites. Without my laptop, I only had my iPhone available to do some tests. The reports indicated that it was only limited to customers on the west coast, but that everyone else could access the sites fine. Immediately I started doing some google searches for looking glass sites on the west coast. This yielded nothing but broken links and sites that did not work well on the iPhone.

    My frustration with this experience gave me the motivation to produce a mobile looking glass application, that would make my life much easier. I spent the next few weeks aggregating ISP’s looking glass devices, writing code, and eventually came out with an app that I was happy with. I really wanted this application to be widely available so that no one would have to deal with the same frustration as I did, but I also wanted to be able to cover my costs. I thought that the best way to handle this would be a free application, supported by ads.

    Apple approved “Traceroute” (LookingGlass was taken) on October 1st and with excitement I watched as the downloads accumulated each day. Traceroute was being downloaded across the world, and by November 1st it was being used in 57 different countries. Yet each day when I checked in on my iAd performance, it was disappointing. The number of impressions to the number of requests was abysmal. Traceroute has a very diverse international user base approximately 60% of the users are outside the US, and as of writing this iAd support is just starting to trickle out internationally. Each day hundreds of people were using Traceroute but I was only getting credit for a small population of these users. On one hand I was happy because I had produced a useful niche application, but on the other hand I was hoping to be able to at least be able to cover my apple licensing costs.

    Come late October and only having generated enough revenue to purchase a few Americanos, I decided to start thinking about other ways to monetize the application. I never liked it when developers put out free but crippled versions of an application to push people to convert to a paid application. Although if you could get the same functionality in the free version as a paid version who would choose the paid version? I shrugged my shoulders and with nothing to lose thought I would give it a try.

    I got to work and stripped out all of the code for Ad support in Traceroute and published Traceroute Pro, to the app store.

    Results:

    Apple approved Traceroute Pro on November 2nd, and in the one week since that approval Traceroute Pro has generated very low double digit downloads. Although comparing the revenue of Traceroute Pro vs. Traceroute, the 99c downloads have yielded more revenue in a week with very low volumes than the Ad views on the thousand plus applications of Traceroute that are in use.

    Given the revenue numbers in just one week it would seem that it would be better to release future applications as a paid applications instead of the ad supported model, although I think that there are some variables to watch before I come to that conclusion.

    • Its difficult to tell if the paid downloads are current Traceroute users who upconverted to Traceroute Pro to avoid ads, or are these new users?
    • If I integrate a secondary Ad platform to fill in when iAds fails to generate an Ad will that have any impact on revenue?
    • As Apple roles out iAd international support will the fill rate increase significantly to impact revenue?

    I plan to explore using Admob to step in when the iAd requests fail. I’ll follow up with a new blog entry for if this works and how well it performs in comparison to iAds.

    I’ll keep an eye out on these variables and report back as things progress but at this point the best recommendation I could produce for utility application developers is to utilize both application types and see what works for your audience.