May 262012
 

… and they really did not like it :) Here’s the link to the review.

All of what he says is valid, and is helpful feedback. In my defense, I could say that this was my first real attempt at a game, and I wasn’t trying to compete with Super Mario. But then again, why shouldn’t I be? Striving for excellence is a good thing. I will say this – I spent a lot of time towards the end of Neil Rajah, fighting my urge to just publish it and get it done with, while knowing that it really needed more polish, first impressions matter, etc. In the end, it’s far more polished and complete than any of my previous attempts, and I also know that there’s a lot of room for improvement in that area. Next time :)

May 232012
 

It looks like Amazon has rejected Neil Rajah yet again, this time because it uses a Swarm virtual goods store. I don’t have confirmation on this yet, but it looks pretty likely. They approved the latest update for general devices almost 2 weeks ago. Yesterday I submitted a support ticket, asking if it was still in the queue to be reviewed for the Kindle Fire, because I hadn’t received any email telling me if it was approved or rejected. The response I got basically said “Apps sold through Kindle Fire should use Amazon’s In-App Purchasing API.” I asked for clarification, but I’m guessing this means that they rejected it for the Fire, but neglected to tell me.

This isn’t a big deal for me to work around. I already have a Swarm-less version for the NOOK tablets, so that version should work for Amazon as well (with the ‘go to store’ link switched to the Amazon link). That will be a lot less work than writing a new storefront screen, and integrating their IAP API. So I’ll probably make that change and submit it to Amazon again.

But the more interesting thing here, for me at least, is how this is another aspect of fragmentation. Yes, it’s completely optional, because I’ve chosen to list the game on all these different stores. But look at the variety of IAP implementations and requirements out there:

  • Google Play – They have an IAP system, but usually don’t enforce it. Although there have been some reports of them threatening to pull apps that use something other than Google Checkout for IAP
  • NOOK – They don’t have their own IAP system, and they don’t allow 3rd party IAP systems. So basically, no free-to-play games on the NOOK tablets until they come up with their own IAP infrastructure (and it’s not clear that they’re planning to)
  • Amazon – Recently released an IAP SDK. From the accounts I’ve heard, it is pretty easy to use. They’ll apparently allow 3rd-party stores for their general devices, but not for the Kindle Fire. Which basically means that it’s not allowed – by my metrics, hardly anyone is using the Amazon app store any more other than Kindle Fire owners

The takeaway for me – on my next game, if I want to list on these stores, I should plan to implement my own store, and abstract out the backend so I can use multiple IAP implementations. And then I should ideally implement Google Checkout, Amazon, NOOK (if they have something by then), and a 3rd party solution like Swarm/TapJoy/etc. for all the rest of the stores.

May 182012
 

If you type that into Google, it looks like my blog is the first match returned. With Bing, it’s 3rd or 4th. This is mostly Google and Microsoft personalizing search results for me, but it’s still pretty funny. I am very far down on the list of indie Android game developers that matter. Maybe this is a sign that I should spend less time blogging and more time writing games :)

P.S. It does the same thing on my wife’s PC, as well as some of my friends. But again, since I’ve shared my site with them on Google+, Facebook, Twitter, etc., that’s still personalized search results.

May 132012
 

I had stumbled upon deidein’s blog while looking for reviews for a different game. His ‘About the Author’ page instantly struck a chord – he’s in his 30s, works in tech, husband, dad, likes Android. Pretty similar to me :) So I asked him if he’d like to review my game. Well, he did, and the first review didn’t turn out so well :) The game was crashing a lot, and that left a pretty poor impression on him, as it should. I had just started to realize that my crash reports were indicating a couple of high-frequency crashes, so I decided that I needed to do a good bug fix update. I also started up a conversation with deidein, getting his input on how the game could be better. I didn’t implement everything he suggested, but it was all good advice.

I uploaded a new version with the changes, and asked deidein to take another look. Here’s his updated review. I think he did a pretty good job of covering the essence of the game. And the issues that he points out are definitely valid ones, that I plan to address, time and budget permitting :)

May 112012
 

AppEggs.com was one of the Android app/game review sites that I had emailed with info on Neil Rajah. They recently contacted me and said that they liked the game, and were going to review it. As far as I can tell (mostly from just checking Alexa), AppEggs seems to be popular in China. So hopefully this will help expand my user base beyond India.

Here’s the link to the review. They even sent me a link to this nifty badge that I can use :)

This is the second such badge I’ve got, the first one was from Frugal Dads. I don’t think they mean anything at all – at the end of the day, it’s just some HTML code, and probably highlights the other site more than it does anything for me. Maybe I should make a separate page just to show off all my useless badges :)

 Posted by at 7:40 am
May 112012
 

Go watch this video and listen to their commentary, it’s quite funny :)

The Yogscast are a couple of guys who post videos and podcasts about games. They’re very popular – over 180k followers on Twitter, to give you an idea. I’m not sure how they stumbled upon the Neil Rajah trailer on YouTube, but I’m glad that they did :)