The QNX Neutrino OS is of course the underlying platform used by the Playbook as well as huge range of server, industrial and automotive products, all with “space-grade reliability”. QNX has of course shipped Neutrino in a huge array of different products in various configurations, making it one of the best choices for industrial, automotive, transport and consumer devices.

Interestingly, with the QNX Car, automotive OEMs can leverage Flash in a very unique way.  Merging highly available OpenGL rendering with Flash components, and blended together using some special sauce.  So with QNX Car, it’s possible to produce dashboards that are highly available and safe, yet dynamic and easy to produce in Flash.  To enable this, the Neutrino OS employs a number of distributed processing techniques that ensure the safe running of key components – all while offering amazing multimedia and connectivity features.

Throughout 2010 we’ve all been thinking about the huge range of new devices, tablets, televisions and mobile phones that have begun to change the digital landscape.  As part of my investigation into the automotive space, I started to think about the interactions between these devices.  Do passengers want their tablet to be the control hub for their car of the future?  What can we learn about our driving “expertise”, or green credentials using applications?

Imagine all of the opportunities for great integrated applications, think of all of the information at your disposal! We could have personalized and theme’d dashboards, mood sensors, and with 4G connectivity options on the horizon, we could see vast amounts of telemetry data help with the ever increasing congestion on our roads.

Well the good news is that the folks at QNX are already putting these concepts together. Let’s take a look at this demo shown at CES, integrating the RIM Playbook directly with the QNX car control systems…

This year I’ll be missing Adobe MAX in person, heading to Ireland tomorrow for a family wedding, so it has been an interesting experience to watch from afar.  I guess the most obvious thing to point out is that “I can” – that is, watch it from afar.

The keynote this year is being approached differently, it’s all about solutions.  You’ll notice that ‘devices’ don’t have a predictable section of their own, instead they are presented together across a set of five innovation vectors, Web Development, Video, Digital Publishing, Enterprise Applications, and Gaming.  The dynamic has shifted from technologies to solutions, as presented by Kevin Lynch and guests Martha Stewart, Mark Goldberg of EPIX, Joe Simon of Condé Nast, Mike Lazaridis of RIM and David Nuescheler of Day Software (soon to be an Adobe company).

The conference this year is powered by Akamai and distributed using Flash Player to desktop computers, mobile phones and tablets and all major browsers.  In addition, this years MAX is also streamed using Peer-2-Peer technology, found in Flash Player 10.1 – which is now available on 74% of desktop computers and just 3 months after launch.

These changes sum up our ongoing strategy to enable the creation of applications that are fit for purpose, expressive and multi-screen.  As part of this we re-organized our teams at Adobe, folding the Flash Platform business unit into the Creative Suite Business Unit.  Together our new group is called CIBU – Creative & Interactive Solutions.

Web Development

Earlier in the year at Google IO we showed a new HTML5 extension for Dreamweaver CS5, created to enable the production of web properties across screens.  Within this new HTML5 pack we have added support for CSS3 and media-queries that allow your web pages to be easily transposed to different screen sizes.  Simply run the Adobe Updater to get started.

Kevin also showed a new prototype, codename “Edge” that is effectively Flash Catalyst for HTML and uses the popular JQuery JavaScript library.  Using Edge you will be able to create HTML5 applications and sites with animations and media, drastically shortening the development time for web properties, widgets, and not to forget, great prototypes that run across screens.  I can’t wait to start creating AIR applications and mobile websites with Edge, it’s going to be huge.

Finally, with our recent acquisition of Omniture we also showed NetAverages, an amazing product that forms part of the suite of applications including analytics, optimizations, conversion and acquisition tools.  With NetAverages you can now gain access to a wealth of data around HTML5 support, devices, platforms and various technologies – all of which is presented in a stunning Flex interface.  Statistic are gleaned anonymously from a large range of the worlds most popular websites.

Digital Publishing

