- Dec 27, 2001
- 47,351
- 14
- 61
So, unless things change drastically between Apple and Adobe in the next few weeks, from what I'm hearing you can expect to see Adobe taking Apple to court over the issue. It's not going to be pretty.
lol, unless there's a contract, good luck
Yea, seriously. On what other grounds would they even have a case? Monopoly? I really am having a hard time picturing the DOJ backing that, especially given Apple's healthy - but not dominant - share of the smartphone space and tiny share of the PC market.
I guess it could be bluster by Adobe to try and get concessions, but I can't imagine Apple's lawyers falling for that.
I don't Adobe has a case (IANAL), but I can see why they are upset; Apple has been unwilling to incorporate their product into the iPod and iPhone, which is totally within Apple's rights (a little controlling, but whatever). So Adobe accepts this fate and sinks development time and money into creating an application that will compile down to iPhone code, Apple goes and blocks those apps from the App Store.
Perhaps not illegal, but it's the reason I refuse to buy an iPhone and Android will be my next platform of choice.
These two used to be so close. Adobe was what kept Apple relevant in those dark days. I wonder if Adobe will start delaying their professional software for Macs.
Adobe writes shit Mac software for a decade (flash for OS X is a joke and chokes even high end machines) -> Apple finally has a new platform which they have control over -> Adobe wants a piece of the action -> Apple blocks them at every turn.
Sounds like pay back is a bitch... While it's definitely not "right," there is nothing Adobe can really do about it IMO. I wonder if Adobe has some patents they may go after Apple with or something because otherwise a lawsuit seems pointless.
Adobe should just stop all Apple development of Photoshop, Lightroom etc and see how Apple likes it.
Adobe should just stop all Apple development of Photoshop, Lightroom etc and see how Apple likes it.
So, with Apple already burning cash in frivolous lawsuits with Nokia and HTC, and possibly Google and Adobe soon, when are their shareholders going to step in?
Adobe should just stop all Apple development of Photoshop, Lightroom etc and see how Apple likes it.
So, with Apple already burning cash in frivolous lawsuits with Nokia and HTC, and possibly Google and Adobe soon, when are their shareholders going to step in?
I'm personally glad Apple's doing this, I saw a demo from Adobe of a flash game that was cross compiled running on an iPhone 3GS, it looked unplayable...
What you have here, is a power play on Apples part. With the iPad it's obvious Apple desires to be the source for as much digitial content as possible. Look at the markets they have their hands in: music, video, tv, books, newspapers, magazines, etc. Apple doesn't want content providers to rely on someone else's tech to provide these services... they want it to come from them via their marketplaces.
The way I see it, with HTML5 on the rise, Flash and Silverlight are already dying, and Apple knows it. Apple just wants to benefit as much from it as possible, consumer be damned.
So the lawsuit isn't about Flash. It's about Adobe's Flash-to-iPhone compiler - which is a tool which basically lets you take a Flash application and create an iPhone app using it with a minimal amount of work. Apple recently updated their SDK specifically to disallow use of this compiler for iPhone apps.
An article about the OP's blog link:
http://www.appleinsider.com/article...will_sue_apple_over_cs4_iphone_app_tools.html
And more specifically - but without the lawsuit threat:
"Apple Gives Adobe The Finger With Its New iPhone SDK Agreement"
http://techcrunch.com/2010/04/08/adobe-flash-apple-sdk/
Thats the issue right there, Apple is already getting crap about dumping the 1st gen & second gen iPhones because the hardware isnt capable of taking on the new OS and still performing worth a damn.This all happened before
Apple ran into similar problems back in the early 90s, when all the application developers that had started their businesses on the Macintosh began seeking lowest common denominator ways to sell their apps to both Mac users and Windows PC users. This resulted in developers largely ignoring all the new features Apple developed for the Mac OS, including QuickDraw GX and PowerTalk.
Rather than developing apps for the Mac, developers such as Microsoft and Adobe began creating their own internal platforms that then tacked a Mac-native front end onto their new general purpose code. The result was that Apple suddenly became powerless to push its third party Mac developers to support the platform's unique features, resulting in increasingly less differentiation between the Mac and Windows PCs.
Ten years later, Apple similarly had a difficult time trying to convince its third party developers to natively support its new Mac OS X operating system. Adobe refused to bring many of its Mac apps to the new Carbon environment Apple created expressly to facilitate easy porting to Mac OS X; among the list of apps that never made the transition were FrameMaker and Premiere. Adobe didn't even bring Photoshop to Mac OS X as a native app until 2005.
Similarly, while Adobe joined Apple on stage in announcing the migration of the Mac to Intel in 2005, Adobe didn't release a Universal Binary version of its core apps until early 2007. The company never updated its existing Creative Suite 2 apps, nor the Studio 8 suite it had acquired from Macromedia.
In the future, Apple doesn't want to be forced to wait a few years for Adobe to get up to speed on its development plans. For the iPhone OS, Apple has established a rapid development cycle that demands that its app developers stay current with the latest firmware. They can't do that if they're tied to a third party development platform like Flash Professional, which is likely to lag Apple's own Xcode tools by months or even a year or more.
That being the case, it's hard to fathom how Adobe could invent a legal claim to force Apple to do anything to support its efforts to produce iPhone apps using alternative development tools.
Apple's chief executive Steve Jobs reportedly explained the situation to a user by writing, "we've been there before, and intermediate layers between the platform and the developer ultimately produces sub-standard apps and hinders the progress of the platform."
So the lawsuit isn't about Flash, guys. It's about Adobe's Flash-to-iPhone compiler - which is a tool which basically lets you take a Flash application and create an iPhone app using it with a minimal amount of work. Apple recently updated their SDK specifically to disallow use of this compiler for iPhone apps.
An article about the OP's blog link:
http://www.appleinsider.com/article...will_sue_apple_over_cs4_iphone_app_tools.html
And more specifically - but without the lawsuit threat:
"Apple Gives Adobe The Finger With Its New iPhone SDK Agreement"
http://techcrunch.com/2010/04/08/adobe-flash-apple-sdk/
The legal question isn't whether Apple shouldn't allow Flash on their iPhones, but whether developers can violate the Terms of Service agreement for being by merely using a rival's compiler.
Its a stupid game and Adobe needs to take its marbles and go home. As I said, the Android marketplace is perfect for them, let them be Google's problem when they deploy an update to Android and a crap load of ported apps don't work for consumers