Sonic the Hedgehog Comes to Atlas Controller

Wed, Jun 12, 2013

Android, Arcade, Console, Mobile

Sometimes, it takes an iconic console character and game to show just how perfect of a marriage there is to be had between Android games and the Green Throttle Atlas Controller — a console experience adapted to a mobile platform which then supports a console controller for a mobile console game! …I think! What’s happening here, in short, is that Green Throttle (a TriplePoint client) is teaming up with SEGA to bring Atlas support to Sonic 4 episodes I and II.

We’ve talked before about how some games simply play better when they’ve got the original interface that their designers had in mind, and while Sonic’s certainly made good on mobile so far, there’s really no better way to play his platformers than with a quality controller. From the press release:

The Android versions of Sonic 4: Episode I and Sonic 4: Episode II, available from Google Play and the Amazon Appstore, will be updated soon to include support for Green Throttle, giving fans a new way to enjoy their favorite spiky blue speedster.

Fans can purchase the Atlas controller from store.greenthrottle.com or on Amazon.com and enjoy mobile-to-TV multiplayer action using the Android device that they already own. Compatible devices include the Kindle Fire and many of the latest Android smartphones and tablets on the market today.

Look for us to look at Sonic 4 when it gets throttled up!

Be Sociable, Share!

Related posts:

  1. Throttling Up: Duke Nukem, The Bard’s Tale, and More
  2. Green Throttle Passing out the Green
  3. Sonic 4 Episode II Rolls and/or Flies Onto Console and/or PC Today and/or Tomorrow
  4. E3 2010: Sonic The Hedgehog 4: Episode 1 Hands-On
  5. Sonic is Completely PC Now
, , , , , , ,

This post was written by:

- who has written 16 posts on Frisky Mongoose.


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