This year we’ve seen the introduction of the Tablet form factor, which is a great leap forward for the publishing industry – enabling a new distribution and monetization model for the publishing industry.  As part of this great work we’re going to ramp up our contributions to webkit, delivering improvement in layout control – including precision text wrapping around shape/images and enhancements for dynamic rendering of content for different form factors.

Today, almost all major publishing houses use Adobe InDesign to create their print pieces and deliver these to consumers at news stands.  So it makes a lot of sense for this workflow to be enhanced to encompass the packaging and delivery of Digital Publications.  We’re calling this solution the Adobe Digital Publishing Suite, a set of tools, deployment and SiteCatalyst reporting services that make it incredibly easy to target these new devices in a sustainable way.

Publishers create “stacks”, which are essentially articles/pages/ads in InDesign CS5 in portrait/landscape/both and publish these individually.  Each stack can include interactive elements, buttons, links, scrollable frames and slideshows to enable rich experiences and drive innovation in their digital pieces.  In addition, you can also use the Interactive Overlay Creator to produce 360° views, panoramas, image pans, audio, video, and web views.  Web view is very similar to StageWebView, described in my previous blog posts

Video and audio are added very easily and use the H.264 format in addition to standard mp3 formats.  You can integrate audio as part of the experience, maybe clicking sounds or swoosh effects – although I hope you can be more imaginative!  Each interactive element has associated parameters to enable you to control the interaction for the user, such as looped slideshows, handling swipe events, fading, hightlights, transition timing and delays.

Finally, you can use the Adobe Digital Content Bundler to take the stacks and create an issue of your publication by simply adding each of the publication content folders and stacks.  Publications can then be viewed in a generic viewer application and later deployed in a custom viewer for each publication.

From a publishers perspective, managing the technologies, deployments and interactions is pivotal to success in this new multi-screen world.  With the Digital Publishing Suite, content creators can spend more time driving their content and brand – instead of worrying about the ever increasing costs of reaching their users across devices.

Enterprise Applications

For the Enterprise we are now focused on “Customer Experience Management”, a new set of solutions that are targeted directly to enhancing the productivity and experiences for our largest customers.

At MAX we announced the availability of Flex 4.5 “Hero”, the latest version of Flex that has been highly optimized to enable the creation of mobile applications for Android, Blackberry and of course desktop computers.  This new framework includes additional mobile components and skins to speed up the production of multi-screen apps and deliver new experiences on devices.

Flash Builder Burrito / Flash Catalyst Panini

Attendees received a DVD with a new version of Flash Builder, with some amazing new features for creating mobile applications.  These include device debugging for Android (inc. USB support), integrated Android SDK tools and simulation for a host of supported devices.  Flash Builder Burrito ships with Flex 4.5 embedded and you can download the trial here.  Among the many new features are improved coding features, performance improvements and much improved support for working with Flash Catalyst Panini.

The Catalyst team have also been hard at work improving the workflows for designers and developers using Flex.  With “Panini”, the team have focused on delivering the first steps towards full round tripping between Photoshop and Illustrator and Burrito.  The results are looking great, enabling resizable applications and components, custom skins, code generation improvements and improvements for animation control and styles.  You can download the trial of Panini here.

Day Software

Earlier this year we announced that we are to acquire Day Software, a Swiss company with offices in Boston.  Day are a global leader in content management with customers like Audi, Nissan, Volkswagen, MTV, Virgin Media and McDonalds.  David Nuescheler was on hand to show CQ5, an amazing solution for managing content in multiple languages and for multiple screens.  Customers can simply drag and drop assets and pages, type content directly into the pages and leverage approval and localization workflows directly from the tooling.  I can’t wait to see more of our new EMEA team

Video

