OpenFeint Signs Up Four Developers For Virtual Goods Platform

Sun, Jul 4, 2010

iPad, iPhone, Mobile

OpenFeint, along with ngmoco’s Plus+ service, are the two leading achievement, leaderboard and matchmaking providers on the iPhone. Now, Aurora Feint (the developers behind OpenFeint) have partnered with four studios–Halfbrick Studios, PikPok, Retro Dreamer, and Hypercube–to test out a virtual goods platform on the iPhone and iPad.

“With few good quality virtual goods-based social games available for smart phones, the market already exceeds $168 MM,” said Aurora Feint CEO Jason Citron, as reported by Gamasutra. “We think that this is a tremendous revenue opportunity for game developers.”

He adds: “OpenFeint X offers game developers the opportunity to enter this market quickly without having to build the internal server expertise required to support scalable social games.”

This new platform should open the doors for some new types of games to come onto the iPad and iPhone platforms. With an easy way to integrate virtual goods into their games, developers might be more willing to test out titles that can take advantage of OpenFeint X, and that’s a good thing for both end-users and the developers behind the games that use OpenFeint.

OpenFeint currently services 28 million users and has its achievements, leaderboards and social elements in 2,200 games.

Be Sociable, Share!

Related posts:

  1. iPhone Developers Cautiously Optimistic About iPad
  2. OpenFeint “Delighted” with Apple’s Game Center
  3. Free OpenFeint Standalone App Now Available
  4. Social Gold Drives Repeat Purchases of Virtual Goods
  5. The Latest Cross-Platform Gaming Company: SiXiTS
, ,

This post was written by:

- who has written 186 posts on Frisky Mongoose.

Art is a Weekend Editor at Frisky Mongoose focusing on video games and the social media that surrounds them.

Contact the author


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