I-Play Launches Fast & Furious: Adrenaline on iPhone

Thu, Apr 29, 2010

iPhone, Mobile

Yesterday, I-Play announced the launch of Fast & Furious: Adrenaline for iPhone and iPod Touch. Adrenaline is actually the seventh installment in this mobile franchise, and it sees the franchise taking a step towards further social connectivity.

Adrenaline accomplishes this by allowing users to upload videos of their best races to both Facebook and YouTube. When connecting to Facebook, racers can also post their scores to the Facebook leaderboard to see how they stand up against worldwide competition. There’s also Wi-Fi and Bluetooth multiplayer functionality included in the game, allowing you to download ghost and race against them to improve your own times, as well as race against other players.

Apart from the social features, the gameplay itself contains 35 different cards fitting into multiple categories: Import Tuner, Muscle and Exotic. You’ll race through four different areas of Los Angeles (the Suburbs, Downtown, Beach Front and Industrial) in multiple game modes, including Road Race, Cop Chase, Time Trial and Drag Race.

As you progress, you’ll unlock new cars, garages and car modifications. Fast & Furious: Adrenaline is now available on iTunes for $2.99. Race over there to pick up your copy of the game. Fast & Furious Adrenaline

Be Sociable, Share!

Related posts:

  1. Play Big Win Soccer on Your iPhone, Not With Your iPhone
  2. Checker Kingdoms Launches on iPhone
  3. Be A Fast Plumber With PipeRush for iPhone: A Frisky Hands-On
  4. Tactile Entertainment Launches Pocket Creatures for iPhone
  5. Mo-Star Launches Princess Fury Update / Lite Version on iPhone
, , ,

This post was written by:

- who has written 2533 posts on Frisky Mongoose.

Brandy is the Social Editor at Frisky Mongoose, focusing on the social side of the gaming world.

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