Flash is now enabling the playback of 120 Billion megabytes of video every month, an astounding number that presents huge challenges for the Flash Player team.  Today Flash supports numerous formats, resolutions and audio codecs being mixed together and delivered using DRM, encrypted streams, the open RTMP and it’s variants.  In the latest player we also support playback over HTTP and RTMFP for P2P distribution of large events, thus driving the industry forward.

So what’s so big about video on a TV?  – Well, what we actually showed is DRM protected and encrypted video running across the internet in HD format to a television.  We’ve all sat at home watching video on our computers with 30″+ televisions in front of us, it’s just annoying.  Today we showed that EPIX can leverage the Omniture analytics suite and industry approved Token based DRM (Flash Access) to present high-value content from the studios directly into the home.  This signifies an industry change, for the first time you can deliver video across screens, whilst protecting it, measuring it, and enabling users to gain access to a full web of video currently missing from the living room.

At MAX we announced two things, Flash and AIR for TV and a new way to display video – StageVideo.  StageVideo enables the use of hardware decoders, much like VLC does today, and this results in huge improvements in the CPU usage – but with limitations.

The API enables video to playback on a graphics plane, delivered straight to hardware, as opposed to being pipelined back into the Flash Player.  Because of this, videos rendered with this API cannot support transparency and objects will not render behind the video.  Flash content, such as overlays for video controls are rendered on top of the video in a separate graphics plane.  In fact, on TV this will be the defacto rendering method and all video objects will render this way.

Moving forward, all devices using the Flash runtime will have access to this new API set.  The Blackberry Playbook is the first tablet to implement this support to deliver an incredible video experience on their hardware, demonstrated for the first time at Adobe MAX.

AIR applications can now be built for TV using AIR2.5, the applications runtime deployed for Android and desktop platforms.  These applications are typically video based, although we do see some great opportunities for gaming and social connectivity moving forward.

Flash Player and AIR on TV are supported on Samsung TVs and Blueray Players, Google TV and BBC Youview hardware.

Gaming

The most exciting piece from the keynote today was probably the advancements in gaming and 3D support planned for an upcoming Flash Player release.  On the top of the tick list is game controller support, the ability to simply plugin your USB joypad or steering wheel and start playing games!  I’m so excited about it

Needless to say, gaming on the web is set for a omplete overhaul, with 3D capabilities that use leverage GPU hardware and rendering millions of triangles per second.  What’s more incredible is that the demo below uses 0% CPU, and if our current stats hold true, we can get this out to 3/4 of the online world in three months after launch.

Check it out…

Note: These AIR features are “working”, although they may not make it into the v1 product.
Note: This is not an Adobe product, but simply a feature demo that took 3 days. Any one can build P2P applications with Flash and AIR.

This week I have been working on a couple of different mini-projects to test out new beta features of AIR 2.5 for Android. The engineering team are pushing out features every week, and I have to say I’m very very impressed with their efforts. We are arguably now at feature parity with the desktop AIR releases, which is precisely the goal of the Open Screen Project.

In the 5/7 build we have added Camera, Microphone, StageWebView and NativeExtensions features to the beta. Of course AIR comes with all of the Flash Player 10.1 features along with multi-touch/gestures, support for bitmap matrix caching and Geolocation APIs in addition.

The code isn’t exactly stable so I don’t want to release it just yet. I hope I can finish it by next week, by which time it will have a name.  I changed the name of this demo since it’s not an Adobe Flash Platform product, which caused some confusion. There aren’t plans currently to release this as a product, however I will publish the source code for all.

Flash/AIR on!

Surprise!  Today at Google I/O Vic Gundotra, Google VP Engineering announced Flash Player 10.1 and Adobe AIR 2.5 running on FroYo.  The launch today represents a milestone that we’ve been working towards for some time, and all of us at Adobe are hugely excited to see Flash Player 10.1 finally get into the hands of consumers.

The beta is now waiting on the Android Market for Nexus One and other Android 2.2 users to test out.  General availability is expected in June 2010.

