(Confirmed) Honeycomb not coming to phones "Says Google"

[splmonster]

Google Android 3.0 Honeycomb won't come to smartphones

 

[Baconator]

I think everybody is seeing it all wrong. This is what he said: "The version of Honeycomb we've shown is optimized for tablet form factors," Kovacs added, via a followup email. "All of the UI changes are the future of Android. Yesterday's event focused on tablet form factors, which is where you'll first see Honeycomb."
He said "the version of Honeycomb" emphasis on version. Version could mean that there is another Honeycomb. Also he said "which is where you'll first see Honeycomb first." This could all mean that Honeycomb will come out possibly for mobile devices also. None of what I read on their actually led me to believe that Honeycomb will not come out for phones.

Also this was the company's spokesman and he could have been easily confused. Remember this: Exclusive interview: Google's Matias Duarte talks Honeycomb, tablets, and the future of Android -- Engadget
Engadget talked with Matias Duarte the person who was involved with Honeycomb. He was asked Honeycomb for phones and he said "yes."

 

[splmonster]

I think everybody is seeing it all wrong. This is what he said: "The version of Honeycomb we've shown is optimized for tablet form factors," Kovacs added, via a followup email. "All of the UI changes are the future of Android. Yesterday's event focused on tablet form factors, which is where you'll first see Honeycomb."
He said "the version of Honeycomb" emphasis on version. Version could mean that there is another Honeycomb. Also he said "which is where you'll first see Honeycomb first." This could all mean that Honeycomb will come out possibly for mobile devices also. None of what I read on their actually led me to believe that Honeycomb will not come out for phones.

Also this was the company's spokesman and he could have been easily confused. Remember this: Exclusive interview: Google's Matias Duarte talks Honeycomb, tablets, and the future of Android -- Engadget
Engadget talked with Matias Duarte the person who was involved with Honeycomb. He was asked Honeycomb for phones and he said "yes."

They have said features will arrive not "Honeycomb" itself. Read that article

 

[Chris Kerrigan]

Well, Honeycomb is a tablet specific OS. No doubt that some of it's features will be arriving on phones, but I hardly call this fragmentation. Google set out to create an OS specifically oriented at tablets, meanwhile integrating some of it's new features into future versions of Android for phones.

 

[Johnly]

Am I missing something? I always thought HC was a Tab OS. Did someone say it WAS coming to a phone near you? Like Chris says, we will see "aspects" of it.

 

[Chris Kerrigan]

Am I missing something? I always thought HC was a Tab OS. Did someone say it WAS coming to a phone near you? Like Chris says, we will see "aspects" of it.

I think what happened was a bit of confusion, even on the part of myself. Google at one point did say Honeycomb would be coming to Tablets, but I think they meant more along the lines of a phone-oriented version of many of the Honeycomb features (Ice Cream Sandwhich?).

 

[Johnly]

I think what happened was a bit of confusion, even on the part of myself. Google at one point did say Honeycomb would be coming to Tablets, but I think they meant more along the lines of a phone-oriented version of many of the Honeycomb features (Ice Cream Sandwhich?).

I don't follow, but I know it is a bit confusing as it is a first. From everything I have read, HC was, and has always been a tab OS? Confirmation is good though. Maybe I am confused

 

[splmonster]

Some people were saying "Honeycomb" will come out for phones. I was just putting that to rest. We will get some of its features but we will not get "Honeycomb".

 

[Chris Kerrigan]

It's a very good point, and I'm glad you made it because I think there does need to be a distinction made between the OS itself, and it's features being baked into future phone versions.

 

[sniffs]

Does any of this matter? We've been shown time and time again that the will of the people will out do a company.

I bet 100 bucks that we'll see the requirement stripped from Honeycomb and it'll be ported to phones by some devs.. It's only a matter of time before we get the Honeycomb ASOP and people hack it.

 

[Scottish]

Some people were saying "Honeycomb" will come out for phones. I was just putting that to rest. We will get some of its features but we will not get "Honeycomb".

And... why does this matter?

 

[uberspeed]

It's AOSP and the writer can't spell "fragments" correctly. oy

 

[Jalarm]

ummm....
Android 3.0 Honeycomb emulator has traces of smartphone support -- Engadget

 

[IRepTheKing]

I will be happy just to get an official Gingerbread release from Sprint.

 

[Kyle Gibb]

Just think about it... a 4-inch cell phone doesn't have the screen real estate to handle the new UI elements of HC. I would suspect that the phone version of Android will take some design and color hints for HC but won't change much. We will still have the notification bar at the top, app launcher at the bottom etc.

And I'm perfectly fine with that. I don't want the same UI on my 10 inch tablet and my 4-inch phone and my 15-inch laptop. Design the best UI you can for each form factor and go with it.

 

[SanGo]

ummm....
Android 3.0 Honeycomb emulator has traces of smartphone support -- Engadget

The international Galaxy Tab had phone call support, future tablets probably will too. Being that this has all been taken from an sdk "preview" its quite likely that things may change by the time the official source code is pushed.

 

[potatoho]

And I'm perfectly fine with that. I don't want the same UI on my 10 inch tablet and my 4-inch phone and my 15-inch laptop. Design the best UI you can for each form factor and go with it.

Ideally for me would be that the phone UI stays similar to what we see in Froyo and the tablet UI as i what we see with Honeycomb in the demos. Apps using fragments will designate a single pane and popup menus for the phone UI, and these same apps when running in tablet UI will have extra fragments which surround the normal pane. The fragment API backported to 2.x so you get a single app which runs on all devices with both form factors.

And my ideal phone would support two simultaneous screens. An internal phone UI screen, and an HDMI-out screen which runs the tablet UI. So you choose from the same pool of apps and they run smaller on the phone UI screen, and larger with more fragments on the tablet UI screen.

 

[lyk13]

If I want to take a garner at this, I would say Honeycomb IS a tablet-optimized OS. But that doesn't mean the OS couldn't branch out to a phone-specific version if deployed seperately for target models.

I believe Android OS moves together, and it be dumb for Google to leave out the smartphones in their next iteration.

Let's just patiently await. Or until our Nexus S-es suddenly receive an OTA to install Honeycomb. LOL.

 

[splmonster]

Does any of this matter? We've been shown time and time again that the will of the people will out do a company.

I bet 100 bucks that we'll see the requirement stripped from Honeycomb and it'll be ported to phones by some devs.. It's only a matter of time before we get the Honeycomb ASOP and people hack it.

"Honeycomb" was confirmed by Google to not have a spec requirement. That was old news...

 

[DPtheKid]

I was expecting only to get parts of it in the first place. This just would not work on a phone.