Category Archives: Iphone

The big news out of Adobe MAX 2009 last week was all about mobile and the developments for the Flash platform on devices, the forthcoming release of Flash Player 10.1 and of course the announcement that Flash CS5 will be able to publish Flash files as native iPhone applications!

Flash on the iPhone

Here’s how they broke the news:

It’s a huge announcement.

Rumours of Flash running on the iPhone have been going around for over a year now, with Adobe and Apple ‘officially’ being in talks since November. The Flash team did well to bluff any developments when asked about it at Flash on the Beach this year, so clearly they were keen to save the big reveal for MAX as it deserves.

As you can see in the video, Flash CS5 will make it super-easy for developers to publish their Flash applications as a native iPhone executable, so simply it would seem, as changing a publishing setting at author-time.

This means developers don’t need to make any changes to their applications in order to run them on the iPhone (though presumably the APIs will be limited). It also means that existing applications won’t need to be rebuild from scratch (not even be completely refactored, as before) and can be distributed via the AppStore.

It doesn’t, however, have effect on viewing Flash in the Safari browser. This still cannot be done.

What Adobe have achieved is the ability to compile Flash as an iPhone executable to run as a native application – they haven’t created a Flash Player for the iPhone, or any way for the iPhone to interpret a SWF at run-time. They’ve made their files compatible, rather than the other way round.

There’s already some applications available in the AppStore, these are:

 
Adobe have created an Applications for iPhone Labs page demonstrating apps running on the phone:

Flash iPhone demonstration

There’s also an FAQ (and Developer FAQ) which goes through what can and can’t be done.

Mark Doherty has written about the announcement and lists some of the limitations that will be imposed, for example some typical features you might expect to work with, but won’t be available:

  • Microphone access
  • Camera access
  • Photo selection from file system
  • Contact selection from the address book
  • Cut/copy/paste
  • Maps

 
..actually quite a few limitations.

Ted Patrick is one of the Adobe team who developed some of the demo applications. He has posted an article on his blog with the four sample apps and included full source so you can see, as he says, there’s absolutely nothing special going on – it’s just simple AS3 cross-compiled to iPhone ARM Binaries.

Aditya Bansod has written an article for the Adobe Developer Connection which goes in the technicalities in a little more depth. He also has an hour-long episode on Adobe TV, taken from MAX, exploring the technologies:

Of course, it’s not news that Flash isn’t without sceptics. Not everyone is looking forward to the prospect.

Jeff Lamarche is an iPhone developer who has some very good points on being cautious when developing Flash for the iPhone.

He shares my opinion that you should avoid ‘hammer development’ principles and instead should choose the best tools for a platform. He says:

Flash has always been a compromise that takes considerable overhead to let you create applications that can run on multiple platforms, while feeling native on none and getting native performance on none.

He goes on to make valid points about performance when road-testing some of the applications, also noticing some inefficiencies and possible breaches of Apple’s guidelines.

Presumably when you create applications with the recommended workflow, with XCode, Interface builder and the iPhone SDK, developers are somewhat constrained by them – definitely with regard to the interface, visual components and interactivity. With Flash’s ‘back-door’ sneak of creating apps, these may be breached.

That being said, I haven’t had a chance to play with these applications yet (I don’t actually have an iPhone..) but even then, presumably these are apps for demonstration and are, as proven, purposely uncomplicated.

And as always Flash has its haters.

A comment on Mike Chambers’ post might be a bit knee-jerk and unjustified, but also hints as to some of the feelings that will no doubt surface if the AppStore is inundated with bad Flash apps and games.

Hopefully Apple won’t change their position on accepting Flash.

Flash on everything else

But not to forget – this was really the second big announcement of MAX.

The first announced that the forthcoming Flash Player 10.1 appears to run on pretty much every other smartphone and high-end mobile device on the market too. Which has a lot to do with new commitments to the Open Screen Project.