While today’s announcement is all about Android, our target mobile operating systems for Flash Player also include Windows Phone 7, webOS, Symbian, and BlackBerry. Adobe provides a porting kit and Linux-based reference implementation to Open Screen Project partners to allow them to port Flash Player 10.1 to other platforms. These ports are subject to Adobe certification and must pass our standards for compatibility, performance and usability in order for devices to be marketed as “Includes Adobe Flash Player.”

Optimise your Flash Content

Flash Player 10.1 on Android

In all, Flash Player 10.1 has been built from the ground up, and not just for mobile phones but for the desktops, tablets, netbooks and even televisions, consoles and set-top boxes.  We have been working extremely hard on the runtime of course, but on top of that many of you have been working with us to optimize your web content for Flash Player 10.1.

Here is a landing page that features a number of websites that highlight the variety of Flash Player user experiences available on a mobile device. These sites and most popular websites that use Flash can now be accessed on smartphones supporting Flash Player 10.1.

Since we demonstrated the Flash Player on Android at the Mobile World Congress there have been a number of decisions made, changes implemented and tweaks applied to Flash Player 10.1.  These changes focused on usability, integration, performance and power management – so let’s look at some of these in more detail.

Installation and updates

I have documented the process over here in another post.  Suffice to say, the process is simple and demonstrates our commitment with the Open Screen Project to ensuring the evolution of Flash Player on mobile and devices.

Multi-touch

Due to time constraints with shipping FroYo it hasn’t been possible to make all of the Android browser changes required to enable multi-touch in Flash Player.  Web enablement has always been the top priority and so this (extremely complex) integration will happen later.  AIR 2.5 on Android is multi-touch enabled and so it’s still possible to use your fingers, thumbs and toes as necessary on Android.

Accelerometer

One of the cool new feature of Flash Player 10.1 is the accelerometer API, making Flash Player the first browser technology to support access to this hardware.  In Device Central CS5 we have added some emulation support for the API, you can read more here.

Focused Mode (single tap)

The Android and other browsers support multi-touch for viewing web pages, so that you can pan and zoom around non-optimized sites with ease.  To ensure that touch events are received by Flash or the browser appropriately we have created focused mode.  It works very simply using a priority system, so if you tap the Flash content that you want to interact with Flash receives the touch events, if Flash doesn’t pick up the event then it’s passed to the browser.  Tapping on the HTML will revert this focus priority back to the browser.

Smartzoom (double tap)

When a user double taps a piece of Flash content it will zoom to fit the screen, while maintaining the correct aspect ratio.  The content is still viewed in the context of the HTML, rather than launching into full screen mode.  This ensures that content remains in embedded mode – which makes sense given that this is the predominant usage of Flash on the web.

FullScreen (AS-only)

Another change to our previous showing is that FullScreen mode is now controlled via actionscript, just as it is on the desktop.  So if you want your video player or game to playback using the full screen, then you’ll need to use this code: stage.displayState=StageDisplayState.FULL_SCREEN;

Smart Rendering

We have already seen some of the benefits of this effort on the desktop version of Flash Player 10.1.  Essentially it means that Flash content that’s not visible to the user will not be rendered and will receive limited CPU time.  SWFs that are off-screen and/or consuming required resources can also be put to sleep and resumed on demand.  You can control this behaviour by applying priority values to SWF files using the embed tag.

Video Hardware Decoding

One of the hardest features to get right has been video hardware decoding, and for the beta version this will not be enabled.

Sleep Mode

The player will be put to sleep along with the device to conserve power.  So if you fall asleep watching youtube then you won’t wake up to talking cats at 4am – tried and tested.  cats…

Out-of-Memory Management

For me, this is the kick-ass feature that should always have been arbitrating the use of the Flash Player.  If your content is not optimized correctly, has serious memory leaks and manages to use too much CPU power then it’ll go in the “sin bin”   These SWFs will render with a “click-to-play” button that the user can control as necessary.

