Archive

Posts Tagged ‘iphone’

A Story of Why Devs Should Think Twice about Developing for the iPhone

October 19th, 2009

2 Rejections and 42 Days of Waiting

Last week we received an e-mail from Apple’s App review team notifying us that after 14 days of review, our latest update to iCombat Lite would not be accepted because of “inappropriate keywords.” The offending keyword was “wii tank,” and we had chosen this because many of our users have told us that our game reminded them of the tank mini game that is part of Wii Play.

While we knew not to use current iPhone app names as keywords, it had never in a million years occurred to us that “wii” might be problematic.  In Apple’s words, they “cannot post applications that contain irrelevant keywords in their search criteria” and suggested that “it would be appropriate to remove ‘wii tank.’”  Interesting since they: 1) had already approved our iCombat paid version with the same keyword, 2) have approved an app with Wii in the title, and 3) they had already rejected iCombat Lite two weeks prior for some other reason without mentioning any problems with the keywords.

What is so frustrating about this latest round of trivial rejections is that the app review “feedback” seems to always come on day 14 (at the earliest), and happens serially.  To give you an idea, we first submitted iCombat Lite update 1.1 on September 8th, 41 days ago!  After being rejected for an issue Apple reported with the code on September 22nd, and spending several days working on replicating the bug (which we never even managed to), we resubmitted the exact same keywords and code on September 28th.

On October 12th (14 days later) we received notice that the entire update would need to be resubmitted because of the “wii tank” keyword.  Had anything changed from the approved iCombat Paid version or the previously rejected lite version?  Nothing at all…and so we deleted the words, resubmitted and for the third time started another 14 day approval cycle.  All in all, if we are lucky we expect the iCombat Lite update to be approved on October 26th, just 48 days to get to market (42 if we subtract the days we took to work on the first rejection).

Reasons to Avoid Developing for the iPhone

Ignoring how illogical this last keyword rejection has been, the real damage of the current app approval process is that it has created a slow and arbitrary development environment that does nothing but discourage indie developers.  The biggest issues with this setup are:

  1. Slower development cycles – As if figuring out what users wanted wasn’t hard enough, now add a 14 day approval delay which quickly turns into 1 month with any rejection and you have a buffer that really starts to isolate developers from their users and this constrains the feedback – iteration loop
  2. Product/ Market fit is replaced with Product/ Apple fit – To use Andreesen’s advice (worth a read), entrepreneurs should “do whatever is required to achieve product/ market fit.”  Here the only thing that matters is finding what users want and giving it to them.  Yet with Apple as the gatekeeper success is not determined by the market but first by whether Apple will LET you play in its garden. This perverts the goals of the developer and ultimately reduces the chances that an efficient product/ market fit can occur.  You could even argue that on the off chance that you find an exceptional product/ market fit you are at even a higher risk of being cannibalized or pulled or copied by Apple itself.
  3. Impossible ROI calculations – If you are trying to run a business based off of App development, how can you possibly calculate the return on your investment when you have no control over your launch to market? Unless you are ngmoco with funding from Kleiner Perkins then how can you build a business on top of such uncertainty (market and execution risks should be more than enough to contend with without having to worry about the d-bag app reviewer risk)
  4. App approval amnesia and the lack of a fast track system – What seems to be happening all too often is that previously approved apps, after waiting weeks in the queue, get rejected for features that had already been approved in past releases.  This approval amnesia combined with being lumped in with new app approvals creates a developer disincentive to work on refining applications.  Does it make sense when iCombat Lite, having been live for 3 months with 100k installs and no complaints, suffers a 40+ day delay because it is being forced to the back of the line over and over again to wait amongst what is new crapware?  The sooner these apps can get updates out the sooner they can deliver high quality experiences to Apple users.

All of these factors serve to undermine developer confidence, reduce the quality of apps in the store, and ultimately choke app development activity.  Developers are already looking to other platforms and are limiting investment as the environment has simply become too unpredictable to work with.  Sure Apple has its reasons, namely pushing its 85k or 100k or 250k apps commercials to prove it has the most evolved app ecosystem versus its peers.  But if Apple doesn’t fix these problems soon, those numbers will begin to mean less and less, and at some point the number of apps in the App store will be about as meaningful as the number of videos uploaded to YouTube.