Ryan Stewart has a run-down of the news, which announces Flash will run on Blackberry, Palm Pre, Windows Mobile, Android and on Skyfire browser for Nokia Symbian OS (links via InsideRIA).

Google have joined the project, see the post on their blog and Adobe’s press release for more information.

At Flash on the Beach, Mark Doherty’s spoke about the improvements to Flash Lite and how advances in Flash technology outside of the ‘main’ Flash Player have beneficial effects overall, to the platform as a whole. One such advancement is that the new multi-touch and gestural events in Flash 10.1 will be completely available for non-mobile applications too.

Daniel Dura and Matt Bugbee‘s Multi-touch and the Flash Platform on Adobe TV discuss and demonstrate what can be achieved with these new events.

I’ve just noticed that InsideRIA already have a ‘Getting started’ primer for multi-touch Flash, too.

As I say, advances in one technology can propagate development in another. That said, Adobe have also announced that they are developing a lightweight Flex framework for mobile devices, called Slider.

Slider is a mobile-optimized version of the Flex 4 framework, allowing developers to leverage their existing Flex skills but benefit from optimised performance and a streamlined user experience for devices with less memory and slower processors.

There will also be a new set of user interface components.

Going full circle, a greater presence of Flash and Flex on mobile devices puts more pressure on Apple to adopt the Flash player for their Safari browser.

Hopefully some time soon, seeing this screen will be a thing of the past:

As Serge says, there’s lots of things to get excited about and it’s a great time to be a Flash Platform developer!

Update: I’ve now written up my thoughts on Day Two and Day Three.

Now in its fourth year, Flash on the Beach has quickly grown in to one of the most popular Web conferences in Europe. This week hundreds of developers, designers, gamers and animators (you name it) have arrived in Brighton to see and hear the latest news and innovations in the Flash world. I’m here and until Wednesday, trying to get to the best of the packed schedule.

Flash on the Beach 2009

Keynote

Richard Galvan and Mark Anders

The conference opened with a keynote from Adobe’s Richard Galvan (product manager for Flash Professional) and Marc Anders (Senior Principal Scientist).

They started with the usual kind of Flash Player boasting, statistics, looking at the penetration and speedy uptake of the past versions for the last view years and looked over some of the feature successes of 2009 before outlining what we can expect in the near future.

Of those success stories they particularly highlighted the prevalence of 3D, the perspective API in particular and the new drawing API. With both, celebrating the growing power of the Flash platform in their ability to handle these developments as they’ve promised years previously.

They talked about the forthcoming release of Adobe AIR 2.0, demonstrating some of the popular applications that have surfaced this year in TweetDeck and Fanbase.

Elsewhere on the Flash player, the new text rendering engine looks impressive. The forthcoming update easily renders ‘print quality’ text in any reading direction – not only bi-directional right to left, but supporting languages such as Thai, Hebrew, Arabic and Asian languages horizontally and vertically.

We had a sneak preview of what else is to come in the CS4 update. Inclusive of the above text advances; authors will have a far greater amount of control over editable properties, more toward the likes you would find in Photoshop (kerning, ligatures, etc) as well as the TLF (Text Layout Framework) improvements which can link multiple text fields like columns, as to what we’re more familiar with in Adobe Illustrator.

There’s a keen initiative to make life easier for newcomers to Flash – and designers ;) .

For example, there are now a number of code snippets bundled with the Flash IDE which, whilst not being anything brand new at all for most workflows, has been lacking in Flash for some time. These will beparticularly beneficial for those experiencing migrations problems from Actionscript 2.0.

Alongside those, the code IDE also has both auto-completion and code introspection for custom classes.

As has always been Adobe’s intention, there’s a continuation of tightening the integration of programs across the Creative Suite.

Flash Professional and Flash Builder (the renamed Flex Builder) have a partnered workflow between coding and design environments. Documents can be created within the Flash IDE and a document class be generated and automatically be launched within Flash Builder. Flash Builder in turn has compile and debug shortcuts via the toolbar to switch back and forth with Flash thereafter.