Device Events

As with Flash Lite before it, Flash Player 10.1 has to be a good citizen on a mobile phone.  So if you receive a call or change application then Flash Player will respond appropriately, which typically means shutting down or pausing depending on the platform.

Minimum Spec

As has been documented before, our minimum spec for Flash Player 10.1 is ARM11-Cortex A8/9 at 550mhz.  For Cortex-A8 processors we require NEON, which enables improved multi-media playback for a lower mhz rating.

If you don’t know what any of that means then I wouldn’t be too concerned.  These chipsets represent the bulk of what our OEM partners are shipping, or planning to ship moving forward – and this list will undoubtedly expand.

Demos

Use Flash Builder to develop Adobe AIR apps for Android
Use Flash Professional CS5 to develop Adobe AIR apps for Android
See Flash Player 10.1 running on Android

AIR 2.5 on Android

Also announced today is an expanded pre-release of AIR 2.5 for Android devices.  Many of us on the Evangelism team have been playing with this for several weeks now, and it’s seriously cool.

More info here

The tools covered will include Flash Builder, Flash Professional, Flash Catalyst, Flex 4 and the Flash Player 10.1 and AIR 2 runtimes. In my own session we’ll also be covering Device Central and some asset optimization guidelines for targeting mobile phones.

We’ll also look at P2P with Flash Player 10.1 as well as Livecycle, PHP and Java integration on the backend.

Schedule:

June 7th – 12:00 – 13:00 GMT Erase the Designer to Developer gap: Adding interactions to your design with Serge Jespers
June 7th – 15:00 – 16:00 GMT Connecting your design to PHP services with Mihai Corlan
June 8th – 12:00 – 13:00 GMT Connecting a web application to a J2EE backend using Flash Builder 4 with Michael Chaize
June 8th – 15:00 – 16:00 GMT Working with Flash CS5 components in your Flash Builder 4 project with Mike Jones
June 9th – 12:00 – 13:00 GMT Going multi-user with P2P in Flash Player 10.1 with Tom Krcha
June 9th – 15:00 – 16:00 GMT Developing multi-user applications with LiveCycle services with Tom Krcha
June 10th – 12:00 – 13:00 GMT Bringing web Applications to the desktop with AIR 2.0 with Piotr Walczyscyn
Jun 10th – 15:00 – 16:00 GMT Code once and run on multiple mobile devices with Mark Doherty

We’ve been busy for the past week building “EVA” to demonstrate all of the above.  I think you’ll be really impressed with it and of course we’ll be providing the code after for you to use in your own applications.

SIGN UP HERE

While I was at the Mobile World Congress earlier this year I recorded a quick video of sample tablet hardware running a beta version of Flash Player 10.1.  It has taken a “little” while to arrive on Adobe TV, but in the video I’ll show some popular websites covering video and gaming.

The hardware is a development board sporting the ARM based NVIDIA Tegra Next Generation chipset, which is a dual-core ARM-Cortex A9 device.  Although I didn’t show it here, at the conference we were also running AIR applications beautifully on the hardware.

Our Open Screen Project partners NVIDIA announced that some 30+ tablet computers are expected to ship in 2010 with this chipset.  One of the advantages of having NVIDIA and ARM as Open Screen Project partners is that we can all contribute collectively to Flash Player acceleration for these devices.  So as OEM begin to adopt TEGRA they can rest assured that the Flash engineering is already taken care of.

My favourite so far would have to be the NotionInk Adam, which is an Android based tablet created in India.  The screen apparently has transmissive, transflective, and reflective display modes that will serve the device well in different lighting conditions.

Yesterday I spotted a lady here in the UK showing off her Palm Pre to a friend.  So today I recorded a video to take a look at Palm’s WebOS Browser with Flash Player 10.1.  Please note that the engineering build on this device is not up-to-date, but you can certainly get an impression of how great the experience will be.

