April 2010
« Mar   May »



« | Main | »

The Apple is Really Rotten

By Rich Tretola | April 9, 2010

apple-rottenAs a follow up to the recent snubbing with the iPad being released without the Flash Player Apple has again targeted Adobe’s plans for compiling apps to iPhone.

Last year at Adobe MAX, Kevin Lynch appeared in a video spoof of Mythbusters where the Flash CS5 iPhone packager was announced. There has been some question on how this packager actually works and with the recent changes to the developer user agreement within section 3.3.1.

“3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).”

So, what does this mean? Well it looks like the greed of Apple continues to grow as well as the obvious hatred of Adobe. Greed because they would like to completely corner the market for tooling used to create iPhone and iPad applications and hatred because it is pretty obvious that Apple would like to crush Adobe’s upcoming Flash CS5 launch.

What should Adobe do about this?

First off, they will need to make their packager compatible with the new policies by showing that the work flow includes a source code conversion from AS3 to one of the approved languages before compilation.

Second, it is time for Adobe to fight back by pulling support for OSX from the supported operating systems of their flagship Creative Suite at some point in the future and strengthen their relationship with Google and target Chrome OS for future builds of Creative Suite.

What do you think Adobe should do?

Topics: Flex, mobile | 48 Comments »

48 Responses to “The Apple is Really Rotten”

  1. Pureinvestor Says:
    April 9th, 2010 at 8:08 am

    Adobe should buy up apple, fire Steve jobs, and put flash on all the devices.

    Reply to this comment

    Rich Tretola Reply:

    Um, Apple is like 12 times larger than Adobe.

    Reply to this comment

  2. Antony Says:
    April 9th, 2010 at 8:19 am

    Nothing. The device is from Apple and only this means they have all control over it. Like it or not.

    Reply to this comment

    Rich Tretola Reply:

    Actually, that is not entirely true. Just ask Microsoft about Internet Explorer and anti-trust lawsuits.

    Reply to this comment

  3. Chinmay Says:
    April 9th, 2010 at 8:21 am

    I agree that Adobe must fight back. But not supporting OSX doesnt seems good. Most of designers use photoshop+OSX combination and not supporting OSX would only result in benefit of MS who is trying to push its blend/silverlight suite to designers.

    Reply to this comment

  4. Andrew Westberg Says:
    April 9th, 2010 at 8:23 am

    Apple won’t stop unless the devs step away from their macs and switch to Windows, Chrome, or Linux. Everybody keeps complaining, but nobody is voting with dollars. Apparently, the apple-flavored cool-aid tastes too good.

    Reply to this comment

    Joel Fiser Reply:

    Finally some sense.
    Flashers shouldn’t be developing for a company that wants to destroy Flash in the first place.


    We are the developers – dammit. Stop being a bunch of pussies and, if you believe what Apple is doing is bad for the Internet – let’s do our best to destroy Apple.

    I’ll say it agin… WE HAVE THE POWER.

    Reply to this comment

  5. Adobuoy Says:
    April 9th, 2010 at 8:24 am

    Chrome OS isn’t designed for hardcore apps – it’s not going to be that kind of operating system.

    Agree that Adobe are getting a raw deal here and that Apple are being douche bags – but Google aint exactly going to be the salvation of the world either!

    Reply to this comment

  6. Ad Says:
    April 9th, 2010 at 8:31 am

    Greedy? Unfortunately for us Flash devs, it’s entirely up to Apple what they do with their own platform – it’s not like we have some inherent right to publish for iPhone.

    Reply to this comment

    Ross R Reply:

    Actually we do…

    Its a law in the USA that you cannot use power (and greed) to inhibit competition and innovation.

    This change is blatantly stopping innovation and competition by disallowing all competitors (not just Adobe mind you) from creating products that could possibly directly compete with their own. If Adobe products allow people to dev for iPhone, as well as Android, Chrome, etc… then the same app can compete directly with Apple from other platforms. This change seems to be intended to stop this type of competition.

    Reply to this comment

  7. Ginkgo Says:
    April 9th, 2010 at 8:36 am

    Adobe should port Flash to Silverlight (similar to that C code to Actionscript converter), and then you could take on Apple via Windows Phone 7. As an added bonus, it would help solidify Silverlight on the marketplace and provide Adobe with a real competitor.

    Flash developers would then be able to easily use either plug-in technology from Adobe’s development environment…

    Reply to this comment

  8. Joel Says:
    April 9th, 2010 at 8:55 am

    Adobe doesn’t have the kind of capital to buy Apple even if Apple would accept a bid for sale. Jobs has too much stake in the company for that to happen.

    The best thing for Adobe to do in response to Apple’s constant attack is to listen. Apple’s main claim to keeping the flash platform away from iPhones and iPads is due to memory/processing concerns. They address those and put some money into research showing that Flash on portable devices is feasible without a crunch and Apple would have no arguments publicly, unless they finally own up to the “Well it’s our toy” argument.

    Alternatively, they could also use Objective-C to write a flash interpreter, bit of a pain to probably do that, but if you can get Hulu on an ipad, I think the wave will crash.

    Reply to this comment

    Ross R Reply:

    Adobe HAS addressed the memory/processing concerns – and HAS been spending a lot of time and money researching and proving that it works. Check out the numerous videos displaying Flash on all platforms except the iPhone/iPad. Adobe has stood up to its side of that bargain, and Apple responds by saying – whoops, sorry, your devs aren’t good enough for our platform.

    Reply to this comment

  9. Matt Perrin Says:
    April 9th, 2010 at 9:01 am

    Forget the OSX vs. Chrome OS battle. Won’t work and you can’t convert the diehard Mac users to trade OSs just to get access to Creative Suite. If so, they would have switched years ago. Someone (Apple?) will make a CS clone on OSX and that will be it for Adobe. Actually, now that I’m thinking about it… why hasn’t Apple done that yet!?

    As far as the iPhone. If you can’t take it on directly then go all in on Android & Win7. Adobe already announced Flash Player 10.1 & AIR for Android at the Mobile World Conference back in February in the link below…

    So, get the same thing going for Mobile Win7.

    And Adobe, PLEASE create a viable marketplace for mobile, tablet & desktop users to browse apps & purchase them. The Adobe AIR Marketplace is a complete joke. Emulate the iTunes model, make it a seamless experience, don’t make it difficult for users to spend their money or find stuff. And make it an app like iTunes integrated into the Mobile or even Desktop/Tablet experience.

    If you wanted to go really crazy, open the marketplace up to hosting Android & Win7 native apps as well as desktop apps. Yeah, it’ll bleed over into the Flash stuff but you’ll get a larger pool of potential customers browsing all of your apps.

    Am I forgetting anything? Cheaper tools? Maybe a cheap version of Flash Builder so that the novice / hobbyist / student can get involved in Flash development? All I keep hearing about the iPhone XCode SDK is how easy it is to use and get started making apps right away. Flash has a bit of a learning curve and the current pricing makes it prohibitive to just casually learn.

    Reply to this comment

  10. Lee McColl Sylvester Says:
    April 9th, 2010 at 9:14 am

    I don’t think Adobe should do anything. It’s us that Apple are affecting, with Adobe as the second party. If Apple make it harder for the developers, then we’ll build our amazingly cool shit on Android phones, instead. In time, these amazing apps we’re building will win paying customers cash to the Android market and Apple will see a decline in sales. Ergo, it’s up to us to make this change.

    Where would Apple be if no developers built apps for the iPhone? Maybe their slogon would have been “We could have had an app for that” ;-)

    Reply to this comment

  11. Dan Says:
    April 9th, 2010 at 9:32 am

    “Where would Apple be if no developers built apps for the iPhone?”

    Should that read “Flash Developers” built apps for the iPhone? In which case I think the answer would be: In exactly the position they are now.

    Reply to this comment

  12. Lee McColl Sylvester Says:
    April 9th, 2010 at 9:41 am

    I think you underestimate the number of Flash developers that have and are developing for the iPhone… A big portion of Apple’s apps have been built by Flash developers and I could name a long list of friends and ex-colleagues that are or have done so.

    Also, think about the number of Unity3D dev’s that will also be hit by these issues. I can’t see, really, how CS5 will differ in those legalese phrases from Unity.

    Reply to this comment

  13. Steve Says:
    April 9th, 2010 at 9:45 am

    No tit-for-tat crap. That will only make developers and designers pissed off at Adobe too. So Adobe should not pull CS5 form Macs.

    I find myself wondering what Adobe’s contingency was for this. I mean, really! Who actually believed that Apple would allow Adobe to sell tools that made it possible to buid Fash apps that deliver to iPhone. So does Adobe have an ace up it’s sleeve?

    It’s interesting, to me, that Apple didn’t have the nuts to wait until a month after CS5 hits the shelves before changing the terms…

    Reply to this comment

  14. Carlos Nazareno Says:
    April 9th, 2010 at 10:11 am

    AIR is going mobile on multiple mobile platforms.

    Adobe should do a really good job with the Adobe AIR Marketplace/Shibuya, work tightly with carriers & device manufacturers and provide a really good alternative to the Apple App Store for developers.

    The AIR Marketplace should give a very good experience to users, make purchasing apps easy, provide a good way of featuring great apps (and some way of filtering out crapware – would a user generated rating system be enough for this?) and then give great support to developers and make sure developers can monetize on the AIR Marketplace.

    Also, Adobe should play well with carriers/manufacturers and incentivise them to push the AIR Marketplace (revenue sharing or what have you, as long as developers get a good cut, can a make a living selling AIR apps and customers have a hassle-free smooth system for purchasing apps).

    That’s how you’ll fix things.

    Oh, and don’t be evil and lazy like Apple ;)

    Reply to this comment

  15. Lee McColl Sylvester Says:
    April 9th, 2010 at 10:14 am

    Look at it this way. Adobe did the right thing. It provided for its customers. Apple did the bad thing, by throwing this crap in our faces. So long as Adobe do the right thing, they’ll have loyal followers. I’m more Adobe’s man, now, than I ever have been…

    What I can’t understand, though, is the legality of this. In the UK, that sort of licensing wouldn’t stand up. Apple could be easily taken to court if they tried to uphold the licensing terms. It would be deemed grossly unfair. How come nothing has been done about it? How come Apple’s lawyers allowed this to be printed? Tbh, I find even the whole concept of the App Store to be grossly unfair. Sure, Apple could have the App Store and that’s their prerogative, but there should be other means of allowing software on their devices (besides jailbreaking it). To do otherwise is to corner the market. Yet, Apple are allowed to do it.

    M$ has been sued for much much less…

    Reply to this comment

  16. Rodion Says:
    April 9th, 2010 at 10:14 am

    Adobe may start looking to Linux, at least port development tools (CF Builder, Flash Builder) for Linux – many developers are Linux nuts. Later CS can be ported, but there’s not so many designers working on Linux – it will be hard to convince designer move to Linux from Win/Mac.

    Adobe has power even to have it’s own Linux distribution with all tools ported and polished to work within this environment. Corel once tried same, but to be honest, failed. Pushing my crazy idea to it’s end, Adobe can make entire workstation with Linux and CS inside :-)

    Reply to this comment

  17. Ginkgo Says:
    April 9th, 2010 at 10:29 am

    Actually, what I really wish for is that Adobe had never bought Macromedia… Remember when Adobe actually built competing tools to Macromedia’s Flash development tools? (Though they were limited because Macromedia wouldn’t allow full scripting access because of it’s non-open nature.) Now we’re stuck without anybody to provide viable graphically orientated competitors, other than Microsoft (what does that say about the industry as a whole?).

    Just imagine if Adobe was releasing HTML Catalyst right now, to compete against Macromedia’s Flash tools, and Silverlight.

    Adobe HTML Catalyst would leverage HTML 5, Canvas, WebGL, local db storage and more, for state of the art web application development without the need for any proprietary plug-ins. It would help put even more pressure on Microsoft to get IE up to current standards support, and allow graphic designers to leverage the powers of Javascript libraries like JQuery.

    Combined with Adobe HTML Builder, providing an object-orientated suite of advanced components for developers to really take their web apps to the next level? Dreamweaver has too much baggage to really go there, in the same way that Flash CS 5 isn’t an optimal developer solution. The apps created with it would run on pretty much any machine, and targeted builds could be made for HTML app orientated devices like the Palm Pre, or even the iPhone.

    It would be awesome to see Adobe’s incredible talent pool develop such awesome apps… But Macromedia’s Flash has really taken over Adobe, and at this point Adobe’s employees seem more content to endlessly complain than push new web technologies forwards.

    Reply to this comment

  18. Benny Says:
    April 9th, 2010 at 10:36 am

    Start at schools and design agency startups. Give them free/cheap CS WINDOWS licenses. Allow students to use the license as a legible for upgrade after they leave their school.

    Collaborate with hardware manufactures and Microsoft to come up with a certified hardware setup that will run Adobe CS guaranteed and optimal on Windows and the certified hardware. Bundle Hardware, Windows and Adobe CS in a dream package for graphic professionals.

    Give the Windows version of the CS6 suite some advantages over the Mac version. For example 64 bit only on windows. New versions released 6 months later for the Mac.

    Or buy Apple?

    Reply to this comment

  19. Zachary Pinter Says:
    April 9th, 2010 at 10:47 am

    I’m obviously not a lawyer, but even if Adobe started “showing that the work flow includes a source code conversion from AS3 to one of the approved languages before compilation” it sounds like they’d still fail the new license agreement.

    It states that apps must *originally* “written in Objective-C, C, C++, or JavaScript.”

    What a truly horrible thing for a company to do. Apple has always been just as evil (if not moreso) as Microsoft has ever been. They finally gain power/leverage, and they’re already abusing it. Apple does much better as the underdog..

    Reply to this comment

  20. Kenny Says:
    April 9th, 2010 at 11:47 am

    1. Performance issue is a dead horse that people need to stop beating on. Hardware acceleration is key to Flash performance. According to Adobe, hardware acceleration is not supported under either Linux or Mac OS X, the latter because Mac OS X does not expose access to the required APIs. In layman’s terms: Apple isn’t allowing Flash to become more efficient on their Mac OS X/Safari platform (or their iPod/iPhone/iPad one, either) by not providing the access to the hardware it needs to reduce its CPU load.


    2. To blame the Flash Player on any memory issue you are having is like blaming the car for getting into a car crash. No you blame the driver, or in our case, the developer.

    3. Flash development is a career. iPhone development is a rush. If you are a Flash developer, there is no need to worry.

    4. Can someone sue Apple already? If MS pulled something like this someone would be all over them by now.

    Reply to this comment

    Darren Reply:

    I don’t think you can sue Apple – at some stage there might be some anti-trust/monopoly issues but currently Apple are not even the leader in the smartphone market (RIM is), let alone have a monopoly.

    Reply to this comment

  21. Edwin Says:
    April 9th, 2010 at 11:48 am

    Any developer with major investments in Python, Ruby, Java, C#, ActionScript, etc. and not Objective C has been told by Apple to F Off. Developers should return the favor and develop for platforms that treat them respectfully and not as punk ass serfs with Stockholm Syndrome.

    Reply to this comment

  22. Russ Says:
    April 9th, 2010 at 11:53 am

    @steve, really, if Adobe didn’t see this coming, then they deserve what they got. But I can’t image that is the case.

    Benny, I think your ideas are spot on, team up with MS, and do a huge push to the Education system. Not really sure why schools are so into macs anyway, since they are more expensive.

    Reply to this comment

  23. Paul Says:
    April 9th, 2010 at 12:25 pm

    It’s not only what Apple have done, but the malicious way in which they have done it.
    They have let developers believe that the CS5 iPhone/iPad packager would be permitted. The beta products have been allowed in the iTunes Store since the product was announced in October.
    It is the developers they show disrespect to, not just Adobe.
    If Microsoft had done this lawsuits would be flying by now!

    Reply to this comment

  24. David Schenk Says:
    April 9th, 2010 at 12:26 pm

    I think that Adobe can not engage in any act to hurt Apple. If Apple continues on they are only doing it to themselves. The act of Adobe trying to break Apple would reverse the rolls and Adobe would be the bad guy…. that wouldn’t be good either.

    What should happen is Adobe should support all the platforms that they possibly can but turn their attention away from iPhone/iPad to the other mobile devices and build them up. Not with the intention of crushing Apple but just to level the playing field. The minute Adobe gets too greedy everything will fall apart. When the rest of the market grows enough to affect Apple and they choose to allow Flash then Adobe need to leave the past in the past and do whatever it takes to mend the relationship.

    Apple may be the leader of that segment of the market for now but the rest of the market is catching up…and fast! When the rest of the industry gets up to speed then Apple may find that they have a corner of the market… just not “thee” corner.

    There isn’t a way to change Apple’s mind without doing from the user’s side…. developers are such a small percentage of the population compared to the user!

    I can’t imagine that with all the things Adobe is doing that they won’t find a way to show Objective-C, C, C++, or JavaScript or whatever code is necessary.

    Reply to this comment

  25. Bryan Bartow Says:
    April 9th, 2010 at 1:19 pm

    I sure as hell hope Adobe doesn’t pull OS X versions of their tools. I can’t stomach the thought of using Windows.

    Reply to this comment

  26. Fabianv Says:
    April 9th, 2010 at 1:45 pm

    What Adobe will do: Probably come up with some ingenious way of getting iPhone packager to work – such as converting AS3 to Objective C/C++ and having to then use XCode to compile

    What I selfishly want Adobe to do: Kill of OSX support

    What I think Adobe should do: Send out a clear message of disappointment about Apples TOS changes and show how awesome the Open Screen Project is working on other platforms

    Reply to this comment

  27. Adnan Doric Says:
    April 9th, 2010 at 1:46 pm

    Adobe can stop selling Photoshop for MacOS, Apple will be the big loser in that war, trust me on that.

    Apple = 1984

    I’ll just sell my iPhone and buy Android HTC Desire, I think I am too old to own such limited device.

    Imagine a second, we need to jailbreak the phone to actually use it as we want ? It is MY phone, I want to be able to do ANYTHING I WANT, simple.

    Bye Apple, enjoy your “open” standards.

    Reply to this comment

  28. scottm Says:
    April 9th, 2010 at 2:56 pm

    Few things:

    1. It’s not greed… Apple doesn’t gain from this in any direct financial way. If you want to distribute an iPhone/iPad app no matter what tool you use you still need to pay the $99 Developer price, beyond that the tools Apple offers are free.

    2. Ending CS support for Apple would likely backfire and translate into lost sales… The only tools not immediately replaceable are Photoshop and maybe Illustrator (and there are many tools that are close enough to fill that gap fairly quickly). Yes Apple would certainly loose sales if this happened too, but it would be desperate kamikaze move and investors would not appreciate it. Oh yea this would do nothing help the Flash, and would likely kill it off for good.

    I think the big beneath the surface thing here is that Apple, while not holding all the cards, certainly holds the best hand and they know it. You can debate this, disagree with this, hurl curses and threats, whatever, but that doesn’t change the facts on the ground.

    The truth is nobody (but developers) want a write once run anywhere world, because they soon find out that that means living with the lowest common denominator of everything, and most people want more.

    See here’s the real problem… Adobe has constantly been pushing the wrong aspects of Flash (the Video & Design aspects) so now Apple comes along and says… “hey we can do all of that with HTML5″ and everyone cheers (‘cuz everyone at one time or another have been thoroughly annoyed by Flash… the “Oops you need to update tot the latest version” warnings… the intrusive loud ads… the lazy designers that layout pages in flash and when you try to open a link in a new tab you can’t…etc). See most people think the death of Flash is a good thing. All the while Adobe should have been pushing Flash as a cool RIA platform… given up the trivial markets and pushing the things that just can’t be done on the web any other way. (Anyone remember They had this cool Flash app back in the day where you could set up your room with furniture offered… click buy and be charged 2x as much because of shipping… That App was amazing, and thing have gotten better, but nobody notices.) if Adobe showed only the cool useful stuff that can’t be done any other way, and that gained peoples mind share then Adobe could have won… I’m not to sure it not too late now though.

    Reply to this comment

    Rich Tretola Reply:

    To your first point, Apple would gain as it would force you to use Apple OSX tools to build your iPhone/IPad apps while with Adobe’s tools you could use Windows as your OS.

    I agree that ending support for OSX would kill Adobe’s profits but what other leverage do they have outside of PhotoShop?

    Reply to this comment

    scottm Reply:

    “but what other leverage do they have outside of PhotoShop?”

    None… that’s their problem. The only way to change things for Flash is to somehow show the Flash eco-system as a unique powerful RIA tool that can’t be replaced with open standards, and I’m not sure they can do this in a strong enough way quickly enough.

    Also in doing this they’ll irritate those designers to whom they sold Flash to as a cool video and design tool.

    Really this is a bit of Adobe karma that screws a lot of good developers in a process.

    A while ago Apple built a Flash runtime into QuickTime. They were “asked” to remove this…. Bad Apple-Flash karma (and a really good reason for Apple to hold a grudge given the state of Flash Player on the Mac).

    Adobe tried for years to figure out a way to beat Flash (with web standards… ironic.) They failed and ended up buying Macromedia to get Flash for themselves (hoping to leverage the 90% penetration rate into all sorts of of stuff). (Killing Freehand and competition at the same time). More Bad Karma.

    Reply to this comment

    Matt Perrin Reply:

    @rich I was under the impression that a legitimate Mac with an Intel processor (aka, no Hackintoshes) was required to digitally sign any application before you can submit it to Apple, even with the CS5 Packager utility. So you’ll still need a Mac Mini or something to publish the finished product even if you develop it on a Windows machine.

    Maybe Adobe needs to just roll with the punches and embrace HTML5. I haven’t looked into it at all yet (should probably get around to it soon). Wonder if you could hack that HTML5 Canvas element to act as a frame for Flash content / server side AS3.

    Reply to this comment

    Darren Reply:

    @scott, Apple gains because otherwise exisitng Flash developers would write their apps in Flash CS5 and they would work across PC, Android, iPhone, etc. In this scenario, Apple doesn’t have an app that is exclusive to their platform. Apple would rather you use their tools to write an iPhone app and afterwards consider spending the time to write the app for other platforms.

    Reply to this comment

  29. Another iBrick in the Apple Wall » Just Another Rant Says:
    April 9th, 2010 at 5:17 pm

    [...] are already a bunch of posts and commentary on the Apple SDK update prohibiting applications that link to [...]

  30. Friendly Tec Says:
    April 10th, 2010 at 1:14 pm

    You didn’t see this coming? Does adobe have the capacity, and desire to put flash on the Iphone? Yes. Does flash run on most other popular mobile divices? Yes. Why doesn’t flash run on iPhone? Apple.

    Reply to this comment

  31. Matthew Fabb Says:
    April 11th, 2010 at 2:26 pm

    Perhaps Adobe should just sue Apple? As many have pointed that this new licensing agreement breaks a ‘restraint of trade’ contract law. As it’s one thing to ban a technology on a device, but something completely different to ban tools to build something, when the end result is no different to the user. Where apps need to be decompiled and inspected at the byte code level to tell them apart.

    Reply to this comment

  32. Matt Perrin Says:
    April 12th, 2010 at 7:39 am


    Just saw this. Apparently there are abilities within Dreamweaver to embed converted Flash content into Canvas tags. Had no idea that was even possible. Fast forward the video to the 3:10 timestamp to see the extremely simple steps.

    Flash CS5 will export to HTML5 Canvas

    The animation looks fairly simple, and I loathe the Timeline, hope something similar is in FB4.

    Reply to this comment

  33. I’m with Adobe! | EverythingFlex: Flex & AIR Says:
    April 14th, 2010 at 8:32 am

    [...] The Apple is Really Rotten [...]

  34. Sasa Says:
    April 15th, 2010 at 1:30 am

    They will loose more than they gain if they pull their support from osx.
    after all who uses chrome except the very few among designers!
    Better if they find a way to work together for the benefit of all.

    Reply to this comment

  35. Guilhem Ensuque Says:
    April 21st, 2010 at 10:46 am

    > [Adobe should] make their packager compatible
    > with the new policies by showing that the work flow
    > includes a source code conversion from AS3
    > to one of the approved languages before compilation

    This is exactly what we do at OpenPlug: ELIPS Studio does generate C++ from AS3. Still, as some other commenters have said here, it remains to be seen whether this is enough for Apple. (full story here:

    What should Adobe do next ?

    Well here’s my take :
    1- open source the flash player to quell critics and share the evolution costs in an open way
    2- get involved in HTML5 implementations (e.g. webkit)
    3- focus on tools: Make Dreamweaver spit out HTML5/CSS3/JS for mobile web apps
    4- focus on tools: idem for Catalyst
    5- focus on tools: idem for Flash/Flex Builder + with native mappings for the unique features of each mobile platform
    6- Buy Palm (half kidding, just consider how all the others bundle their apps platform with mobile hardware: Microsoft / WindowsPhone7 phones, Google / NexusOne, Apple / iPhone)

    Further detailed in this blog article:

    Reply to this comment

  36. sEAN. Says:
    April 28th, 2010 at 10:23 am

    I’ve had to use Adobe products for the last decade. A happy day in my career was when I switched to Apple. Audition is ASS. Premier is ASS. Dreamweaver is is a joke. And the world can totally live without Flash.

    I’m reading all this whining about how evil Apple is…

    If Apple was a automobile manufacturer and Flash made carburetors, no one would blame Apple for putting fuel injectors in their cars instead of carbs. The people at the Flash Carburetor Factory would probably be bummed. I’d like to think they would whine about it as much has Adobe has.

    Reply to this comment

    Bob Taylor Reply:

    It makes me chuckle when I read comments like that. A tools a tool, and Flash is an extremely useful one. You can slander it all you like, but numbers are what counts, not the prattle of some minor developer having a “I’m right and you’re wrong” hissy fit :-)

    Reply to this comment

  37. Blue Says:
    April 30th, 2010 at 7:31 am

    I think the question is not what Adobe should do, but rather what Apple users being Adobe users at the same time should do – and I think they are HUUGE. There is an intersting Open letter to Steve Jobs:

    Maybe this is just the beginning.

    Reply to this comment