‘Ripoff’ Apps are Harming iPhone Developers

Mon, May 10, 2010

iPhone, Mobile

I believe there’s a saying somewhere that reads something like: “Make something good enough, and someone will copy it.” Well, the same thing is happening on the iPhone App store in which popular apps are being copied as unoriginal developers try and make a quick buck on the backs of other developers.

The idea is in no way new and according to Mobile Marketing Watch, has existed since the beginning of the App Store but appears to be even more apparent these days. Lead developer of the blogging site Tumblr, Macro Arment wrote about his experience in trying to download an iPhone game called “Angry Birds” and its many copycats.

Searching for “Angry Bird” brings up two legitimate results for the popular game. The rest of the results however, are for other apps that have little or nothing to do with Angry Birds. What’s worse is that most of these spam apps cost money as well, as to do nothing but ripoff someone looking for Angry Birds.

With all of Apple’s restrictions on the App store, you would think that making the store more developer friendly would be a good idea. Here’s hoping that they enforce a solution soon.

Be Sociable, Share!

Related posts:

  1. Top Grossing iPhone and iPad Apps for Last Week
  2. Here’s Your Top Grossing iPad, iPhone Apps for Last Week
  3. Angry Birds Super Bowl Ad’s Got Game
  4. iPhone Apps Getting Cheaper
  5. Little Things (Free Code Giveaway!) & Angry Birds – iPhone & iPad Game News
,

This post was written by:

- who has written 807 posts on Frisky Mongoose.

Talor is a Contributing Editor at Frisky Mongoose focusing on the mobile side of the social gaming world.

Contact the author

  • http://www.facebook.com/cvbuskirk Chris Van Buskirk

    What Talor says is real. I released highly production apps which have cheap knock offs weeks later. It's appalling and pathetic.


Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0