For the user experience professionals out there, check out the card metaphor for switching between applications; amazing.

As some of you know, learning about AIR, AS3, Flex, Flash Catalyst, Flash Builder has been my side-project for a few months now.  As I mentioned in a previous post, it is essential to prepare for the future and invest now in learning new skills.

For me, the best way to learn new things is to create a project that’s difficult, yet cool enough to keep you interested.  So my first few steps revolved around learning how to use Fireworks, then Flash Catalyst, Flash Builder and ultimately distribute an application using Adobe AIR.

AIR 2.0

One of the amazing new features of AIR 2.0 is the ability to embed and execute native code from right inside Actionscript, an API called NativeProcess.  This means that you can safely run existing services over the command line, as well as install your own native service components.  AIR 2.0 is in beta right now on Adobe Labs, and is mobile ready as designed so it’s a great time to get started.

So what would a Platform Evangelist for mobile and devices create?

Introducing Helisso

What is it?

• A packaging utility that can produce SIS packages for Symbian devices
• It targets the Flash Lite 3.x runtime for Nokia’s S60 devices
• It runs on PC and Mac OS, all versions

Details

• The tool has embedded Python binaries inside, compiled versions of “Ensymble“
• For signing purposes the tool also includes OpenSSL for certificate signing
• It is unsupported and without warranty

How do I use it?

How do I install it?

• Install AIR2 Beta first
• Windows
• Mac

I have been hugely impressed with the capabilities provided by AIR, in this only my first AS3 project.  Looking back on all of the technologies that I have used has really got me excited about AIR applications on Android, and even sprouted a few iPhone applications in advance of that.  Seriously, imagine having all of the power of AIR and this toolchain on mobile phones?

Lastly, a big shout out to Steve Hartley of Oppian, Jussi Ylänen creator of Ensymble, without whom this wouldn’t have been possible.

Flash Player 10.1 will become available in the first half of 2010 for all supported platforms.  In fact, the desktop beta 3 is already looking incredible and proving to be a huge hit with developers testing their content.

One of the most important parts of our work with our Open Screen Project OEM partners is to enable the seamless discovery, installation and update of Flash Player 10.1 on device platforms.  I know that some have asked questions on this, and so I’m glad to bring you some responses, if a little late.

Extending the reach

In the “marketecture” diagram below you can see that Flash Player 10.1 is extending it’s platform reach, doubling it in fact.  It’s worth noting that recent reports around minimum spec’s for Flash Player 10.1 are alluded to here also, because working with our partners, we are targeting the latest chipsets available.

To explain, smartphones have a typical lifespan that is less than half that of a desktop computer, and so hardware choices are made by planning for the future.  Over the past few years we have shipped over 1.5Billion devices with Flash Lite using this simple rule.

Therefore the choice to target the ARM Cortex-A8 chipsets will result in greater efficiency, and most importantly a wider range of consistent experiences as uptake grows.  To be clear, that uptake is already happening, and it will expand rapidly just like it does every other year.

It’s like a Moore’s Law of mobile phones

Yet some devices will not be able to support the full Flash Player 10.1 due to low hardware capabilities, and for many of those devices we have a new version of our optimized runtime, Flash Lite, to fill the gap.  In fact the alpha version has already been spotted running Farmville on Android Eclair here.

Driving the Distribution

Working with our OEM partners we have enabled the Flash Player to be installed in a manner consistent with the desktop experience.  When visiting websites that have Flash content, users can click on the “Flash Player required” images/links provided by content developers to begin the installation process.

As with the desktop, the browser then redirects to the Flash Player Download Center, and in the case of mobile phones we pass these requests to the requisite device application stores such as the Android Market.  Today’s application stores have extended abilities to correctly identify devices, and to manage the update of applications and plugins like Flash Player.  Users can of course visit their application store directly if they wish.