The keynote concluded with Mark Doherty joining Richard and Mark on stage to demonstrate some of their developments with mobile devices. Showing Flash running (almost) natively on a few mobile devices and even promised their first television platform support – though poor cabling let down the demonstration.

Advanced Desktop Development with Adobe AIR

Mike Chambers

The first talk proper I attended was with Mike Chambers exploring some advanced techniques with Adobe AIR. Since it’s release 18-odd months ago, there’s been plenty of entry-level talks and tutorials at conferences I’ve attended, so I was looking forward to a more advanced demonstration.

Mike went through some of his contributions to the AS3corelib, a must-have library of tools that came around last year.

The first was the FileMonitor, straightforward enough, is a handler class for monitoring changes to a file on the system marked for observation. The class dispatches events on modification and movement (or if it is deleted) by polling the file regularly and, basically, looking for changes to the last modified date. Mike noted that this class and the VolumeMonitor, which he demonstrated next, essentially facilitate what AIR natively ‘cannot’ really do. They’re not particularly hacks, but workarounds until the runtime supports these functions natively.

Mike also talked about the AIR 2.0 release, that as well as having the performance improvements you’d expect, checks off a few of the most popular feature requests, which was one of Adobe’s highest priorities.

He demonstrated the StorageVolume API, which monitors for USB mounted hard drives. He recorded a video with a flip camera and handled the file transfer within an AIR application which detected it’s mounting and read the file contents.

This really made AIR look like it could eventually be a very powerful desktop runtime (and already it’s pretty damn good as it is). But with it’s seamless connection with the hardware devices and by seeing it confidently carry out the kind of tasks you’d expect more traditional proprietary software to perform was really something.

Likewise, Mike showed some examples of storing persistent data for applications by creating custom file types. He also utilised the application cache, by way of the ResouceCache class, to optimise processing. This of course also allows you to access these kinds of assets whilst offline, which after all is half the deal with AIR. It too really made AIR look like a far more serious, or at least a more mature platform than it’s young age may otherwise suggest.

Finally he talked about forthcoming changes to running native processes and applications – and this is a huge deal.

I’m sure this is would have been the most requested feature by far – that AIR should be able to launch files in their native apps and run other applications or processes securely from within it’s own runtime.

Mike was the developer of the CommandProxy, a proof-of-concept bridge between AIR and the OS by way of a secondary application (running in the background), but this development now makes that obsolete. This would be able to talk to other applications the correct way, whether that application is something like Photoshop or a command line process.

Apparently though, if you do use this functionality, you can no longer distribute your applications as an .AIR file. Although your app will still be completely cross-platform (this is important to Adobe, he says) you’ll have to export as the platform-specific executable – so a DMG or EXE file, for example – though handy as it is, the compiler will produce these for you :) .

Mike has now uploaded his notes to his blog here.

HelloEnjoy

Carlos Ulloa

Next up was Carlos Ulloa who discussed a selection of his latest work for his studio HelloEnjoy. Founder of Papervision3D, Carlos (as ever) didn’t fail to impress.

The first project was ‘Flowers’, a very intricate visualiser and editor for forms of artistic models of abstract 3D flowers. Whilst offering a very simple interface to manipulate the characteristics of the flower – shape, size, colours, in real-time – it hid some extremely complex mathematics and transformations behind-the-scenes.

Carlos took us through how the project was conceptualised and ultimately built, referring to some of the libraries he used along the way – Flint particles being one of them, as well as the excellent GouraudMaterials for shading.

Secondly he demonstrated EnergyLab – a relatively straightforward game mechanic, but executed to the highest levels of workmanship and attention to detail that I’ve probably ever seen in such an application.

Having visited the site before and being impressed enough simply by the experience it offered (it deservedly won a FWA, too), I hadn’t truely realised how much work had gone into the development of the project – particularly the 3D work more in the combination of Papervision and Maya, than the video production which is arguably more striking.