Reblog this post [with Zemanta]

Marketing Your App is More Important than You Think

April 6th, 2009

I came across an interesting post on “How to use Twitter, Facebook and YouTube to market your mobile games” and it reinforced what I have noticed since readying to launch iCombat – there are too many channels to manage when it comes to reaching the end user!  This may sound like a high class problem to all of the game and content developers that have faced the gatekeepers of distribution over the years but the sudden blossoming of dozens of channels to reach users has created its own set of problems.  Now the burden of brand management and marketing has fallen into the lap of the developers, where they must become “marketers” of their product if they hope to get noticed.

The rise of the fractured, multichannel market has created dozens of sites that developers now need to visit to build goodwill and help gain exposure, something that is fundamentally different from what they probably want to be doing. In my case this translates into 18-20 hours a day since launch to manage the marketing effort and frankly it is still more than I can handle. While I have enlisted friends and an intern to help, most developers don’t have the luxury of dedicating all of their own time to managing their launch.

I have compiled a list of some of the tools and sites I think necessary to use today:

Top Down channels – kissing the ring

  1. Bloggers – what some refer to as the “digital influencers” – sites with major traffic like Gizmodo, Techcrunch, GigaOM
  2. Targeted review sites – Touch Arcade, 148Apps, Pocket Gamer, etc. – I have counted 60+ serious ones in all

Bottom Up channels – connecting with your users

  1. Facebook – both personal status and group page
  2. Twitter
  3. MySpace
  4. App/ Development/ Gaming Forums - Touch Arcade, maybe iPhonedevSDK, etc.
  5. Product website & blog – here you need to have a demo, maybe a news section and your blog
  6. YouTube – a great way to communicate with avid gamers
  7. iTunes App store summary

Analytics Tools – monitoring usage, downloads, buzz

  1. User downloads – iTunes Connect – Heartbeat App or AppViz (super easy to use but less flexible than Heartbeat)
  2. Usage behavior – Pinch Media – gives you uniques, geo data, version & device stats, as well as unique data by action in your App (very cool)
  3. App ranking – AppRanking by Michael Dorn or Mobclix
  4. Web traffic - Google Analytics or Wordpress Stats
  5. Affiliate data – Linkshare – here if you are an Apple affiliate you can earn back 5% of your 30% cut that goes to Apple – and monitor clickthrough conversion data from your site
  6. Brand management – ScoutLabs or Google Alerts – Scout doesn’t really seem to work for small apps or early on in a campaign as it is, for these smaller apps Google Alerts is a great basic filter

While this list is not comprehensive this is basically everything I am using for the marketing of iCombat. I didn’t realize just how many channels and tools this involved until trying to post an urgent piece of news.  When iCombat was reviewed in Gizmodo’s weekly roundup of iPhone apps I quickly wanted to update every channel I was using. Read more…

iCombat is Launched! (Also, Why We Chose To Do Another Tank Game)

April 1st, 2009

After 8 days waiting to be approved by Apple, iCombat is accepted and “Ready for Sale.”  I was pretty patient during the wait but by today I was starting to get worried.  I shot off a few e-mails to Apple, posted my scenario to a couple of websites and waited, and late this evening I found out that we were approved.  When I spoke to the team they thought it was an April Fool’s joke, which thankfully it wasn’t because we are now in the App store.  You can check out our description and buy it in the iTunes store here.Large icon

While I have been vague about what iCombat would be until now, I wanted to give you some background as to why we chose to do a classic arcade style tank game.  I grew up in the mid 80’s playing a beat up Atari 2600 – it was behind the times even then (let alone now!) but the good side of having the outdated console was that I could buy old Atari games at used book stores for under a dollar. I didn’t have the money, or need, back then to buy a newer console and it didn’t matter because the Atari had some of the best game play design of any console I have ever played.  Simple rules, easy to use controls, a fast learning curve, all of these things helped make it much easier than picking up today’s games (except maybe the Wii).

