3 ms·
Certainly, and the reasons those standards were put in place were good ones. There where devices with less than usable touchscreens (including resistive) and in
by tmzt 13y ago
Certainly, and the reasons those standards were put in place were good ones. There where devices with less than usable touchscreens (including resistive) and in some cases no touchscreens. These are the myriad of devices from Shenzen, one after another, running Android derived from AOSP.
At the same time, these devices were only one of the problems. Google was fighting against companies putting the Market on devices that could barely run Android, couldn't run 3D games that were available in the market, didn't support playback of video formats that were commonly used in the games and other applications, and had other limitations.
The availability of the devices contributed to Android's popular image as a low-end platform, with Apple's iPhone being the premium device. Remember, this was during the Android 1.0 and early 2.0 days.
At the same time, it was clear that Android needed to support multiple platforms. I asked one of the developers in IRC at the time when we would see a "set-back box" running Android, or systems for vehicles. The response was along the lines of "let's concentrate on phones first."
Now we are seeing a perfectly reasonable restriction in the Market (now Play Store) license being used to exclude a new product category from the officially supported application store where Google collects a healthy cut.
Also, doesn't the Ouya controller have a touchscreen, and even run Android on it's own internal CPU/GPU? It's not clear to me from the Kickstarter description but it would make sense.
The trade-off here for Ouya is either collecting the share of the revenues for themselves, including possibly through their own free-to-play credits system, or having a large number of partially supported games which were not designed to use a controller. I can see that whether it was the original plan or not, having their own application store makes sense for Ouya if they can get the developer attention they need.
That's really what I'm talking about here, Google's careless implications of creating a competing console may have the effect of confusing potential buyers at Target or GameStop as to which Android console to buy. The result being they buy neither.
- baggachipz 13y agoAll very good points. The Ouya is indeed an Android console, through and through. It doesn't take much digging into the settings area to see stock Jelly Bean UI. Like, right down to the "shutting down" popup/animation. It does have a touch pad on the controller, but I've never once seen a reason to use it (yet). A "nice to have", though. Despite the recent negative buzz, I've been pretty happy with my Ouya so far. It's a $99 console, people. Some of the games have hinted as some real innovative gameplay and it can emulate any classic game console you can imagine. Next up is getting XBMC running on there, it's supposedly pretty far along. It does suffer from typical Android issues, the most notable being the tendency to slow way down for a second or so, then speedily "catch up" to input that was deferred. If you've scrolled an Android phone, you've probably seen that behavior. It's annoying in gaming. I hope they can fix this.
- Pxtl 13y agoThe Ouya has a touch pad, but not a touchscreen. The touch pad is intended as a fallback pointing device, not a primary input. But yeah, Android is appearing on a myriad of devices, many being simple "mini-PC" screenless gizmos with the Play Store illegally hacked on. There's a huge market for low-cost hackable set-top devices and Android is the cheapest popular OS for this, so it only makes sense for Google to start supporting this market and get in on the action. Actually, this is one space where Microsoft's Windows 8 RT has a tremendous advantage. WinRT's store requires that every application support keyboard/mouse controls. This means that a potential WinRT set-top box could include a presenter-style controller and access the official Win8RT thing without the kind of growing pains Google will see as they deal with expanding their OS into new form-factors. Of course, MS won't bother with a Win8RT set-top box because they've already got the XBox1 coming, and they don't want to cannibalize their own market like that.