I think this article shows how completely out of touch some Apple blogs and fans are. (Note: Am typing this on a 13" MBA and have an iPad mini and iPhone - and two Android phones - next to me, so am impartial). For starters, there is nothing at all new or innovative about any of the above. Since a few years ago, I have been able to dock even my most basic Android phone in my car (at the time, a Motorola DEFY running a very old version of Android) and do the following:
1. Issue spoken commands to do pretty much all I can do today with Siri.
2. Navigate to must about anywhere on Earth, with Google's excellent satnav killing Google Maps/Turn by turn directions
3. Obtain location info, such as nearest ATM, gas station etc.
Further, the navigation interface is not from above, but is down at street level like a regular satnav, so it's easy comprehend. Looking at maps from above is confusing because you lose your orientation, but that's another discussion. (I'm aware that Apple maps can do street level views now, but it couldn't even last year.)
I hate to say it, but Apple are years behind. Google Now today can do a huge amount, and lot of it will work in any car, simply by mounting your device above the dash.
I still think Apple made a huge error giving Google maps the boot - they have a lot of catching up to do, in particular in the place naming accuracy and Street View department.
You do realize that Google Maps and Now are Google's key leading features for Android, right?
The problem is that's all Google has, and Apple has largely caught up within a year. At the same time, Apple's iOS has some things Android doesn't have. And you know what those things are. So it's a wonder why you feel the need to do a superiority dance for a hobbyist platform with no good app exclusives, no advanced development tools like Core Data, no security, no enterprise support, no real integration, and so on. If you like Android, enjoy it. The world is not confused. Nobody has ever needed some comment troll to educate them about how their personally favorite product is so wonderful everyone else is stupid for not talking about it rather than the topic being discussed.
iOS in the Car is not Apple hardware in the car. It is getting iOS from your iPhone onto the car's existing screen. That's why the Home button is there: it's to use the screen's built-in features when an iPhone isn't connected.
AI is totally wrong about this.
The very first paragraph at apple.com about iOS in the Car even says so:
"OS in the Car seamlessly integrates your iOS device — and the iOS experience — with your in-dash system. If your vehicle is equipped with iOS in the Car, you can connect your iPhone 5 and interact with it using the car’s built-in display and controls or Siri Eyes Free."
The in-dash system is NOT running iOS.
Previous articles have described various ways iOS in the Car could be implemented (AirPlay wireless/cable integration, iOS appearance hosted by third party hardware, Apple hardware), with the pros and cons of each. None of them are an AI prediction, so there's nothing to be "totally wrong" about. The program is an expansion of Eyes Free, so there's no revelation in what you are saying, and that's been widely mentioned as a possibility, including within AI's coverage.
I think this article shows how completely out of touch some Apple blogs and fans are. (Note: Am typing this on a 13" MBA and have an iPad mini and iPhone - and two Android phones - next to me, so am impartial). For starters, there is nothing at all new or innovative about any of the above. Since a few years ago, I have been able to dock even my most basic Android phone in my car (at the time, a Motorola DEFY running a very old version of Android) and do the following:
1. Issue spoken commands to do pretty much all I can do today with Siri.
2. Navigate to must about anywhere on Earth, with Google's excellent satnav killing Google Maps/Turn by turn directions
3. Obtain location info, such as nearest ATM, gas station etc.
Further, the navigation interface is not from above, but is down at street level like a regular satnav, so it's easy comprehend. Looking at maps from above is confusing because you lose your orientation, but that's another discussion. (I'm aware that Apple maps can do street level views now, but it couldn't even last year.)
I hate to say it, but Apple are years behind. Google Now today can do a huge amount, and lot of it will work in any car, simply by mounting your device above the dash.
I still think Apple made a huge error giving Google maps the boot - they have a lot of catching up to do, in particular in the place naming accuracy and Street View department.
well sure, you can dock you iPhone or droid phone on a dashboard mount now and do all that stuff. so?
currently, Apple's EyesFree also transmits and displays basic iPod-like info to your car's display screen too, as noted by bzzlink above. i suppose there is some droid equivalent ...
but just passively mirroring your smartphone's screen onto your car display like AirPlay - which is certainly possible now, i suppose there is even some droid equivalent - would not be very useful, and actually distracting. their display UI's are obviously not designed for that situation at all.
integrating the full capabilities of the Siri/Google Now voice OS UI into a comprehensive "virtual" car system is quite straightforward in concept, yes, because the bluetooth setups are there now. but an entirely new touchscreen UI layout specifically designed for a dashboard display - including also such specialized screen layout for every app it might run (starting with vehicle info apps from car makers and services apps like Sirius) - is what is needed that no one has done yet for iOS or droid.
so iOSC is basically reformatting a very simplified iPad touchscreen UI for this unique situation. no doubt some droid version will appear next year too ... even tho according to you, that should already exist now if Apple is "years behind."
but don't let rationale analysis get in the way of a good rant.
I think this article shows how completely out of touch some Apple blogs and fans are. (Note: Am typing this on a 13" MBA and have an iPad mini and iPhone - and two Android phones - next to me, so am impartial). For starters, there is nothing at all new or innovative about any of the above. Since a few years ago, I have been able to dock even my most basic Android phone in my car (at the time, a Motorola DEFY running a very old version of Android) and do the following:
1. Issue spoken commands to do pretty much all I can do today with Siri.
2. Navigate to must about anywhere on Earth, with Google's excellent satnav killing Google Maps/Turn by turn directions
3. Obtain location info, such as nearest ATM, gas station etc.
Further, the navigation interface is not from above, but is down at street level like a regular satnav, so it's easy comprehend. Looking at maps from above is confusing because you lose your orientation, but that's another discussion. (I'm aware that Apple maps can do street level views now, but it couldn't even last year.)
I hate to say it, but Apple are years behind. Google Now today can do a huge amount, and lot of it will work in any car, simply by mounting your device above the dash.
I still think Apple made a huge error giving Google maps the boot - they have a lot of catching up to do, in particular in the place naming accuracy and Street View department.
You are forgetting Google was trying to hold out features from iOS that were readily available on their pOS. Apple absolutely did the right thing by booting them and going solo.
I think this article shows how completely out of touch some Apple blogs and fans are. (Note: Am typing this on a 13" MBA and have an iPad mini and ..... ..... blah blah
[quote name="Oflife" url="/t/158949/exclusive-hidden-contacts-revealed-within-apples-ios-in-the-car#post_2376423"](Note: Am typing this on a 13" MBA and have an iPad mini and iPhone - and two Android phones - next to me, so am impartial).[/QUOTE]
No one gives a frick. If you can't make your argument without this, you can't make your argument. You're hardly impartial.
[QUOTE]For starters, there is nothing at all new or innovative about any of the above.[/QUOTE]
Which you know, because not only have you seen this device in person, you've used it to the fullness of its capabilities.
Come on, man.
[QUOTE]I hate to say it, but Apple are years behind.[/QUOTE]
I hate to say it, but they're not even in vehicles, so no, they're not. They've neither won nor lost. They're [I]watching[/I] the game be played. :no:
You are forgetting Google was trying to hold out features from iOS that were readily available on their pOS. Apple absolutely did the right thing by booting them and going solo.
How could Google how back features on a app that wasn't their's?
Perhasps the virtual home button on iOS in the Car is pointing to a larger screen iPhone 5S with a virtual on screen home button to compete with Moto X and Nexus 4.
Isn't the physical Home Button for use if you have not paired an iPhone with the car system. People without an iPhone can use the basic built in features. The Home Button is the same as the Menu button in BMW. I still don't like the idea of having to reach to touch the screen. In the BMW I like having the iDrive right next to my hand in the center console. In a small car it is not much a stretch but in a big SUV you'd have to reach a lot further to touch the screen.
If it's integrated directly into the car rather than over the iPhone there may not be any way to disable detailed default location tracking that comes with iOS7. Apparently the service would be integrated with car navigation that requires location on, correct. Just as with Google there might be more than a few iOS users uncomfortable with anyone, even Apple, tracking and recording exactly where they've been, when, and how long they stayed there.
As only one of a couple reasons I personally think any dashboard services would come from the iPhone and not built in to the system itself.
By the way I meant to ask, what do you guys over there at Google think about Scamsung starting to push their own non Android OS? Does this worry Google at all? Just curious.
I still think Apple made a huge error giving Google maps the boot - they have a lot of catching up to do, in particular in the place naming accuracy and Street View department.
Here... Compare Apple 3D Flyover with Google Street View using Disneyland Paris:
Apple Maps 3D Zoomed Out -- to 3D Panned and Zoomed In (and everything in between)
Google Maps 2D Zoomed Out -- to Street View (and nothing in between)
You are forgetting Google was trying to hold out features from iOS that were readily available on their pOS. Apple absolutely did the right thing by booting them and going solo.
How could Google how back features on a app that wasn't their's?
C'Mon... Quit playing dumb... You know full well that Google supplied the backend data to Apple's maps app through iOS 5.
I read somewhere that Google was paying Apple to use Google's backend data.
I don't think anyone but the principals involved know what really happened... But most suspect that Google offered Apple the data for new features, like TBT, in exchange Google wanted to track users and/or include ads...
They couldn't resolve their differences and so Apple rewrote the Apple Maps app to get backend data from other sources.
It was a bit of a screwup for Apple... but they've recovered pretty well.
I suggest that it was a major screwup for Google... Google "owned" mapping on iOS -- now, they are an also-ran.
I think this article shows how completely out of touch some Apple blogs and fans are. (Note: Am typing this on a 13" MBA and have an iPad mini and iPhone - and two Android phones - next to me, so am impartial).
I am not typing this on my Galaxy S4 because it's a lagging piece of sh*t and I find it annoying!
C'Mon... Quit playing dumb... You know full well that Google supplied the backend data to Apple's maps app through iOS 5.
I read somewhere that Google was paying Apple to use Google's backend data.
I don't think anyone but the principals involved know what really happened... But most suspect that Google offered Apple the data for new features, like TBT, in exchange Google wanted to track users and/or include ads...
They couldn't resolve their differences and so Apple rewrote the Apple Maps app to get backend data from other sources.
It was a bit of a screwup for Apple... but they've recovered pretty well.
I suggest that it was a major screwup for Google... Google "owned" mapping on iOS -- now, they are an also-ran.
What was to stop Apple from making their own TBT using Google's data? They're doing it now using data from another source.
Comments
Quote:
Originally Posted by Oflife
I think this article shows how completely out of touch some Apple blogs and fans are. (Note: Am typing this on a 13" MBA and have an iPad mini and iPhone - and two Android phones - next to me, so am impartial). For starters, there is nothing at all new or innovative about any of the above. Since a few years ago, I have been able to dock even my most basic Android phone in my car (at the time, a Motorola DEFY running a very old version of Android) and do the following:
1. Issue spoken commands to do pretty much all I can do today with Siri.
2. Navigate to must about anywhere on Earth, with Google's excellent satnav killing Google Maps/Turn by turn directions
3. Obtain location info, such as nearest ATM, gas station etc.
Further, the navigation interface is not from above, but is down at street level like a regular satnav, so it's easy comprehend. Looking at maps from above is confusing because you lose your orientation, but that's another discussion. (I'm aware that Apple maps can do street level views now, but it couldn't even last year.)
I hate to say it, but Apple are years behind. Google Now today can do a huge amount, and lot of it will work in any car, simply by mounting your device above the dash.
I still think Apple made a huge error giving Google maps the boot - they have a lot of catching up to do, in particular in the place naming accuracy and Street View department.
You do realize that Google Maps and Now are Google's key leading features for Android, right?
The problem is that's all Google has, and Apple has largely caught up within a year. At the same time, Apple's iOS has some things Android doesn't have. And you know what those things are. So it's a wonder why you feel the need to do a superiority dance for a hobbyist platform with no good app exclusives, no advanced development tools like Core Data, no security, no enterprise support, no real integration, and so on. If you like Android, enjoy it. The world is not confused. Nobody has ever needed some comment troll to educate them about how their personally favorite product is so wonderful everyone else is stupid for not talking about it rather than the topic being discussed.
Quote:
Originally Posted by JLL
They are.
iOS in the Car is not Apple hardware in the car. It is getting iOS from your iPhone onto the car's existing screen. That's why the Home button is there: it's to use the screen's built-in features when an iPhone isn't connected.
AI is totally wrong about this.
The very first paragraph at apple.com about iOS in the Car even says so:
"OS in the Car seamlessly integrates your iOS device — and the iOS experience — with your in-dash system. If your vehicle is equipped with iOS in the Car, you can connect your iPhone 5 and interact with it using the car’s built-in display and controls or Siri Eyes Free."
The in-dash system is NOT running iOS.
Previous articles have described various ways iOS in the Car could be implemented (AirPlay wireless/cable integration, iOS appearance hosted by third party hardware, Apple hardware), with the pros and cons of each. None of them are an AI prediction, so there's nothing to be "totally wrong" about. The program is an expansion of Eyes Free, so there's no revelation in what you are saying, and that's been widely mentioned as a possibility, including within AI's coverage.
Quote:
Originally Posted by Oflife
I think this article shows how completely out of touch some Apple blogs and fans are. (Note: Am typing this on a 13" MBA and have an iPad mini and iPhone - and two Android phones - next to me, so am impartial). For starters, there is nothing at all new or innovative about any of the above. Since a few years ago, I have been able to dock even my most basic Android phone in my car (at the time, a Motorola DEFY running a very old version of Android) and do the following:
1. Issue spoken commands to do pretty much all I can do today with Siri.
2. Navigate to must about anywhere on Earth, with Google's excellent satnav killing Google Maps/Turn by turn directions
3. Obtain location info, such as nearest ATM, gas station etc.
Further, the navigation interface is not from above, but is down at street level like a regular satnav, so it's easy comprehend. Looking at maps from above is confusing because you lose your orientation, but that's another discussion. (I'm aware that Apple maps can do street level views now, but it couldn't even last year.)
I hate to say it, but Apple are years behind. Google Now today can do a huge amount, and lot of it will work in any car, simply by mounting your device above the dash.
I still think Apple made a huge error giving Google maps the boot - they have a lot of catching up to do, in particular in the place naming accuracy and Street View department.
well sure, you can dock you iPhone or droid phone on a dashboard mount now and do all that stuff. so?
currently, Apple's EyesFree also transmits and displays basic iPod-like info to your car's display screen too, as noted by bzzlink above. i suppose there is some droid equivalent ...
but just passively mirroring your smartphone's screen onto your car display like AirPlay - which is certainly possible now, i suppose there is even some droid equivalent - would not be very useful, and actually distracting. their display UI's are obviously not designed for that situation at all.
integrating the full capabilities of the Siri/Google Now voice OS UI into a comprehensive "virtual" car system is quite straightforward in concept, yes, because the bluetooth setups are there now. but an entirely new touchscreen UI layout specifically designed for a dashboard display - including also such specialized screen layout for every app it might run (starting with vehicle info apps from car makers and services apps like Sirius) - is what is needed that no one has done yet for iOS or droid.
so iOSC is basically reformatting a very simplified iPad touchscreen UI for this unique situation. no doubt some droid version will appear next year too ... even tho according to you, that should already exist now if Apple is "years behind."
but don't let rationale analysis get in the way of a good rant.
We were looking at the Ford SUV but I spent two minutes looking at there computer and said no thanks
You are forgetting Google was trying to hold out features from iOS that were readily available on their pOS. Apple absolutely did the right thing by booting them and going solo.
Quote:
Originally Posted by Chandra69
Quote:
Originally Posted by caliban10
Perhaps one of the Home buttons means drive to my Home.
Actually, I thought the same!
You wouldn't want that if your car gets stolen.
Quote:
Originally Posted by Oflife
I think this article shows how completely out of touch some Apple blogs and fans are. (Note: Am typing this on a 13" MBA and have an iPad mini and ..... ..... blah blah
Stopped reading.....
No one gives a frick. If you can't make your argument without this, you can't make your argument. You're hardly impartial.
[QUOTE]For starters, there is nothing at all new or innovative about any of the above.[/QUOTE]
Which you know, because not only have you seen this device in person, you've used it to the fullness of its capabilities.
Come on, man.
[QUOTE]I hate to say it, but Apple are years behind.[/QUOTE]
I hate to say it, but they're not even in vehicles, so no, they're not. They've neither won nor lost. They're [I]watching[/I] the game be played. :no:
How could Google how back features on a app that wasn't their's?
Wonder though if someone's going to be forbidden sushi at Apple for leaking information
Nope. Whatever it is, nope.
Isn't the physical Home Button for use if you have not paired an iPhone with the car system. People without an iPhone can use the basic built in features. The Home Button is the same as the Menu button in BMW. I still don't like the idea of having to reach to touch the screen. In the BMW I like having the iDrive right next to my hand in the center console. In a small car it is not much a stretch but in a big SUV you'd have to reach a lot further to touch the screen.
By the way I meant to ask, what do you guys over there at Google think about Scamsung starting to push their own non Android OS? Does this worry Google at all? Just curious.
Here... Compare Apple 3D Flyover with Google Street View using Disneyland Paris:
Apple Maps 3D Zoomed Out -- to 3D Panned and Zoomed In (and everything in between)
Google Maps 2D Zoomed Out -- to Street View (and nothing in between)
C'Mon... Quit playing dumb... You know full well that Google supplied the backend data to Apple's maps app through iOS 5.
I read somewhere that Google was paying Apple to use Google's backend data.
I don't think anyone but the principals involved know what really happened... But most suspect that Google offered Apple the data for new features, like TBT, in exchange Google wanted to track users and/or include ads...
They couldn't resolve their differences and so Apple rewrote the Apple Maps app to get backend data from other sources.
It was a bit of a screwup for Apple... but they've recovered pretty well.
I suggest that it was a major screwup for Google... Google "owned" mapping on iOS -- now, they are an also-ran.
Quote:
Originally Posted by Oflife
I think this article shows how completely out of touch some Apple blogs and fans are. (Note: Am typing this on a 13" MBA and have an iPad mini and iPhone - and two Android phones - next to me, so am impartial).
I am not typing this on my Galaxy S4 because it's a lagging piece of sh*t and I find it annoying!
There, am I doing it right?
What was to stop Apple from making their own TBT using Google's data? They're doing it now using data from another source.
Quote:
Originally Posted by dasanman69
What was to stop Apple from making their own TBT using Google's data? They're doing it now using data from another source.
Google.
Google rewrote their terms to be unacceptable to Apple.