Carlos went through an extremely complex and lengthy process to achieve the desired visual results requested by the client, who pretty much came to them with a video full of CGI and asked “Can you do that?”. It’s exemplary of the powerful effects that can be created in Flash as boasted in the keynote.

Working in parallel with Papervision and Maya, for weeks scrutinising every detail of the project it would seem, it’s as much also a remarkable achievement of workflow and process. I don’t think that playing the game really represents this.

Finally we saw walkthroughs of HelloRacer, an iPhone application developed with Unity 3D in just a week (the online version of which can be seen on Carlos’ blog), and the popular HelloEnjoy website – newly improved with extra models and sound. By this point most people were already pretty blown away, Carlos made this look relatively simple - he sets a high bar.

Adobe Town Hall

Adobe Flash Platform team

This session was a face-to-face Q&A between the leaders of the Flash platform and the community at large, an open-mic style meeting allowing anybody to fire any questions they had.

The team was Richard Galvan, Mark Anders, Paul Burnett, Andrew Shorten, Mark Doherty and Lee Brimelow.

Most questions related generally to workflow, feature requests or concerns over software bugs, with the odd teething problem with CS4 thrown in. However a few points are worth nothing outrigh.

For one, the panel were asked about threading and whether there are any plans to support some kind of threading in the Flash Player (ever, at all). I thought this would produce an outright “no”, but it seems it is something that they’re considering. No doubt due to the high amount of requests. They said, whilst threading is very hard to achieve and in no-way present in any form natively for the player right now, they’ve looked at other methods of running concurrent tasks seen elsewhere with the likes of HTML5 or Grand Central Dispatch, to facilitate something similar. So although there is a definite interest, what we might eventually see may not necessarily be ‘threading’, per se.

Another (perhaps inevitable) question asked for any update on the status of Flash for the iPhone – both for support in the Safari browser as well as potential to run applications natively on the platform. Disappointingly, there is none. This was an outright blank – although of course, it’s still a target. Adobe will demonstrate Flash Player 10 to the best of its ability at Adobe MAX 2009, but other that that, there’s no new plans. It was actually at FOTB last year that the first announcements were made.

Thirdly Flash Media Server got a mention, FMS is something I have a bit of a soft spot for. The question was asked as to whether it will ever support AS3 – currently it’s a cheap version of AS1, which is basically Javascript. Though unfortunately here too, they had no news to offer – more to do with the fact that none of these guys work on the platform personally, so they couldn’t offer anything. But it was said that the platform is still being developed though, and it’s probably just ‘a matter of time’.

Finally there was a quick conversation about the ‘headless’ Flash player, a distribution for search engines to allow indexing of Flash-based content (SWF files). I wrote about this when it was announced, but it sounds as if it might now be released again but for developers to play with – for the same reasons and SEO purposes so we can see how it works inside-out, but also as a tool that could be used for the likes of automated testing, or anything else that we might be able to come up with.

Another note taken from the session actually, it seems that Flash on the Beach is unfortunately ‘too close to MAX’, as I heard on multiple occasions. Adobe are obviously holding back from secrets for MAX, fair enough, but it was disappointing to hear this said a few times to the crowd of eager community members who’ve paid their hundreds of pounds for their tickets.

Cybernetic Art Revisited

Dr. Woohoo!

Flash on the Beach has been noted for a being a conference that despite it’s name isn’t solely concentrated on Flash. Although you’d expect the whole platform to be covered (Flex, AIR, etc), which it is, FOTB also hold sessions on technologies only loosely associated with Flash, other Adobe products and pure Web technologies too. They’ve held talks on the likes of Processing for example, and there are talks about technology in general. This was the first of those kind for me.

Dr. Woohoo! talked about his time working with cybernetics and digital art and his paradigm of Art + Science = Serious Fun. He talked about about the people and places that have influenced his work and shaped his career to date.

