Home >
Anyone who's a fan of the iPhone and does interactive design, just clapped with a bit of internal excitement over the notion that Adobe just broke down the friction involved in producing an iPhone App via Adobe Tools.
There are some problems though, not just technical but market wise as well. Let's break this down into two parts.
First, Don't poke the sleeping giant.
A few folks have commented on how aggressive Adobe seems to be getting these days, like that kid named Jeremy in a Pearl Jam song. Okay, good, aggression breeds confidence, confidence breeds awareness, awareness breeds adoption. It's good to be confident that your product is the better choice, but be careful who you poke at especially when you need them more than they need you.
Adobe has spent a lot of cycles / years nudging Apple stating that Flash should be on the iPhone. Apple has firmly just said no, and despite the answer, Adobe keeps expecting them to cave due to public demand. The problem with this logic is that Apple won't. Apple is making money hand over fist on revenue based around the iPhone ecosystem. Not only are they generating profits, but they are breaking new ground in the market and future of how devices connect with consumers. As its the first time in history, carriers are lining up to pay Apple for the right to sell their product and promise to take a reduced profit margin in the process (which is scaring the heck out of all other mobile & pc brands).
Think about that for a second, Adobe created a separate team who's sole mission was to make their own product accommodate the iPhone since Apple wouldn't bend to their demands - ie Apple 2, Adobe 0.
If a few hundred thousand Flash fans are disappointed in Apple, it will actually make little difference to the above bottom lines - it's actually simply put, a rounding error. As you have to take a step back and realize, Apple iPhone is the same as Windows is to Microsoft. All gravity orbits around the iPhone now for Apple. Apple simply won't tolerate a threat to this business model from Adobe, Microsoft or even Google - be careful not to wake the sleeping giant.
Secondly, Just because it's easy, doesn't mean its successful.
Objective-C is a bit of a learning curve, and it as my father would say "separates the men from boys" as it's the difference between "I have a cool iPhone App idea" to "I have a cool iPhone App Idea, and I'm committed to making it" and it essentially ensures that those who finally make it to the AppStore publishing process did so because they really really really wanted it to happen.
If Adobe does come through with the promise that folks can produce Apps for the iPhone via basic common skills found in most Flash Developers today, great, but the problem here is that there are only so many Twitter, Flickr, iFart etc style apps you can be reproduced over and over. There are only so many basic line of business Web 2.0 apps you can produce.
It can invoke another gold rush into the Apple ecosystem, but is Apple ready for it? Is Apple going to be patient. Is Adobe actually going to deliver a quality approach here? If there is an inherent flaw or problem with the way it distills down to native code, it can potentially ruin a lot of peoples incomes or dreams fast.
Overall, going forward Adobe need to play this next round of Industry chess carefully, as Apple isn't easily bullied for one and secondly having lots of Apps in the appstore is fine, but right now the problem with the iPhone AppStore is there are too many applications (yes I said it, too many). Finding the next iFart solution isn't getting any easier, and it's resembling much like WordPress plugins today - 50 different ways to handle comments but no real killer solution.
I'm not convinced Adobe is going to pull this off in version 1.0. I think they are reacting to market conditions in a way that's historically been a bad position for them. They need to plan this one out carefully, ensure all the i's are dotted and the t's crossed. Telling people ahead of time before they are ready to ship is simply a marketing tactic to bolster interest around replenishing their CS5 sales given CS4 didn't yield a healthy scorecard.
The expectation bar has now been raised, Adobe's alliance with Apple needs to pickup lost ground, become positive and less aggressive and lastly they both need to find a way forward in stabilizing signal from noise when it comes to solutions for the iPhone.
Update: Please note, I no longer work for Microsoft, some folks in the comments are confused if this is a Microsoft endorsed post. Microsoft in no way shape or form have anything to do with what is written here or officially support this post.
Tag Cloud
Podcasts & Screencasts
@InsideRIA on Twitter
Follow InsideRIA on Twitter
Facebook Application Development
I simply don't understand why Adobe thinks "real web experience" means "Flash". That's rude, I understand Flash is almost everywhere on the web but even Google FInance does not make me think I need flash on my mobile.
Does Adobe really thinks all I need is automatically starting video ads on my phone?
@rad_g - If you think all that Flash is is automatically starting video ads, well then it's understandable why you don't think you need Flash on your phone. The Flash platform, enabled through the Flash player offers a wealth of application possibilities, from streaming to real time collaboration, data display and way more!
@Scott - I like how you assume that Flash on the iPhone means a ton of stupid applications. You like rad_g truly don't understand what Flash offers. You see iFart, I see rich experiences powered by the Flash Platform!
@Kevin Schmidt:
What else would you expect from a Microsoft Evangelist? ;)
Not much of an abundance mentality here. Remember, the cream rises to the top. "The internet" isn't a failure because of so much inferior content - the iPhone won't be either.
@rad_g:
I think it's just as rude to assume that Flash is only used for iFart apps and advertisements. Adobe has grown Flash into a platform for rich application development - and provided frameworks like Flex and its mobile companion Slider. This is a good thing and it's a natural evolution. Let's embrace it.
@Kevin, @Scot: No, I'm a flex developer myself but the last thing I want is flash on the phone. And let's face it, majority of flash on the web is stupid abs and pointless games.
@Kevin: Google Wave works on iphone, provides real-time collaboration and doesn't require flash. IMO the only thing that keeps flash alive is video.
To me the Flash CS5 -> iPA solution is less interesting than the fact that every other mobile system will soon support Flash. This can only be threatening to Apple as there's suddenly a much richer experience to users of these platforms (ads notwithstanding - they can be blocked). Of course Apple won't put flash on the iPhone, as it is a competing application platform. But I for one have no interest in what the iPhone has to offer - the Web without Flash. And I'm sure I'm not alone... time will tell.
Uhm...the Pearl Jam song "Jeremy" is not about a kid who got overly aggressive. It is a about a very real 16 year old boy named Jeremy Wade Delle who shot himself in the head with a 365 magnum in front of his high school class back in the 90's. You may want to re-think that comparison in your intro.
Doesn't Microsoft/Novell's Monotouch project do exactly the same thing? Silverlight compiles to iPhone native bytecode though the Mono SDK. Adobe is not the only one trying to break into the iPhone app market.
@rad_g:
Let's not get confused and think that Adobe has gotten the Flash Player on the iPhone because it hasn't. What's happening here is that CS5 compiles to an actual iPhone app, not a swf. So right now you don't need to worry about Flash being on your phone.
Unity3D also compiles for the iPhone, so what is the big fuss about Adobe it also. What is the sleeping giant going to do, block all those apps; that's already what they are doing, you can't blame Adobe for trying something.
Sorry but Scott Barnes is completely the wrong person to be writing such an article. Whether or not he has valid points is overtaken by his bias, and to be honest I thought the arguments here were pretty weak - just an excuse to take yet another cheap shot at a competitor. 2-0 to Apple? Oh grow up Scott. You'd rather see Adobe mope around and do nothing than be pro-active now wouldn't you. It's understandable why Apple don't want Flash on the iPhone, it's understandable why Adobe want to allow Flash developers to publish iphone apps and I wouldn't be surprised if Microsoft follows Aobde's lead on this one in the future.
Unfortunately Scott Barnes does as much harm for Microsoft as Ted Patrick does for Adobe. Both are incapable of having a balanced argument, they have an agenda to push and often resort to acting like bickering children. Can we please return to the quality articles from insiderRIA that we are used to. Anti-Flash articles are fine as long as they have substance. This one doesn't.
"The Flash platform, enabled through the Flash player offers a wealth of application possibilities, from streaming to real time collaboration, data display and way more!"
You say that as though Flash is the only way to do all that stuff, but it isn't. Likewise, Flash isn't the only way to create a rich user experience. Adobe seem to be trying hard to make that phrase synonymous with Flash (can't blame them).
Personally, I don't care about Flash on iPhone as I'm an Android fan. I am worried about it coming to Android though, as I am very sceptical that the Flash Player will both perform well on my phone and not leave it drained of battery in a couple of hours. However, I'm hearing great things about FP10.1 so I'll give it a go.
@rad_g
When someone says "the real internet" that includes a multitude of plug-ins. Flash, Silverlight, Java, Java FX, etc etc. If any 1 of these plug-ins is not allowed - the "real" internet is not being offered. This is Apples marketing snafu. They claim real internet, but don't offer it. Its not just because Flash isn't on there.
Also, Android phones are hitting almost every major manufacturer next year, or so sources say. Once the market is saturated with another option that works, and allows Flash, Apple may be forced to change their policy, lest they lose too much market share.
I for one want an iPhone, but I will wait until I'm not tied to a specific network, and I can get the REAL internet on it. And, if something better comes along, I will go that route. So far, I see myself on Verizon with an Android phone sooner than I'll ever have my hands on the iPhone.
I really don't see how this will screw up Apple's app store. Yes, a lot of developers see Apple's app store as a potential gold mine and a lot of developers will attempt to write apps with CS5 and try to sell them. Apple will in turn have to deal with the influx and will probably come up with some new rules for the approval process. I don't see this as a bad thing because Apple has the power to do what it wants and they WILL do whatever they want to deal with it.
However, anybody with some insight will see that its not just about the iPhone anymore. The iPhone represents approximately 40% of the mobile OS share right now. Yeah, thats quite impressive, but its still less than half and other mobile operating systems are gaining ground by the day. Adobe has nothing to worry about so long as they continue their efforts to get the Flash Player on as many devices as possible. And not just mobile phones. TV's, set top boxes, netbooks, etc. So imagine once Flash Player 10.1 becomes widely available. As a Flash developer that excites me more than the idea of being able to publish my project to an iPhone app. The iPhone isn't the end all of mobile development.
After the "experience" with Flash on my MacBook — intrusive ads, computer getting hot, fans spinning up, and so forth — I installed a Flash blocker. What is Adoobie smoking, that makes them think I want Flash anywhere near my iPhone? All Flash would do is annoy me, get the phone hot, and suck the battery down far too quickly.
If Adobe's actually compiling Flash to native code, that might be OK (have to take it case-by-case). But anything coming from Adobe these days has to be assumed guilty until proven innocent (PS Elements has successfully passed this hurdle).
rad_g, according to Adobe, they get 3 million iPhone users going to Adobe's Flash Player install page every month. Clearly there are a lot of users who want this functionality and don't understand why it's not available. So Adobe isn't being rude, but responding to consumer demand beyond the demands of their developers. I imagine that similar to desktop browsers that the minority who don't want Flash Player on their mobile phones can disable them.
It will be interesting to see if once Flash is available on all the other mobile phones except for the iPhone if it will effect the bottom line. I doubt there's that many Flash fans out there among the general public, but if smartphone company advertises that their phone reaches Hulu, all of YouTube, not just a small percentage of videos and other popular Flash websites, then it could have an effect on the bottom line for the iPhone and the Touch.
As for Adobe hurting the iPhone app store, even without Adobe increasing the market there's an issue with the iPhone app store. Apple needs to deal with it with either increasing quality control or provider better filtering and sorting of the applications within the apps store. Perhaps Adobe moving into the market will cause Apple to finally do something about this issue.
Hum... I think you are taking the wrong approach here Mr. Barnes... and I think your background (http://www.oreillynet.com/pub/au/3911 - "former Rich Platforms Product Manager (Silverlight/WPF) and first RIA Evangelist for Microsoft...") is taking away your objectivity here.
The best advantage with Adobe doing this is the fact that a developer can build an app using AS3 and package it for the iPhone, then modify slightly to eventually release for WebOS and Android (via Flash Player 10.1), not to mention as an AIR or Web application. This is HUGE! AS3 truly becomes a ubiquitous development platform.
Oh dear. Scott, you are doing yourself no favors writing articles such as this one - biased from end to end, which I guess is to be expected.
I would like to point out since I have seen it within a few comments that Scott is no longer a Microsoft employee.
Such a huge amount of doubled comments on this website should make insideria team think there is something wrong with commenting here.
I didn't read all of the comments but you guys do know Scott is no longer with Microsoft, right? Look beyond who he is/was and see the points for what they are. For instance, if a crackhead tells you not to do crack for reason x, y, z, does that mean it is valid info because they are on crack themselves? Nope, info is still valid. To clarify, I'm NOT comparing Scott to a crackhead. lol.
Scott and I have disagreed on many days but not today. He hit on points I've been meaning to blog about as well.
1) Adobe should not pick a fight. I like the bold stand but taking cheap jabs could ultimately hurt.
2) Apple has no reason to put full Flash (app dev + browser plugin) on the iPhone. They already have a developer story and so far it is a "good" one (financially at least).
3) Flash would cut into Apple's revenue with wildly available Flash apps downloaded from anywhere for any price excluding Apple's "minor" fee (30%). They like commerce but not without their hand in the pot.
Bottom line is Scott has valid points and the article isn't anti-Flash. Not all points are 100% agreeable but the write-off the entire article as bad is a bit odd.
A few counter points if I may - assuming the folks who commented are still reading.
I left Microsoft
I choose to leave for a number of reasons, one of which was that I was no longer just "Scott", as the brand itself was defining who I am. It's good to stop, reflect and make changes in ones career and I left to carve out my own free thinking opinions on how the RIA industry is looking to head in the next 5 years. I'd like to have my seat on the citizen's of RIA floor and not so much in the thick of the brand itself. I turned down offers from other parties who compete with Microsoft to prove that point.
Am I qualified
Part of my role inside Microsoft was to decode what our competitors, namely Adobes movements are likely to be and what potential SWOT would look like. I've got approx a 90% success rate so far in doing this, so whilst some may disagree with the opinions (which is perfectly valid) one of the largest corporations in the world, valued my insights here. It's up to you in the end how you choose to digest this and this piece really doesn't help Microsoft one way or another.
Does this mean you hate kittens & Adobe+iPhone
Let's be clear, this is a cautionary post not a left or right sided post. The purpose of this piece is to invoke a different perspective on the situation firstly and secondly step back, put the brand partisan politics aside and analyze this from a risk perspective. In that, what is the likelihood of Adobe gaining success here? what are the consequences of Adobe's success here? and so on.
As for Jeremy's song
I picked it for a number of reasons, firstly, it invokes that "unleashing the lion" is something one should always be wary of. Secondly Vedder explains that "..The best revenge is to live on and prove yourself. Be stronger than those people. And then you can come back.." I think it's fitting here.
It creates conversation
You're all talking about the impact here. That in itself is important, that's what blogging at times is about, invoking change and conversation.
Historically, Adobe are good at dropping buzz pellets, now comes the point in time where they really need to be careful where they lead the overall RIA community here.
-
Scott Barnes
UX Specialist.
Few comments - firstly, it's easy to cut Apple's revenue out of the picture on the iPhone - give your app away for free, just as - currently - Flash applications are. Or you can develop a web app.
I would presume that Adobe/Open Screen will be looking at closing that gap, and having some kind of platform app store, similar to the Android and JavaFX ones, but I don't think this is exclusively a revenue control story.
Without that, then Flash apps are going to be purely restricted to current freeware revenue streams.
As regards AS3 as a ubiquitous development platform - the problem here is the same with all ubiquitous platforms - as a developer you are ignoring the question - 'why has the user chosen platform A over platform B?'.
It does strike me that a lot of time Flash designers relish the ability to 'go wild' and create their own widgets and look and feel, not understanding the advantages that come from a consistent UI between applications. The iPhone and Android already demonstrate variances in behaviour.
Don't get me wrong - we use Flash / Flex heavily in our development, but the main reason we do it is that we have to - because it upgrades IE. And it does make me question anyone who would code in Flash by choice (again, with all due respect to people who've done things like create Spectrum emulators in AS3 - there are really good coders working in the Flash area - but again, it's notable a lot of them have backgrounds in C/C++).
The errors in this story are numerous. The view point is fatuous.
1. Adobe, not Apple, is responsible for creating Flash plugins. It always has been true on other systems.
2. Apple doesn't want Flash, because it is old, proprietary technology and a resource hog. Apple would rather use HTML5, instead. HTLM5 leaves Flash behind. Adobe tools will not change that.
3. Flash is not a threat to Apple. Nor is a new version of it. Nor is Adobe tools.
4. Apple is not being a monopolist when it keeps cr*p off its ecosystem.
5. Apple doesn't need Adobe much any more. There are many substitutes for Adobe software. Adobe is just another third party developer. In the past, Adobe used its muscle to coerce Apple. Those days are long gone. Adobe needs to adjust to the new reality.
What I don't understand is why people keep saying Flash on the iPhone. Flash Pro is the PROGRAM used to create the iPhone app. Flash on the iPhone would mean a .SWF file running. THIS IS NOT HAPPENING.
Flash Pro is transforming your code and graphics into NATIVE code. Adobe is providing a tool that allows an AS3 dev to compile down to iPhone.
This means that I can write 1 program and deploy it over all kinds of systems with MINOR changes to my code; all in the same language.
Ex-MS employee or whatever, I assume this was in that 10% of your predictions that you didn't get right? *shrug* I'm a huge fan of being able to do a bunch of things with 1 set of tools.
This article does not deserve to be on this site.
Scott Barnes, whether intentional or not, just insulted a large number of the people this site is supposed to cater to, Flash developers. First there's the insult that AS3 development is a common skill that does not measure up to Objective-C development and then that Flash is only good for apps equal with the level of iFart. We should be beyond this "my outrageously cool development platform of choice" is better than your "crappy platform that only children use" arguments we see in what should be a mature industry. People should just grow up.
You Apple people should get off your soap box and understand that Flash will not be installed on your precious device. Even if it was the actual plugin you could simply choose not to install it. Just because you don't want it doesn't give you the right to demand that no one should have it. And if somehow you are forced to install it you can blame your beloved Apple for it and not Adobe.
Adobe should be careful not to awaken the sleeping giant of Apple? What does that mean anyway? Why should Apple care about this development method? It increases the number of developers for the mobile platform that they control without costing them a dime. They should be rejoicing because up till now they had a point about Flash on the iPhone, it was too much of a resource hog. Now, it no longer matters. Plus all those Flash developers will still have to jump through Apple's hoops to get published. It's a win for both Adobe and Apple. I don't see what the problem is.
The app store will be swamped with crappy apps just because of Flash CS5? I say that's already happened with the near-perfect Objective-C that only awesome developers are smart enough to code. What language was iFart developed in anyway?
And all you Flash haters that think HTML5 will be the joyous Flash killer you've been waiting for? I've got news for you. HTML5 is a long way off before being a dominant standard. Plus all the features you hate about Flash (even Silverlight) is going into HTML5. Copying features from Flash/Silverlight is what makes HTML5 superior to those platforms? How does that work exactly? I say, sometime in the future, we all will have extensions to block crappy ads in canvas tags and bandwidth hogging video ads in video tags. You just wait.
Wow! talk about opening a can of worms.
I usually don't comment on articles like this but I'm tired of the attitude towards Flash developers.
First off I personally don't see Adobe bullying anyone here, they saw a need and decided to provide a solution. Whether or not you choose to use that solution is up to you, whether or not Apple allows that application into the iTunes store is up to Apple.
Secondly I take offense to the quote "separates the men from boys" ?? This is such a bull@#$% statement.
Why even include such a one sided statement. This attitude seems to be a common theme amongst a lot of developers towards those that choose a different technology other than their personal preference. This somehow implies that if your not using a particular technology that your not a "real" developer.
I've developed with Microsoft technologies, open source technologies and Flash based solutions and I can assure you I am very committed to developing the best applications for my clients and not everything was easy but yes some of the approaches were easy because I followed in the footsteps of others who labored to make it easier for me, i.e. design patterns. If you develop in Silverlight, Objective-C or whatever, great more power to you but please don't be condescending to me because I'm a Flex or Flash developer.
Yikes,
To clarify a bit further. I'm not disregarding the folks who can produce quality solutions in Flash (I can see how folks can derive that implication, but let me set the record straight#, My thought process in this piece was referring to those who are starting out in the Flash meets iPhone space, and historically speaking, Adobe Flash folks have in the past pumped out stream after stream of Twitter style apps as they grok the overall learning curve associated to the technology upgrades. It's natural and * all brands * go through this phase of adoption life cycle.
Adobe aren't bully head on, but they are taking a passive aggressive approach to the problem - which is a form of social psychological manipulation "aka bullying". They want in on the iPhone as that essentially firms up their Open Screen Project initiative. They of course do not like to be questioned publically "hence a lot of their staffers denouncing this post using the swarm/smear/smother technique). The reality is that they've not really been given permission to enter into this space, and as a result they'll need to work with caution here as Apple hold the cards and they could in turn pollute the ecosystem for other "x-native compilers" as well.
I develop personally in around 9 languages, out of all my favorite technologies ever, I'd still say Delphi was the most fun.
HTH.
--
Scott Barnes
UX Specialist
@Louis Wheeler I couldn't really hear what you were saying with Steve Jobs balls in your mouth. Would you care to remove them and try again?
Scott, even with your clarification, your argument is still spurious. You haven't adequately explained why Adobe would need to seek permission to create a *developer tool* to produce software for a particular device. Apple can reject apps based on their quality but why do you think they have an inherent right to control how they are created? To even imply this suggests some form of satellite-based brainwashing by Apple ;)
P.S. Adobe are not being aggressive but totally consistent with their own philosophy here. After all, they have published the SWF spec and do not restrict any company making devleoper tools that compile to SWF, nor do they restrict anyone from making their own SWF player (in fact they encourage them to do so through the Open Screen Project).
Darren,
I fail to see your logic here? (sorry) I simply stated that bypassing Apple's and approaching it from a different route, actually can directly compete against Apple head on. Look at it from Apple's position.
Adobe could potentially poison the well without realizing it. As if Apple even for one moment considers the concept to be a open threat, they'll simply make moves to shut it down - and they will do it fast and abruptly. This in turn can put other projects like MonoTouch for example in the same mix, so it's not a good idea to keep poking Apple in the chest with their immature behavior is my point. i.e. don't poke the sleeping giant.
Adobe is also an open threat to Apple, as putting Flash+ features on all devices as per the Open Screen Project, simply empowers device OEM manufacturers a faster inroad into competing against iPhone(s). This is also a rational reason why Apple should actually halt the Adobe pipeline when it comes to opening their borders towards Flash Tools. Adobe have made it loud and clear that they want to be the UX platform for screens all shapes and sizes, I can't see Apple warming up to that concept any time soon. Again, don't poke the giant at this stage in the game, wait a few more releases, get everyone attached to it - then bring it out the big plays.
Secondly, ensure that when the tools are released they allow more functionality than baking basic Apps - as then you have the Twitter/iFart model on repeat (simply due to a reduced SDK model). Historically speaking, Adobe haven't really come to the V1 table with all their I's dotted and T's crossed - Adobe AIR was a very weak release. This is in part the problem, and its why the certain Evangelists for example will circle the wagons and protect the concept, without thinking it through.
It's not saying a x-compiler from Adobe is a bad idea, it's not, what I am saying is be careful, be humble and instead of clinching thine fist, leave it open towards Apple. They said no to Flash for obvious reasons (it directly competes with their business), Adobe's found another loop hole to come in under, great, be careful as with power comes responsibility.
HTH.
Scott Barnes
UX Specialist
If you create an IPhone app through Flash you do not have access to the core libraries, so you are going to be limited by what you can create anyway. It will just be a quick way to create games for the IPhone in my opinion.
What an adorable little article. Once you get past the hearty riddling of English errors, you can really start to enjoy the equally spectacular legion of skews and squints in its perspective.
I was literally embarrassed for you reading this article ( and some of your follow up comments ). It must be hard to see the world clearly through the vertical space between Apple's sleeping, giant, inner thighs.
But anyway, congratulations Scottie Barnes. You've just earned yourself a prime spot on the "most embarrassingly misinformed techwriters on the net" wall of shame at http://thetruthaboutapple.com/ when it launches. I'll be in touch to get higher resolution headshots.
I also wanted to congratulate you on being one of the few catalysts of my actually removing a site from my bookmarks. G'night InsideRIA. It was fun while it lasted.
"Adobe AIR was a very weak release" ... woh! Word of advice, when you're in a hole its best to stop digging. AIR 1.0 was a 1.0 release and has gone from strength to strength - the power it gives Actionscript developers to write cross-platform desktop apps means it is now a serious choice over traditional Microsoft tools. You may no longer be a direct employee of Microsoft but it certainly appears that your brand loyalty and bias hasn't really changed. Yes, the CS5 -> iPhone-native announcement has opened a can of worms, and a lot of the negative comment is coming from inside the Flash developer community. Having seen an early alpha example, bloggers are already assuming the finished product is going to be hobbled in some way. Let's cut Adobe a bit of slack and wait til the finished product arrives. You think they are going to fail, and apparently you are 90% right at predicting the future. That is just plain arrogance. It seems unlikely to me that their showstopping announcement at Max will turn out to be a lame release - the negative publicity and sentiment would be a spectacular own goal, so lets credit Adobe with a bit of intelligence and assume they'll only release this if it is a winner. Your "dont poke the sleeping giant" assertion makes no sense either. All Adobe are seeking to do is to provide a way of porting an application to as many platforms as possible, how is that attacking Apple's revenue stream? - If you have written an enterprise RIA in Flex that includes mobile devices, why should you have to have to write and maintain a totally seperate codebase for the iPhone? Surely its just good software engineering principles at work here.
hey, every guy, Adobe , as a solution provider , they just want to meets the developer's needs,Whether or not you choose to use that solution is up to you, whether or not Apple allows that application into the iTunes store is up to Apple.
Anyone know how well Flash runs on other mobile phones?
Its a very expensive way of doing animated graphics. I doubt its going to perform well compared to native apps.. People tend to take-for-granted how powerful their desktop PCs are compared to a smart phone.