[android-developers] Re: Market expanding to technically non-compliant devices?

2010-12-01 Thread gjs
Hi, > It is a little premature to start freaking out about Google TV and making up > stories (OMG we'll need to maintain multiple .apks!) about how horrible > things are. Apologies, just getting ahead of ourselves in anticipation of being able to create app's than span and work together across th

Re: [android-developers] Re: Market expanding to technically non-compliant devices?

2010-12-01 Thread Jonas Petersson
I'll have to stand in Dianne's side in this case. As some of you may have noted a while back I took the time to ensure one of my apps was "Google TV ready" as in fully working without a touch screen. For everything except the map it took a whole of two lines of code per Activity and in the map

Re: [android-developers] Re: Market expanding to technically non-compliant devices?

2010-12-01 Thread Dianne Hackborn
I am sorry it is undocumented. But it is there, and you can use it starting with 2.0 and later. On Wed, Dec 1, 2010 at 4:51 PM, Mark Murphy wrote: > On Wed, Dec 1, 2010 at 7:40 PM, Dianne Hackborn > wrote: > > There are very few things forcing people to use separate .apks. Yes, > prior > > to

Re: [android-developers] Re: Market expanding to technically non-compliant devices?

2010-12-01 Thread Mark Murphy
On Wed, Dec 1, 2010 at 7:40 PM, Dianne Hackborn wrote: > There are very few things forcing people to use separate .apks.  Yes, prior > to 2.0, if an API was being made available as a shared library, you couldn't > use android:required="false" to allow your app to still be installed even if > it do

Re: [android-developers] Re: Market expanding to technically non-compliant devices?

2010-12-01 Thread Dianne Hackborn
On Wed, Dec 1, 2010 at 8:42 AM, dario wrote: > 'Standalone' apps don't have to go away. OHA should commit to openness > to make sure we don't have to fragment our apps. For example, using a > front facing camera shouldn't require separate apks (even Qik had to > do this). > What does "OHA should

Re: [android-developers] Re: Market expanding to technically non-compliant devices?

2010-12-01 Thread Dianne Hackborn
Um. People. Google TV does not have Market on it. This didn't happen by accident. The platform isn't yet ready to give apps and their users a good experience on such devices. You know, a deliberate decision to not cause unreasonable pain for developers. As has been the case at pretty much eve

[android-developers] Re: Market expanding to technically non-compliant devices?

2010-12-01 Thread Chris Stratton
On Nov 30, 9:12 pm, gjs wrote: > I am hoping to avoid the potential user confusion situation for an > integrated (tv and phone) app of having to release two separate > versions You can probably make a single apk that can do either the phone or tv half of the job. But why exactly would your appl

[android-developers] Re: Market expanding to technically non-compliant devices?

2010-12-01 Thread Bret Foreman
I can certainly imagine apps that have voice-only navigation as Android moves into the automotive, gaming, and sports markets. Imagine a pair of Android-powered, voice-controlled augmented reality goggles. -- You received this message because you are subscribed to the Google Groups "Android Devel

[android-developers] Re: Market expanding to technically non-compliant devices?

2010-12-01 Thread dario
'Standalone' apps don't have to go away. OHA should commit to openness to make sure we don't have to fragment our apps. For example, using a front facing camera shouldn't require separate apks (even Qik had to do this). Fortunately thanks to a tip from Diane, we can now use the undocumented requir

[android-developers] Re: Market expanding to technically non-compliant devices?

2010-11-30 Thread Spiral123
ah I see what you mean now. Interesting. The situation you are referring to is already upon us: GoogleTV it comes with its own controller that works well and I can also get a separate Logitech app that runs on my Phone that works as a remote controller, effectively replacing the GoogleTV controll

[android-developers] Re: Market expanding to technically non-compliant devices?

2010-11-30 Thread gjs
Hi, 'What' I mean is, *assuming* I can pack my integrated phone and tv app into a single apk, which needs touchscreen for the phone, would the app be excluded by the market for tv devices because they don't have touchscreens ? Yes until the tv sdk is released I won't know. I am hoping to avoid t

[android-developers] Re: Market expanding to technically non-compliant devices?

2010-11-30 Thread Spiral123
What do you mean what? Your phone touchscreen app will work fine with your touchscreen phone. with luck your app should then be able to find your GoogleTV device and get it to do stuff. How you talk to it and what stuff you can get it to do we will find out when we finally get to see the SDK.

[android-developers] Re: Market expanding to technically non-compliant devices?

2010-11-30 Thread gjs
Hi And when I use my phone touchscreen app to control my TV app hopefully from a single integrated apk then what ? Regards On Nov 30, 7:20 pm, blindfold wrote: > Yes, things are getting confusing if not messy. The Logitech TV Cam > accessory for the Logitech Revue Google TV adds a camera to Goo

[android-developers] Re: Market expanding to technically non-compliant devices?

2010-11-30 Thread blindfold
Yes, things are getting confusing if not messy. The Logitech TV Cam accessory for the Logitech Revue Google TV adds a camera to Google TV http://www.logitech.com/en-us/smartTV/accessories/devices/tv-cam but it can reportedly not be used by Android apps: "The TV Cam cannot be accessed from other app

[android-developers] Re: Market expanding to technically non-compliant devices?

2010-11-29 Thread Spiral123
GoogleTV. My Logitech Revue has no touch screen - assuming the market gets expanded to this device (yes please!) then I won't want to see any apps where I need to touch the screen. On Nov 30, 12:01 am, Peter Webb wrote: > Looking at the Developer's console, I note (correctly) that my > applicat