He spoke about his time at the Santa Fe complex, showed some great recordings of the Art && Code symposium and other exhibitions he’s attended, spoke about the current state of affairs with reference to projects like Computer Vision and more recently Project Natal.

He then demonstrated his latest work with a ZCam and openFrameworks to drive mini-bots around his podium on stage.

There was a lot of name dropping and references thrown in to books and other institutions, recommended reading and quotes from luminaries of the field (far too many for me to write here). His blog is regularly updated, so hopefully his slides will eventually surface there.

Telling Stories

Hillman Curtis

Telling stories was another such session.

Hillman Curtis was the Art Director at Macromedia when Flash was first born in 1998. In his talk he spoke about his journey from then until now, his work with photography, film and Web design and his influences and muses found along the way.

We saw work from his portfolio and part of his latest film; a feature length documentary on David Byrne.

Despite being another code-free talk, it was attended by all event-goers and met with a compelled atmosphere no less.

I actually though this was very well placed at the end of the day, it seemed to encapsulate everything about why we do the things we do, even if not talking directly about our software product itself.

Epiphany

Joel Gethin Lewis

That was the end of the daytime sessions. After a break we returned for the first of the ‘Inspired’ evening sessions of the week. These talks aimed to be free of code too, if not development entirely, hosted purely for inspiration and the feel-good factor.

Joel Gethin Lewis is an interaction designer and artist who previously worked with United Visual Artists.

We saw some of his work there including the brilliant Regent Street Christmas lights of 2007. The huge light installation claimed to be the first ever ‘interactive’ Christmas lights created, the formations and lights changed based upon the density of shoppers below and other factors such as surrounding weather conditions, captured by cameras and climate sensors hidden around the street.

Since then he has founded two new companies, Hellicar&Lewis and YesYesNo.

From the latter we saw their project Lights On (also currently on the YYN homepage at the time of this writing), a massive audio visual performance created for the opening of the new Ars Electronica museum. With YesYesNo, he spoke about his work with openFrameworks and Computer Vision also.

He also worked on another great project called Contact, a floor-based artwork commissioned by the British Council that tracked the motion of those walking over it and generated physics-simulated shapes and objects below them on a giant LCD surface.

The thing is, this project was developed in about two weeks and made possible only by leveraging open source software. It’s with this possibility and ultimate realisation upon Contact’s success that that Joel reached his ‘epiphany’; that in his opinion, all software not only need not be paid for but should be free and open source.

Enthused, he found a whole host of open sourced software and similar successful projects and became set on being a champion of the open source school of thought. There’s a great article from Creative Review earlier this year in which he and partner Pete Hellicar talk about their experience.

All in all, a great first day from Flash on the Beach – all boxes ticked and more, exceeding expectations already.

I do apologise for the lengthy post, worry not – I’m sure I can’t keep this up. :)

For a change, this month’s LFPUG didn’t actually feature any Flash. Instead, we were presented with an introduction to iPhone application development with two single-hour talks delving into developing with Objective-C and the Cocoa Touch environment, but all specifically tailored to take an approach designed for a Web developer’s perspective.

I really don’t know how I feel about iPhone development, as a Flash developer, anyway. There’s been a lot of ‘iPhone for Flash developers’ or ‘Actionscript for the iPhone’ or similarly titled tutorials spring up around the Web lately, which I guess have come about on the back of the over night success stories from applications booming in popularity and the ease with which the App Store lets a small dev team get equal distribution and visibility of their application. But why Actionscript?

The profitability is understandable, I just think it’s strange that specifically Flash developers assume that iPhone development is something they can or should be laying claim to, that it’s something within their domain or their right to be creating these apps? It’s gotten to the point where a Flash platform meeting is hijacked (hijacked isn’t the right word, it wasn’t unwelcome and it drew the biggest turn out I’ve ever seen) – is it selfish (?) that there’s such a demand for tutorials to be made easily digestible for them, when traditionally any other kind of development is usually approached by everyone else peaking in?

