Yes. To install Google Play or Google apps, you absolutely are required to pass the CTS.
But, from your discussion, the CTS obviously doesn't test all parts of the Android platform: it's just a test suite. Kris On Wed, Jul 31, 2013 at 11:06 AM, Omer Gilad <[email protected]> wrote: > I just came upon this by accident > http://officialandroid.blogspot.co.il/2012/09/the-benefits-importance-of-compatibility.html > > This seems like the right approach, but my own experience is that the > Android reality is very far from this ideal. > > I've heard about the CTS. > The question is - are vendors actually forced to pass the CTS with their > customizations? > > On Friday, July 26, 2013 1:39:14 AM UTC+3, Omer Gilad wrote: >> >> .I am wondering how developers here are dealing with the fact that there >> are 1000's of devices out there, some of them running your applications in >> very broken ways >> .I keep running into these kind of issues again and again for the past 3 >> years, and to be honest, I'm fed up with it >> .I've decided to move to iOS development, and the only way to convince me >> otherwise is to give me a decent, reliable way of dealing with fragmentation >> >> So what do you do when you develop a game, for example, and try to create >> a high-quality user experience on Google Play? >> Do you do your QA on 50 different devices? 100? 1000? >> Or do you just shoot blindly and hope that it works, or wait for users to >> send you bug reports? >> >> To make it clear, I'm not talking about "official" fragmentation. >> I don't talk about different screen sizes, densities, features, OS >> versions and so on. >> I talk about the "unofficial" fragmentation. The fact that most devices, >> even the popular ones from the big companies like Samsung, HTC, Motorola, LG >> and so on, contain tons of implementation bugs that prevent apps from >> working correctly. >> I'm talking about the fact that you can call a certain simple API, test it >> on a stock Android ROM (like on Nexus 4), and then have your application >> crash on some Samsung, that decided to break the implementation because of >> some customization. >> >> How can people stand that? >> How is it possible to write code, when the machine that executes it is >> completely broken in unexpected ways? >> >> I'm really fed up with it. >> About 50% of my Android development time is wasted on babysitting broken >> devices. >> I'm waiting for an official Google response about this, and what have you >> been doing in all those years to fix that. >> I've heard about things like "conformance tests" for devices and so on, >> but the reality is far from acceptable in this area. >> >> ,Looking forward for helpful responses >> Omer > > -- > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Android Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
