Another Way Apple's Fight With Google Is Hurting Users
readwriteweb.com
readwriteweb.com
* iOS allows users to install only applications approved by Apple. This makes about as much sense as a house with built-in technology that prevents the owner from using any furniture, kitchen equipment, and entertainment device that isn’t pre-approved by the home builder.
* iOS prevents users from installing and accessing other app stores. (Other proprietary mobile OSs make it difficult or impossible to install third-party app stores.) This makes about as much sense as the home builder having the legal and technological power to prevent the homeowner from visiting certain shopping malls in the area.
Installing any app you want -- and any app store you want -- on your own device ought to be an inalienable right.
--
Edit: I updated the second point to reflect that Android does allow the installation of third party app stores -- see comments below. (Thank you mokeyfacebag, stanleydrew, and ZeroGravitas for pointing this out!)
Well written Android applications are structured like mashups. There is no main. There are multiple entry points for screens (aka Activities) as well as entry points for processing (Services), data (ContentProviders) and even a mechanism (BroadcastReceiver) for telling all interested apps about events (eg battery charge level changing, incoming calls, apps being installed). There is a mechanism for decoupled communication (Intents) which allow specification of a verb (eg VIEW, PICK, DIAL, EDIT) and one or more bits of accompanying data (eg text, urls, images). It is trivial to bring up/use part of another app that didn't even exist at the time yours was released and have the experience combined. (You can always tell iOS apps ported to Android because they don't do mashups or collaborate with the apps already on your system.)
This means that an iOS app will never be improved by other apps installed on the system, while Android ones can be. And because of Intents it becomes possible for a user to choose their own experience - want to use a different browser or app for viewing images? No problem. For example I installed the GitHub app on Android and it added itself to the AccountManager. Now other apps can collaborate with it (eg it supports the SEND verb which creates a Gist) or ask it to display an issue/user/commit.
The (long winded) point behind this is that app installations are far more valuable to Android users. If things were only decided on technical merit then Android will end up nailing iOS because of this. But that walled garden sure looks nice to many people, and it is rare for users to really notice what is going on and they definitely won't have both devices to continually contrast and compare.
I've got apps launching links in iCab, other apps using files from the Dropbox app, etc., so that seems a bit inflexible.
I get that Android's app-to-app crosstalk is considerably deeper, it's just the characterization of iOS that doesn't seem totally right to me.
Try alternate dialers. On Android you just install an app that claims to handle tel:// urls. You are out of luck on iOS. Try adding another social network that can handle sharing. Again you are out of luck on iOS until every source app adds libraries. And images, contacts, calendars, and whatever some startup thinks of next week.
iOS is trivial in this regard - there is essentially no cross app integration. That fits with Apple's walled garden model, and means that apps do not change their functionality after installation which fits in with Apple's review process. Having "deterministic" app behaviour hasn't hurt Apple so far - they rake in over half of the smartphone industry profits.
This is not true for Android. Some OEMs might ship a version of Android that is tied to a single app store (e.g., Kindle Fire), but I'm quite certain that vanilla Android can install any old .apk from any source.
Case in point: Google Wallet.
The openness of Google, nexus, and android is a big selling point for me.
I've got mobile broadband in my laptop. Imagine if the provider of that service would have a say over what programs I could run on my laptop. Very strange.
Video game consoles are similar - MS won't allow you access to the Xbox Live service if you've modded your hardware or installed different firmware.
Verizon doesn't care what you do with your phone, but they say that you can't get their cell phone service unless you run the device the way they want you to.
This is why the whole new Windows 8 direction scares me, too. For now at least, they are allowing desktop apps on Windows 8, but on Windows RT, Microsoft is just as bad as Apple with iOS. They won't allow you to sideload any apps. So if you want to use an app that wasn't approved by Microsoft, you'll have to jailbreak the Windows RT device. Sames goes for WP7/WP8.
What about game consoles? Calculators? Cars? Washing machines?
It's absurd to force a company to provide features and services by law. That is a huge violation of free trade and the rights of those who sell devices. You know what you can and can't do on a device before you buy it. If people cared as much about the issue as you do, they'd buy phones that allowed that. They don't. That is why your house analogy is so far off.
If someone creates software that runs on a game console, or calculator, and distributes it where users have a choice to install it or not, I agree with cs702, it should be up to the user/owner of the device if they want to take the risks to install it or not, the manufacture of the device shouldn't actively prevent such installation, but simply say, "If you do this, we won't support it, and it voids your warranty, but it is your device now."
They don't even after to make it easy for the users. It's not that Apple should provide another way for them to install another app store, that's a feature. It's that Apple shouldn't religiously hunt and destroy every means of jailbreaking just _because_ it allows users out of the Apple Control Sphere.
This is exactly how things work on Macs now and Mac users aren't exactly swimming in malware.
Edit: now that you have completely changed your second point, my comment is not a valid response. Please refrain from substantially changing your comments once posted.
Apples App store and approval process is basically an online version of the classic game console model with much cheaper entry fees for developers and must less restrictive rules.
All the reasons why game consoles have been successful vs PC gaming apply to Apples success, lower piracy, less problems for users, less complexity for developer because of controlled hardware and software platform. All the same limitations apply as well.
Apple prevents sideloading simply to have greater control over the platform.
What information do you have the confirms Apples doing it only for "greater control"? Would they also not want to prevent piracy in order to make their platform more attractive to developers?
What is the difference between a Nintendo DS and a iPod touch other than Apple has a wider range of apps other than games?
Apple has every right to vet the apps it sells in its app store. And it makes sense to do so.
But I agree with your second point, that consumers should have the option to obtain apps from other stores.
You're acting like: 1. Jailbreaking doesn't exist. 2. Apple is actively working to prevent people from jailbreaking their devices.
This is simply not the case. Apple is neither technically nor legally hindering anyone's ability to jailbreak their devices.
Your problem is analogous to complaining you ought to have the inalienable right to go outside, but you were born in a home with doors. But once you open the door, the world is yours for the taking. No one is stopping you.
Your analogy doesn't work because the only way to open the door on your Apple house is to pick the lock.
http://www.wired.com/threatlevel/2010/07/feds-ok-iphone-jail...
But keep things in perspective. Apple chooses to sell appliances, not platforms. Apple products are more like toasters than houses. I agree that I should certainly have the right to modify my toaster, but I don't begrudge the designers for making it difficult for me to do so.
http://www.slideshare.net/bcousins/when-the-consoles-die-wha...
It is unfair to present this ongoing situation as a war on Google by Apple. It is a competition between the two companies. Not to beat a long dead horse, but the war between the two companies started when Google entered the mobile device space.
* Apple began developing the iPhone in 2004 and released it in June 2007.
* Android was founded in 2003 and Google bought the company in 2005. Google and partners announced the Open Handset Alliance in November 2007 and the first Android phone was released in October 2008.
So far, so good. Two companies that did not start out in mobile telephony/computing both began developing products and entering the space around the same time, competing with the existing smartphone manufacturers, particularly RIM and Nokia.
Google's competitive practices have consisted mainly in developing and iterating a solid product, partnering with a variety of hardware providers to develop a large ecosystem and market share, and occasionally releasing flagship devices to raise the state of the art.
Google has borrowed some innovations from its competitors and developed some innovations of its own.
Apple's competitive practices have consisted mainly in developing and iterating a solid product, partnering with developers via an app store to develop a large ecosystem, and maintaining control of the design and manufacture of devices to maintain standards of quality.
Apple has borrowed some innovations from its competitors and developed some innovations of its own.
Apple has also pledged "thermonuclear war" to "destroy Android", launched a patent war of attrition against Android hardware vendors, and is now, apparently, hobbling the functionality of its own device in an attempt to marginalize Google.
There's competition, and then there's anti-competitive behaviour. Apple would do better to stick with the former, since the company is obviously very good at designing, building and marketing highly competitive products.
In fairness, this was a comment made by Steve Jobs. Apple never made such a pledge and Steve Jobs is no longer at Apple.
In fact, you don't have to look far to find "industry insiders" who claim just the opposite. Current CEO Tim Cook publicly stated that he hates litigation (his words) and he met with Larry Page recently to discuss ways to "live peaceably together" and avoid unnecessary litigation. Is this sincere or just lip service? I don't know, but if we're playing the game of predicting Apple's future, it's important to the discussion.
...while we're basing points on pure speculation, I'd like to posit that Google is using the price and availability of its Maps service as a weapon in this iOS vs. Android fight. They're well within their rights to do this, and absent knowledge of what happened it's more reasonable than "Apple is hurting their users in a misguided attempt to compete with Android".
Also, who cares who started it? Usually, competition is good for consumers--in this case, if Apple approved this app, competition would mean we have two natural language search apps on iOS. The problem is that Apple is "competing" by hurting their users, not by improving their products. And Google does this too (see: lack of turn-by-turn navigation on iOS), but my sense is they do it less.
As the article does, it's more helpful to focus on how the competition takes place than on casting blame for starting the "competition," which is fundamentally a good thing.
I could. (Siri would even be able to launch apps, etc, due to Android's more robust API)
Also I think you are being a little disingenuous. When you have the CEO of one company saying it will wage thermonuclear war on a product, that is clearly a statement of intent to destroy said product that goes beyond competition in the marketplace.
> ...the war between the two companies started when Google entered the mobile device space.
Entering a market isn't usually equated with starting a war.
It's been said that the Hohenzollern family had a specific policy: Never start a war unless victory is assured. War is a "two edged sword." It has the potential to do both sides serious harm.
http://en.wikipedia.org/wiki/House_of_Hohenzollern
Apple needs to do some soul searching. They need to be looking out for their customer's best interests. Somehow they've lost the way, and empirically, this is no longer the case. Maps is just the biggest symptom. The article points out another.
As for: Not to beat a long dead horse, but the war between the two companies started when Google entered the mobile device space.
Was entering the mobile market a bad thing? was it not allowed? is it for Apple alone and no one else's? that statement doesn't make any sense. I'm sure there was a time when Apple entered the mobile business and Nokia wasn't none too pleased.
Seems like a hell of a good reason to me.
Was entering the mobile market a bad thing? was it not allowed? is it for Apple alone and no one else's?
Google and Apple had a symbiotic partnership, like WinTel, which dominated for the better part of two decades. Microsoft stayed out of chips, Intel stayed out of doing an OS. If one decided to take 100% and get into the market of the other, it would create a nasty situation where both were forced out of their comfort zones to make crappy stuff. It would break trust. And yet that's exactly what Google did with Android: it had a partner that didn't have search or web in its DNA—and thus an ideal partner—and decided it could take the partner's market. Pardon the teen parlance here, but that's a little backstabby. Apple's indignation, in my view, is entirely justified.
Apple either sends users and data to the belly of the beast that decided to complete head-on with them (making Android better, by the way) or figures out how to do this stuff themselves and offers beta products. I would say that Apple doing the latter given Google's aggression makes a lot more sense than Google's aggression in the first place.
B doesn't follow from A. First off, it's untrue that nobody else had the software expertise to challenge Apple: there's Microsoft, RIM, Palm, plenty others in 2007. Apple had 1% of the market and no monopoly. But let's pretend that none of that is true and that Apple did come to dominate the market. The dependence was mutual, and Apple would have every reason to fear dependence on Google as visa versa. This should have rationally encouraged cooperation. Apple's only alternative for search and web services would have been Microsoft, even more of a direct competitor (then, in 2007), and one to both Apple and Google at that! Undesirable.
Second, Google's handing out bullets to its competitors like candy and is hurting its ability to lock down mobile. In China, Baidu has ripped out core Google services from Android and has replaced it with Baidu services. Amazon has done the same thing for Fire and replaced Google with Bing. If Facebook were to ever build a phone, it wouldn't have to look much farther than Android. And of course Google on iOS isn't long for this world.
Third, the dependence on a single dominant player still exists. Samsung owns the Android space and can hold Google integration hostage for all kinds of goodies. It's pretty much back to square one re: Apple, except Samsung has OS alternatives (including forking Android [hey, who made S Voice?]), where Apple didn't have Google alternatives. HTC is in the dumps and Google is in a tough spot with privileging Motorola, its new baby, for fear of angering aforementioned Samsung.
So no, in short, it's not clear at all to me that this was a rational move.
You are also assuming that only Google benefited from that relationship which is wrong.
Google is a software and services company and in an iPhone world Apple would decide how and when these services are presented to users, if they are presented at all. That is an unacceptable amount of risk as Apple had a disproportionate amount of leverage in that arrangement.
And I disagree with you about what the balance of power would have been in a hypothetical Apple-Google cooperative partnership. What were Apple's alternatives if Google were to withdraw as a backend services partner--perhaps a direct competitor in phones? That doesn't seem too palatable. Doing their own backend services? How's that working out for Apple today?
Now would you expect Ford to continue to buy tires from Firestone?
Samsung is Apple's biggest competitor in the phone space but Apple still buys a large number of the parts used in their phones from them. Apple has been steadily replacing things like processors with their own designs but this certainly isn't because of some petty offense they've taken to Samsung entering their market. It's because it's in their best interest to design their own parts (especially long term). Apple does come off as being emotional about Android with the decisions they've made (especially Maps) but implementing their own Maps and other features of their phones themselves is a good long term business plan. In the case of Maps, they launched too soon but working on their own mapping solution was a good decision.
Both parties are acting in what they believe to be their best interests. I don't fault either. (and btw I completely agree with your second paragraph)
Misinformation. Apple isn't BLOCKING anything!
Apple released, in iOS1, Apple Maps powered by Google Maps API Data.
Google, wanting to monetize Google Maps API access, began charging expensive rates for their heavy users, of which Apple was the heaviest user of all.
In response to Google asking Apple for millions of dollars for a service they provide for free on every other platform, Apple decide to change the data source in Apple Maps.
Google has yet to provide their own app on iOS for mapping, as they're likely pissed that their million-dollar-lunch just ended and now they have to provide a service for FREE.
I'm so tired of this blatantly anti-Apple bias.
Furthermore, Apple does not get their data from "Apple Maps". They pay to license it from TomTom and other companies (though they do, of course, also produce data of their own that gets combined with the third-party sources to produce the aggregation that is Apple Maps).
I don't know how much you meant by "millions of dollars" but it was probably substantially less than the $267 million Apple paid to acquire C3 Technologies to add 3D maps to their offering.
Apple's decision was a great long term decision for them but it did hurt users in the short term (hence Cook's apology).
Paying millions of dollars for maps is a tiny drop in the bucket for Apple and a tiny drop in the bucket for Google. Whatever disagreement they had over maps it almost certainly was not because Google charged too much. Providing additional ads/services to iOS users is significantly more valuable to Google than whatever paltry millions they could have made by licensing their maps.
Large companies do business through special contracts that have their own terms, and the maps contract reportedly is still valid for another year or so.
Looking closer, it's not even clear that ReadWriteWeb asked either party for a comment... note: "Google’s PR response to questions like this is that “we’re working closely with Apple” on getting it released." and "Well, Apple doesn’t talk about these things, so all we know is that it isn’t out."
If anyone wants to watch Scott Huffman's demo of natural language voice search from the search breakfast, the relevant section of the video is on the web: http://www.youtube.com/watch?v=8a2VmxqFg8A#t=10m43s
Gee whiz, I wonder why apple suddenly has a bitter taste towards apple? This makes siri look embarrassing.
This is nothing more than a blog rant.
1- Apple you S.O.B's, why won't you let me do as I wish with my phone
2- Apple, this is your product and I understand that you have the absolute right to do with it as you wish.
I actually find myself in both camps.
Sometimes I wish Apple would let go and treat this like selling Windows or OSX: They provide the OS and let others integrate apps as deep and wide as they wish. Yes, this would mean things like providing developers full access to all resources as opposed to the restrictions we work under today.
On the other hand, I also find myself in a position from which I respect the quality and stability the platform has offered since day one. It's almost like this is a benevolent totalitarian regime.
Until iOS 6 and Maps.
What I see now is a company that might not be making the right decisions for it's customers and users. You could argue this has happened with OSX as well. By releasing a substandard Maps application Apple has proven that it is now willing to make decisions that do not include quality, stability and the users' best interest in the process. I cannot, in any way, imagine that this would have been approved by Steve Jobs. Maybe I think too much of the man, but I don't think I am wrong.
Apple cannot make all the right decisions for this platform. No company can. Not in the long run. At one point you have to let go and allow others to help evolve the platform in ways a single company could not possibly imagine. Not doing so has the potential to tilt the scales and have users eventually vote with their purchases and move to other platforms.
Until Apple allows opt-in sideloading of apps I'm done with iOS.
Not only is this the reason the author percieves the situation as harmful, but avoiding the harm is entirely within the author's control. Just purchase different devices.
When Apple doesn't allow Google search because it is competing with Siri(Ssshh.. actually, it's a lot better than Siri), I am losing as a user.
I wish both companies can work together. In an ideal world for users, the backend technology is powered by Google and the interface and interaction is designed by Apple. That will make a groundbreaking product for sure.
Apple is not playing unfairly here (as you might argue in other battles, such as with Samsung), and neither is Google. They are competitors, and both Maps and Voice/Siri are key functionality for these mobile devices: Google spent a bunch of time building their technologies, and if Apple wants to use it on their highly profitable hardware maybe they should have to pay a lot for it; example: half their margin.
This is, then, what competition is: it is two people/companies duplicating effort to get a similar result, purposely putting each other down whenever possible, and setting up situations where they have whatever advantages the system allows over the other. The customer often loses in these situations, because so much blood and sweat has to be lost to the "fight".
The alternative, "cooperation", normally is frowned on in these circles. Even in the aforementioned cases of open source projects, such as the with web browsers (where the cost is painful fragmentation caused by some vendors misunderstanding or not disliking specifications enough to not bother implementing them) or compilers (the gcc/clang split has been brutal: clang doesn't really compile things correctly, and yet is now the only compiler from Apple for Mac OS X), people are again all "competition is good, deal with it".
Well, sometimes, often, possibly always (yes, even for the restricted domain of "prices" and even when cooperation includes "trusts", at least apparently according to Judge Posner; however you certainly needent go that far with this argument): "cooperation is better, yielding a more powerful result for less development cost"; this is, after all, the premise of open source collaboration.
The iPhone 5 marks the first time in the product line's history that it was not advancing the state of the art.
2) It wasn't just the bundling of IE, but also the use of APIs to prefer and favor IE over third party browsers, and restrictive agreements with OEMs.
Also part of the finding of fact in the case was the nature of how web browsers were obtained in that time period, long, slow downloads. Giving the bundled option a serious advantage. But again before we even get into the anticompetitive-ness of Apple, which no doubt many of their practices are, without a monopoly, it's fair play.
I am not a lawyer, but I think you can be brought up on charges of anticompetitive behavior without "having a monopoly".
Can someone with more knowledge in this area comment?
That PDF provides a pretty good summary of the FTCs scope, and under the current mobile market, it doesn't seem like they'd have any reason to involve themselves, especially when alternatives readily exist.
Apple has 25% mobile market share. Android has 50%. Microsoft has about 90% desktop market share for over a decade. DirectX was made to kill off OpenGL. C# was made to kill off Java and keep software running on Windows. Microsoft killed of Netscape and a decade later IE6 isn't completely dead.
Android isn't going away and by my estimate it will always have more market share than iOS.
Btw, Microsoft completely killed of all other PC operating systems when they required PC vendors to pay for shipping DOS, regardless of the OS they actually shipped.
When companies write apps in C# for the Microsoft platform, they are going to pretty much stay on the Microsoft platform. Those apps, for the most part, aren't ported to the Mac and Linux (please skip the Mono discussion, it's not a 100% solution). Fortune 500 companies and commercial companies are locking consumers into Windows. Maps is one product. There are thousands of C#, Windows only apps.
If Apple had a monopoly, or even close to one, in phones then we would have a problem. However, Android leads by a wide margin and since they sell better in the rest of the world, Apple's little walled garden doesn't really matter.
Objective C was developed before Steve Jobs and he simply adopted it, or his engineers did at NeXT. Personally, I'd like open languages/platforms that offer a little more reuse.
Microsoft writes most of its systems-level software in C++. Microsoft also writes a lot of C#. WCF and WPF are both built on the .Net stack. Bing runs on ASP.NET. Lots of stuff at Microsoft is build in C#, for the same reasons lots of stuff outside of Microsoft is build in C#: it's modern, safe, fast, and pleasant to work in.
> If C# wasn't the only case then it might be acceptable. DirectX, for example, was done to kill off OpenGL.
No, DirectX was written to replace WinG, which is what most games for Windows were written in prior to DirectX. I don't believe OpenGL had any traction on Windows at that time.
> Microsoft hired away Borland's language team, including the Delphi developer and proceeded to build a better Java that only ran well on Windows, and some might say that they accomplished this. :-)
This might be interesting if Microsoft had hired James Gosling away from Sun to work on C#, but that's not what happened. They hired staff away from Borland, who didn't design Java at all. You're conflating unrelated things.
> Objective C was developed before Steve Jobs and he simply adopted it, or his engineers did at NeXT. Personally, I'd like open languages/platforms that offer a little more reuse.
I fail to see the relevance here. The Objective-C used by Apple today is by no means the same as the Objective-C that NeXT started with. NeXT and Apple extended Objective-C significantly at both the language and the library level. This the the "embrace, extend, extinguish" cycle you accuse Microsoft of.
It's strange too that you have a problem with C# being proprietary, but you don't have a problem with Java being proprietary. Oracle owns both the language and the implementations that everyone uses. That it's part of their business plan to maintain it for Linux does not change its fundamental nature.
And just so you know, Microsoft did open the source for C# under admittedly restrictive terms. Look up Rotor. And they have issued a Community Promise that protects projects like Mono. And yes, Mono counts, just as surely as GCC counts, unless Microsoft also owns C++.
Mono is fine but it's not nearly as good as Microsoft's compiler. C# is a great language. It would be great if Microsoft simply open sourced it.
There's nothing preventing anyone else from adopting C# via Mono, is there? Also nothing stopping other companies from improving Mono.
>Google uses "Java" for Android.
Got them sued, too. I think they were within their rights, but this shows that "openness" is not synonymous with safety.
>It would be great if Microsoft simply open sourced it. No arguments from me. I'd love that as well, though I don't see it happening any time soon.
DirectX was made to kill off OpenGL. - DirectX was never compatible with OpenGL. It was created to provide a Windows-95 replacement for WinG which was being deprecated. OpenGL wasn't even originally intended for gaming, which is why it had software emulation for missing hardware features.
C# was made to kill off Java and keep software running on Windows. - C# was also never compatible with Java. Calling it an extension of Java is like calling Ruby an extension of Perl. C# was created to fill a gaping hole in the Windows development world: building native apps in a modern language. Java is ill-suited to building applications that feel native on Windows. It doesn't have easy interop, the UI looks wrong, and it requires installing a huge JRE. On top of that, Java progress at the language level was pretty stagnant. Lambdas, delegates, generics? Sun wasn't interested in any significant new features until C# appeared.
Microsoft killed of Netscape and a decade later IE6 isn't completely dead. Can't argue that one.
This way of operating is what most tech commentators don't really understand. I think the beauty of this strategy is that you don't need to have a monopoly to make the most profits. At any time, there will be a majority of the market using other products, but since Apple is optimizing their platform for quality and high profit margin, they will command the leadership in profits (if they continue doing good products that maintain their customers happy, I mean).
That's not necessarily correct. To determine if they have a monopoly you need to look at the amount of software sold on each platform, not just the number of total devices for each OS.
I think, the app store is a market. I also think, blocking, or even just delaying, entry to the market is anti competitive.
Google appears to be ready to go. Maybe their app violates the app store agreement somehow, and it's bouncing through the review process. Nonetheless, as an external observer, it looks like apple is dragging its feet. A review takes about two weeks, right? Four+ iterations seems like a lot.
It seems to me there are many buyers and sellers in the app store.
I'm pretty sure you're just trolling at this point, but i'd be interested in you explaining your point of view. Hopefully, you would be kind enough to use more than 10 syllables.
That’s the connection you are missing. You have to explain why, in your view, every market has to be a free market (or, at least, why the App Store should be a free market).
I think your view that the App Store has to be a free market is pretty crazy. I cannot understand it. I really do not understand how anti-competitveness figures into this.
Apple is one of many players in the mobile space, far from the largest. In light of that I really don’t see why they have to offer a free and open market. Why shouldn’t they be free to sell or not sell whatever they want?
–
P.S. I hate it when people say that someone is trolling just because they do not agree. That is so lazy and cheap.
Apple can do whatever they want - it's their toy store. I'm not saying it must be a free market. There are two possibilities regarding the delay of the google app. 1, it's taking a long time to actually review the app. 2, Apple is delaying approval, hoping siri will get more market share.
The more time passes, the more it looks like 2 is the case.
Now, this is my speculation about how our thinking differs. You seem to think Apple would only ever do #2. That, because it is their toy store, they will actively quash competing apps, even apps that don't violate the terms of service. Or, at the very least, pay far more attention to threatening apps than a random fart app.
I'm more nieve than you, so I'm willing to allocate some probability to #1.
Apple is "already doing what you'd expect a dumb monopolist to do."
Source: http://bloom.bg/OXP5Ad#ooid=Q5azF4NTq51l-7YDNIS84TWeSqfF0SQv...
The point was, which you clearly missed - there can not currently be two voice assistanst AT THE SAME TIME in use. Googles thing does not replace Siri. If Google had something to replace Siri and Apple blocked it, then yes, that would be anti.
Were my comments: 1) derogatory or offensive? 2) factually incorrect? 3) off topic and/or did not add to the conversation? 4) without any meaningful content. Ex: "Yes!", "Nice post!", "LOL!", etc?
Really? Really?? What is f..ing wrong with you people?
I beg to disagree. Android allows you to easily install additional keyboards, for people who want to switch to, say, Swype, or to use a different input method for their non-Latin alphabet.
So much better.
Besides, if the better search is an app, but you desire unification more there is no reason to download the app.
I honestly don't understand. People act as if Apple is entirely incapable of creating a superior product down the road from Google's. I think that there are obvious competitive advantages to replacing Google's Maps with Apple's Maps in iOS6.
But it seems that everyone just makes the baseline, "duh" assumption that clearly their only possible motive is to screw Google.
Is it not possible that Apple also -actually- believes that version 1 of iOS6 Maps is just the precursor to a product that they will eventually make far superior to Google Maps?? These are not mutually exclusive concepts.
So this hand-wringing about how Apple is screwing users... Call me naive, but I amk completely open to the idea that this is a short-term issue that actually has the possibility to -benefit- users in the long-term, as Apple takes it's lumps and learns what users want in a Maps application, and then eventually deliver things users didn't even know they wanted in a Maps application.
I've really yet to see anyone acknowledge this thought.
edit: You know, I'd at least appreciate a counter-point with the downvotes to my argument. Honestly interested in why I am incorrect. Just saying. shrugs
I am talking about Maps because that is the only thing we have concrete facts on. We have no idea the real reasons the Voice app is not in the App store right now. We simply don't. So I feel it's silly to ascribe motives to something we know nothing about. Obviously, if you have some sort of vendetta against Apple as a company, in a vacuum of information, you will automatically ascribe motives.
I do find it funny that I'm the one "whining" when all I am doing is pointing out is that perhaps the hand-wringing and whining of users about Maps is #1) a touch overwrought and #2 potentially beneficial for users in the long-run. That's all.. And I use the new iOS maps every day and haven't experienced a single problem yet. I'm not saying they don't exist, but living in a large city and using maps to navigate on my bike every day... Nary an issue.
You begin by talking about your macro view of things and all you do is whine and cry about Google Maps when the article is about voice? How can you have a macro view of things and mention a single app? Try and stay on topic at least?