24. February 2015 · Comments Off on ASO Starts With Very Simple Research · Categories: ASO · Tags: , , , , ,

Finding the best keywords for your app is the basis for good App Store Optimization (also known as “ASO”).

However, before you start digging through online app research services such as Sensor Tower, App Annie and others, there are some better avenues you can utilize to do some basic keyword research.

Let’s say, for example, that we have a game app about sailboat racing. So, without relying on Internet keyword searches, come up with an “off-the-top-of-your-head” list of keywords. In less than a minute, I came up with the following quick list:

  • Sail
  • Boat
  • Race
  • Water
  • Ocean
  • Sea
  • Motor
  • Wave
  • Mast
  • Bow
  • Stern
  • Aft

Now, we’re ready for some more help in expanding our list with simple internet searches.

Since I’m looking for terms, I did a simple Google search for “sailing terms” and found the following additions:

  • Nautical
  • Port
  • Docking
  • Anchor
  • Starboard
  • Gooseneck
  • Hull
  • Cabin
  • Keel
  • Rig
  • Rigging
  • Yacht
  • America
  • Cup

I noticed that during my simple research that my terms were getting too technical, so terms like “gooseneck” might not work. I kept the term “cabin” for now, but I might later find out that more users are searching “cabin” to find “cabin rentals” or “cabin vacations” and not for “sailboat cabins.”

I could easily make the above list longer, but I think I have a good, simple start on “sailboat” terms, but I need more “racing” and “water” keywords, including:

  • Sea
  • Lake
  • Coast
  • Crest
  • Marine
  • Tide
  • Current
  • Fast
  • Speed
  • Regatta
  • Course
  • Series

In search for “racing” terms that apply to our sailboat racing app, we found tons of keyword opportunities for auto racing and motorsport racing. However, we continued to dig and started looking for particular “sailboat racing” events to find some more terms including:

  • World
  • Tactics
  • Cup
  • Key West
  • Recreation
  • Vessel
  • Offshore
  • Inshore

That’s a good start!

Next week, we’ll take a few of our starter keywords and dig a little deeper using some online app keyword research tools.

 

06. February 2015 · Comments Off on Spy Girl and the Man with the Unloaded Gun · Categories: Apple, Mountain Woods Media · Tags: , , ,

As app developers, we face different challenges every day when it comes to getting our games approved by iTunes Connect.Screenshot showing man with gun

The iTunes Connect reviewer (sometimes we love ’em and sometimes we don’t) follows a set of guidelines and, when we “break” the rules, our game will be rejected. We get over it; fix the problem and resubmit our app for another review. This process takes up to 10 days – or longer – to be reviewed. If you are rejected, then the review process starts all over again.

We can create a new game in less than a week, but then we’ll have to wait another week or so in order to see if the reviewer will approve our game. Obviously, this can be a stressful process, especially if you are running against a tight deadline and plan on submitting a holiday game 10 days before Christmas, etc.

Recently, we had a rough time getting a free game through the approval process as one of our screen captures (an action picture of the game) contained a character holding a gun. He wasn’t shooting the gun; he was just holding it. We’ve added the rejected screenshot to this blog post for your review.

Spy Girl Unstoppable Femal Secret Agent Espionage PlotNote: Our game “Spy Girl: Unstoppable Female Secret Agent Espionage Plot” is available starting today on the iTunes App Store. You can download it here: http://bit.ly/MWMspygirl

At first, we increased the recommended age settings for the game (due to the gun), but that didn’t work and we received another rejection. The player’s age had nothing to do with the rejection. Instead, it had to do with the screen shot of the villain holding a gun.

So, we deleted the screen shot – and we had to delete the screen shot in all 28 languages and stores that we had submitted the app.

Problem solved. Lesson learned.