I’m not sure, I can’t decide. Maybe it’s more honest – that instead, for example, it’s the look and feel, the slick presentation layer and the interactivity of the interface that’s so attractive (it’s Flash-like) – and a lot of people do start playing with Flash because it looks good. Flash is inherently a visual platform. Maybe Flash just is the closest platform and Flash development easily lends to iPhone development.

Whatever the case, thinking as a platform-agnostic programmer, I was looking forward to the meeting. I have an addiction to learning (or trying) new languages even if I needn’t, plus it was honestly disclosed that this week there would be no Flash content an iPhone 101 bent into shape for Flash developers to understand, it would be was tailored for Web developers generally – I was hoping for more conceptual comparisons rather than perhaps just pointing out syntactical differences – either way, curiosity had the better of me.

First up was Masi Woermann starting with An Introduction to iPhone Application Development. He introduced the broad concepts of iPhone development and the different approach developers must under go to create applications mainly looking at the workflow. Being primarily a Flex developer, Masi maintained comparisons between the architectures of a Flex app and an iPhone app – drawing parallels between Objective-C and Actionscript coding and their relationship to the UI components created with Interface Builder versus MXML.

He introduced the development tools and iPhone SDK, discussed some basics of Objective-C (pointers, memory management, classes) and eventually produced a very simple application – demonstrating the basics of interacting with visual components, straightward methods, getters, setters – some simple OOP.

It was good to see some hands on coding and that, obviously, although it’s a completely different kind of development – it might be intimidating but it’s not impossible. Watch it here:

Masi Woermann - An Introduction to iPhone Application Development

Then Matt Biddulph presented iPhone Development for Web Developers. Matt is primarily server-side developer working with the likes of Python, Ruby and Rails, but instead of going into any code expressed that his real interest in iPhone applications lies in the device’s connectivity, specifically the capability to connect to the Web and interoperate and network with data and objects found there.

He looked at the applications that Twitter and Facebook developed, quoting Joe Hewitt‘s development wisdom with his work at Facebook.

He also criticised some of the failures of the current SDK, as Hewitt also did, specifically that some of the native features that you’ll see in Apple’s applications still aren’t available for third-party developers to utilise. I hadn’t realised this was the case, or would have thought Apple would hold back on anything – I guess with later releases more features will become available. The iPhone OS 3.0 SDK is due for release this summer, perhaps more will become available then.

Watch Matt’s talk here:

Matt Biddulph - iPhone Development for Web Developers

Matt also mentioned Phonegap, an open source cross-platform mobile framework for building apps with JavaScript. It’s been labelled as being ‘like AIR for the iPhone‘ and operates on Android and Blackberry, too. Again, maybe it’s just be another means to cut a corner and not develop with the native environment, but it looks impressive – and it seems powerful. You can take advantage of all the core features of the various platforms – geo-locations, the accelerometer etc.

It’s also created entirely by by Web developers. As the video on their site claims, there’s not many Objective-C developers but there are a lot of Web developers – so in keeping with the rest of these observations, there really are more and more opportunities and points of entry for Web developers to get into mobile and iPhone app development, it’s purely demand that has created these.

All in all, whether it’s ‘in favour’ or not for Flash developers to want to develop iPhone apps is probably irrelevant – whether its a for profit or to expand a skillset probably doesn’t mater either. Hopefully all the attention will cause a shift in the perception of developing for mobile devices in general, I know I still cringe whenever anyone mentions Flash Lite – but it seems that’s starting to enjoying the beginnings of a resurgence too.

Then I think of initiatives like Adobe’s Open Screen Project and think this could be a really exciting time for mobile devices regardless, maybe there’s just so much fuss over the iPhone right now because it’s the iPhone.

