GDC: MOGA Pro Controller coming April 15

1:45 PM on 03.28.2013

Abel Girmay

Contributor

More precision for mobile play

Love it or hate it, the mobile gaming scene has grown considerably in even these past few years. With that comes more variety of games to play, but let's be honest, there's plenty of genres where a touch screen just wont cut it.

Among other companies, MOGA realizes this, and is aiming to cut itself a hearty piece of the pie with its MOGA Pocket and MOGA Pro controllers.

As the name would imply, the MOGA Pocket is designed for everyday portability. The design is entirely flat, with the joysticks placed in indentations, and the triggers similarly tucked away into the frame. The center clamp folds into the design as well and is expandable to fit most phones.

With a design based on the Fusion Tournament Controller, the MOGA Pro has the same rubber grips and tuned analog sticks of its big brother, as well as the retractable center clamp of the MOGA pocket. The clamp on the pro is more forgiving though, expandable to fit even the largest tablet phones.

I got to try the Pro controller out with Dead Trigger, a free-to-play shooter on Android. Honestly, it controls really damn well. The comfort of the pro is clearly superior to the pocket, whose analog sticks end up feeling more like nubs since they rest in indents. Since its size is on par with a standard console controller, this is not something you'll be lugging around on your morning commute.

Also, the MOGA app store will now be supporting Kindle Fire and Android in addition to presence on Google Play. This launch comes with some pretty big backers including, Sega and Rockstar, to supplement the support from smaller devs such as Gameloft and Skyview. No iOS support yet.

You can find the MOGA in stores on April 15, 2013.

Get comment replies by email.     settings



Unsavory comments? Please report harassment, spam, and hate speech to our comment moderators

Can't see comments? Anti-virus apps like Avast or some browser extensions can cause this. Easy fix: Add   [*].disqus.com   to your security software's whitelist.