The main issue with OUYA is that all existing android apps will have to be reworked to support controller/remote input
I dont think the Touch pad on the controller is going to cut it. The creator of the Mupen64 emulator sent me this:
"While originally this was planned as a separate port, having looked at the ODK more closely I've discovered that it can be pipelined inside a single APK. So the Google Play version will in fact include the OUYA port (it is now technically an expansion of the project rather than a port).
That said, there are quite a unique requirements when developing for the OUYA compared to vanilla Android. The most immediate are the lack of a touch screen for menu interfaces such as button mapping (touchpad workaround being awkward and slow), lack of Home and Back buttons on the controllers (OUYA simulating Back with a non-standard keycode), lack of a standard Android action bar and menu overflow button, and serious graphics overscan to name the big ones). Had I not purchased a devkit and actually looked into optimizing the app for the OUYA at all, the Google Play version would certainly not have worked well on the OUYA because of these problems. The most serious concerns would have been no way to access the in-game menu options for things like save-state or load-state, extremely tedious mapping the controllers, and borders of the screen being cut off."