As I write this post an email has just arrived in my inbox announcing there’s new group meeting specifically for developing iPhone, the London iPhone Bootcamp – ‘part seminar, part hackathon, part workshop’ – they too, are looking for the next killer iPhone app!

Thoughts?

A couple weeks back I spoke about Adobe’s possible development on a new Flash platform for the iPhone.

This week the Guardian has an interview with Shantanu Narayen, Adobe CEO, offering some comments on Apple’s position:

“Everything that goes onto the iPhone when it’s shipped needs their cooperation. What we really want is Flash built as a plug-in to Safari on the iPhone. But it’s working; I’ve seen demos of it.”

Hopefully then there’s more promise in the idea rather than just being the product of the rumour mill that it almost looked like before.

As the article says, it would be a significant turnaround for Apple. If the device supports the Flash plug-in, it could potentially offer a future implementation where iPhone applications can be developed in Flash. I know it’s an intimidating task for web developers to look at programming Cocoa and Objective-C.

His comments aren’t the main focus of the interview though, Narayen instead airs his views that Microsoft are muscling in on Adobe’s online video market, accusing them of ‘opening their checkbook’ in a failed attempt to convert companies from Flash to their new Silverlight player.

I’ve not developed with Silverlight, or really have any pressing desire to – and the most recent Flash vs. Silverlight stats probably point to not having to for the majority of clients any time soon, either. The latest statistics post Flash video at an 86% market share against Silverlight at 13% (though US based).

It’s no coincidence that Microsoft released Silverlight 2 so close to the Flash Player 10 launch last month. But can it compare? Some people love it, others are undecided - but if anything, Silverlight need to stop losing big companies. BBC have changed to Flash, NBC quite notably for their NFL coverage too.

Then last week, the New York Times reported:

A Microsoft official cited on Tuesday improvements planned for the company’s Silverlight platform for rich Internet applications, including intentions to run Silverlight applications outside of a browser.

If Microsoft want to get competitive with Adobe, they need to do this – assuming of course they maintain cross-platform support. Then they really can go head-to-head.

They bring with them a mass of .NET and WPF developers. Breaking out the browser, with these, could potentially shadow Adobe AIR in the desktop RIA market – which is still relatively basic in it’s file system and native platform/OS integration.

It would seem the time has come. Paul Betlem, Senior Director of Engineering at Adobe, ‘confirmed’ earlier this week that Adobe are developing a Flash Player for the iPhone. It’s left the Flash community buzzing since the announcement was made at Flash on the Beach on Tuesday.

As a rumour, it’s been bounced around the Web for a while now (1, 2, 3), and Serge Jespers implores it’s nothing new. Perhaps it’s simply the next logical progression in the growth of the iPhone, or an inevitability in attempting to cure Steve Jobs’ Goldilocks syndrome.

His is a stance is one I can completely understand, I agree with the quote Mike Downey finds from Shantanu Narayan, Adobe CEO, in his belief that Flash is synonymous with the Internet. Poor support in the restrictions of Flash Lite could spoil the (otherwise, almost faultless) iPhone experience, or otherwise not be worth the effort that would be involved in it’s integration.

If this does come to fruition, I doubt it’ll be an upgrade for the current second generation iPhone anytime soon, it would certainly be too CPU intensive for it’s predecessor.

Sarah Perez at ReadWriteWeb though, asks a different question – Do We Care?

Looking at the comments and the poll results, apparently we do. Personally, I think it could offer almost boundless opportunity for current Flash developers.

Diggnation this week covered a story of rags-to-riches, posting the iTunes App Store as virtual gold mine for indie developers. Steve Demeter, developer of $5 iPhone game Trism, announced he made $250,000 in profit in just two months. The immediacy and simplicity in getting your application visibility on the app store means any project, like the effort from Demeter’s four-man crew, can contend an equal playing field – an ‘exciting new landscape’ as opposed to today’s overcrowded world of dot-coms, as the article puts forward.

There was nothing nobody could say.