The game that captured my attention most was Combat, a 27 game in one combo pack that included the Tank game.  There were many variations of play, one of which was Tank pong – here you fired missiles (squares) at the other tank (a rectangle) and they could bounce off of walls and hit the enemy.  For me the bouncing missiles and fierce 2 player versus mode hooked me, and so when the iPhone launched we saw the opportunity to bring a similar type of game play to the younger generation of gamers.  The idea was to stick to simple game logic but utilize the powerful features of the iPhone to create something great.  Truthfully, we just created it also because we wanted to play it – and we tried to stay true to the game play fundamentals that made the original games so addictive.  And while there are half a dozen tank style games in the App store, we hadn’t found one that scratched our itch for this classic arcade style play.

We hope, after playing, you will start to share our enthusiasm for tank games and that you will become a fan of iCombat.  We also want to make iCombat better in future updates, so please send us your feedback at icombatgame@gmail.com or post something here.  We are planning to offer prizes of some sort (maybe t-shirts or something) to anyone whose idea is implemented in future updates so send us your best suggestions for future changes such as new weapons, levels, enemies, etc.  If your idea is good and others support it in the comments we will do our best to make it happen.  I will be posting some ideas of my own in the coming days so don’t be shy to shoot them down if you think they are weak!

Reblog this post [with Zemanta]

The iPhone App Market: A Bigger Opportunity than Many Think

March 7th, 2009

There has been quite a bit of negative press about the App store in recent weeks where fears are being stoked about downward pricing pressure and poor user engagement rates after download.  I think all of this negative press is missing the point and serves as little more than fodder for bloggers and journalist eager to write anything other than the old news of App store success.  While the data in terms of averages may point to weak trends, this is because most pundits do not back out the effect of the gimmicky and one off free apps on the App store.  The reality is that in the Games market and especially in the niche application space (like productivity or medical) applications are selling well for over $5 and some for as much as $100.  I came across an e-mail to investors by the CEO of Tapulous Bart Decrem (posted in Techcrunch in January of this year) that summarizes why the opportunity is still so great.  While dated slightly in terms of the stats, the answer is that it is not all about the App store but also about riding the incredible growth in iPhones and the iPod Touch: Read more…

A Few Things to Consider Before Developing Your App

February 24th, 2009

See below a great resource made by Photokast where they recount their experience developing an iPhone application in 30 days.  While the time constraint they chose to work under is impressive, I found their 15 tips for development extremely useful. In their words, “this document is a combination of what [they] have learned over the last four years in mobile development, and how that was applied to the making of PhotoKast. It is not a How-To guide on coding; it addresses the other parts of development, with an emphasis on design and planning.” While I am too far along to use every suggestion on their list, it is still super useful in helping you think about the big picture behind your app idea:

Building PhotoKast: Creating an iPhone app in one month

Reblog this post [with Zemanta]

Finding the Right iPhone Developer: A Developer’s Perspective

February 23rd, 2009

Below is some advice from Taras Filatov, the lead of the team I am currently working with in the Ukraine.  His advice is great if you are thinking about developing an application and are currently looking for developers (either locally or abroad):

1.  “I need a simple iPhone app done…”

A lot of iPhone job posts at Odesk, Elance, RentACoder start like this.  This is somewhat similar to the typical “I need a simple shopping cart solution” post we often see in the web development section.  It might be interesting for you to know that when your ad starts like this there is a very high chance that it will be disregarded by developers or their sales teams that check the website.  This is because developers in most cases find the requirements for something stated to be simple as oftentimes being actually very complex software: with bells and whistles, using GPS location, chat, camera, social networking functionality and a website to support the server functionality.  All of this is just assumed to appear out of the blue built by the same developer.

Typically, there are no specification documents and the job poster has a general, unfinished idea of  what he/ she thinks is a “killer app” and they want the developer to do the rest of thinking. It is also common in such cases that the author did little or no research into what is possible with iPhone SDK and after a discussion it may well turn out that implementing such functionality is impossible at all (except for jailbroken devices) so it turns out to have been a waste of time to even sign all the confidential agreements and begin discussion at the end of the day. Read more…