In addition, those users purchasing new devices from a retailer may already have Flash Player pre-installed, made available in over-the-air software updates or through the browser directly.

Delivering Enhancements

As with the desktop install process, with each version of the Flash Player various updates are applied throughout it’s lifetime to ensure a high level of quality.  Users can expect these updates to be provided automatically on some platforms via their application store update process, as well as through over-the-air software updates.

In the example above you can see the update notifications that users are familiar with on Android devices, and it is expected that this will be used for Flash Player 10.1 during it’s lifetime.  Though I should point out that Nokia have been providing their own update mechanism, directly in the browser for some time now with a huge user uptake.

During the past few days Palm have also begun to lay the ground for Flash Player 10.1 support by delivering their software update.

Player Detection

On the desktop today developers use a combination of methods to detect the Flash Player and version.  Recognizing the need for a consistent approach, these same methods can be used on mobile phones in the future.  Adobe recommends SWFObject2, an open source project that provides cross-browser support.  It is also supported fully within our Creative Suite tools.  SWFObject works across browsers and device platforms to detect the Flash Player and it’s version.  Should an update been required, the tool can enable the ExpressInstall experience or provide fallbacks as required.

Historically I know some have invested considerable time and energy in device databases such as WURFL, which helped us to accurately distribute application installers to devices.  With Flash Player 10.1 we need only be concerned about the browser use case, and so I would argue that we do not need to continue this effort long term.

I hope this information will help you build a picture of the huge efforts that our engineering and product teams have made.  The mechanisms for discovery, install and update of the Flash Player 10.1 are a fantastic achievement, even though for some of you these may seem rather obvious.

With the Open Screen Project partners we are literally changing the ecosystem, enabling a more complete and consistent web experience on devices, and driving the industry forward with the Flash Platform in 2010.

One of the tools that I use almost every day at Adobe for screensharing, video conferencing and presentations is called Acrobat Connect Pro.  It has been around for quite some time and today it’s used globally by organizations to help reduce the travel burden, as well as enabling teams to work together.

Today it is available for the Mac and PC and is created using the Flash Platform, with the addition of some extra features for screen sharing built into the Connect Addin for the desktop.

The great news is that yesterday the team launched their first version of Connect on mobile devices, starting with the iPhone.  It is available for free now on the AppStore, although of course you will need an account and you can sign up for a 30 day trial for free over here.

Features:

• Attend Connect Pro Meetings with integrated conference call or Voice over IP audio.
• See who has joined the meeting, and their role (host, presenter, or attendee)
• View presentations, PDF documents, videos, and screen sharing provided by the meeting organizer.
• Rotate, pan, and zoom to choose your personal ‘best view’ of shared content
• View webcamera broadcasts from unlimited live camera feeds provided in the meeting
• Participate in Chat conversations throughout the meeting.
• Join meetings attended by users on virtually any computer system: Mac, Windows, Linux, Solaris and now iPhone.

Built using Flash Professional CS5

Acrobat Connect for the iPhone was created using the Adobe Flash Platform, and specifically with AIR 2.0 APIs.  The team were able to create their contextual application using Flash Professional CS5 and simply package the application using the upcoming tool!

I know that many of you have wondered about building out complex applications such as this, and so I think this is a great demonstration of what you can achieve using both AIR and the new Flash Pro tool.

In addition, we have already shown Acrobat Connect running on Android devices and that was achieved by simply repackaging the code.  The team made some great choices with regards to their design that have made it possible for the UI to lay itself out dynamically for different screen sizes and orientations.  Some of the mobile developers among you will probably have played with these concepts before, and the rule has always been to ensure that you bake these into your design and development from the start.

As you can see the experience is really fluid and great for the end user.  I’ve been able to connect seamlessly to the Connect session and broadcast my iTunes library in coverflow view

]]> http://www.flashmobileblog.com/2010/02/25/acrobat-connect-pro-is-now-on-the-appstore/feed/ 2