The business world today is much more empowered; empowered to act and react to dynamic changes often the moment they occur. For your organization to reap the benefits of the social media phenomenon, you must adapt and become more flexible in how you engage your customers, partners and community. To do so involves cultivating social connections that focus on solving business and customer challenges rather than the traditional PR techniques of selling your prospects on just how great you are.

Now that you’ve established the need for a social strategy there are a few things that should be done before you actually devise the strategy.

A) Help the CEO formulate a social media strategy team that will include internal leaders and managers spanning the entire organization.

The social team’s job will be to help create the strategy and oversee its implementation. As internal buy-in is critical to overall strategy success, the choices made in team selection are extremely crucial. Remember, you can’t build success on a rocky foundation.

Once the team is assembled, it wouldn’t hurt to…

B) Conduct a session with your company’s executive team where you explore social tech’s ability to and success in transforming organizations.

Be sure to fully explore how the same and more can be realized by your organization. Once the seeds have been planted and the bosses are on board, you can start building out your strategy. And because you’re building on a solid foundation, you should really be able to maximize your competitive advantage by following sound principles catered to your unique value position. Does this guarantee you’ll be the next Facebook or Twitter? No, but it will guarantee a much better fate than just blindly approaching the socialsphere, hoping for the best.

Based on a recently published Forrester Research report, Social Business Strategy, there are four key ingredients to a successful social business strategy:

#1 Know Thy Neighbor
There’s no way that you can create value through social engagement if you don’t truly understand who your employees and customers are, as well as, how they use social technology. According to Forrester, 62 million US adults visited a social networking site at least monthly between 2007 – 2010 representing a 50% increase in social networking usage.

#2 Define Your Goals
What do you expect to achieve by becoming more social? Do you want to improve customer perception? Increase customer sat? Increase sales? Whatever the case may be, get specific, associate each goal with a strategy and detail the steps to achieve the goal. Once that’s established, review what emerging social technology trends make the most sense in support of accomplishing your goals.

#3 Weigh the Pros and Cons
Determine which of your goals has the greatest output (return) for the least input (investment). Don’t get caught up in ego. Realistically assess the risk, effort and complexity of each goal/strategy so you can formulate the clearest picture of which ones should be pursued and which ones to abandon. If a project requires a high investment with very little return, it should be tossed. On the other hand, if you discover a gem of a project that essentially costs nothing to implement but yields untold riches, be smart and fast-track that one.

#4 Pick the Right Tool for the Job
You’ll likely need a myriad of services to support your golden social strategy so choose wisely. Explore all your options whether it be SaaS, PaaS or even IaaS. Determine which ones integrate with your existing infrastructure the best. You ultimately want your technology selection to be the icing on your well baked plan.

I’ve personally found success with this approach and feel that it can effectively be applied to a variety of operational/strategical models. How about you?

RELATED RESOURCES
http://www.forrester.com/rb/Research/social_business_strategy/q/id/57541/t/2

The only problem is this new functionality only works out of the box for NativeWindow instances. A Spark Window, however, manages its NativeWindow internally and does not currently include support for the new owned window logic. Now, you could subclass Window and override commitProperties to add in the functionality but, that’s neither desired nor maintainable.

Why does it even matter? Because a Spark Window is skinnable and if you’ve already taken the time to build an application using skinnable Windows, you don’t want to labor over the changes necessary just to use this functionality.

So, I chose to take a different approach because I’m confident that the AIR SDK will eventually include support for ownable Spark Windows. Until then, I’m using an OwnableWindow interface that all of my Window subclasses I want to be owned are required to implement. This way I can take advantage of the new functionality in the least obtrusive way possible.

Here’s the code for OwnableWindow:

package labs.otuome.air.myapp.view.panel
{
   import flash.display.NativeWindow;
   import flash.events.Event;
   import flash.events.NativeWindowDisplayStateEvent;
 
   public interface OwnableWindow
   {
      function get windowOwner():NativeWindow;
      function set windowOwner( value:NativeWindow ):void;
 
      function respondToOwnerWindowActivated( event:Event ):void;
      function respondToOwnerWindowMinimizedOrRestored( event:NativeWindowDisplayStateEvent ):void;
      function respondToOwnerWindowClosing( event:Event ):void;
   }
}

Now, in my Spark Window subclass I implement the interface like so:

package labs.otuome.air.myapp.view.panel
{
   import flash.display.NativeWindow;
   import flash.display.NativeWindowDisplayState;
   import flash.events.Event;
   import flash.events.MouseEvent;
   import flash.events.NativeWindowDisplayStateEvent;
 
   import mx.events.FlexEvent;
 
   import spark.components.Button;
   import spark.components.RichText;
 
   /**
    * Spark Window component subclass.
    * @author Hasan Otuome
    */
   public class FloatingPanelView extends FloatingPanelUI implements OwnableWindow
   {
      ///////////////////////////////////////////////////////////////////////////
      // PRIVATE PROPERTIES
      ///////////////////////////////////////////////////////////////////////////
      private var _panelTitle:String;
      private var _windowOwner:NativeWindow;
      //////////////////////////////////////////////////////////////////////////
      // PUBLIC PROPERTIES
      /////////////////////////////////////////////////////////////////////////
      [SkinPart (required=false)]
      public var header:Button;
 
      [SkinPart (required=false)]
      public var toggle:Button;
 
      [SkinPart (required=false)]
      public var contentTitle:RichText;
 
      /**
      * Sets the panel's title. 
      * @param value
      */		
      public function set panelTitle( value:String ):void
      {
           _panelTitle = value;
      }
      /**
      * Allows you to specify an owner for this Spark 
      * Window instance. Used only until the Flex SDK 
      * adds support for owned native windows to Spark 
      * Windows.
      */		
      public function get windowOwner():NativeWindow
      {
           return _windowOwner;
      }
      public function set windowOwner( value:NativeWindow ):void
      {
           _windowOwner = value;
      }
      ///////////////////////////////////////////////////////////////////////////
      // PUBLIC METHODS
      ///////////////////////////////////////////////////////////////////////////
      /**
      * Constructor 
      */		
      public function FloatingPanelView()
      {
        super();
 
        addEventListener( FlexEvent.CREATION_COMPLETE, _onCreationComplete, false, 0, true );
      }
      //---------- OwnableWindow implementations --------------------
      /**
      * Adjust the display ordering of this 
      *	instance as it relates to its owner. 
      */
      public function respondToOwnerWindowActivated( event:Event ):void
      {
        this.nativeWindow.orderInFrontOf( _windowOwner );
      }
 
      /**
      * Show/hide this instance based 
      *	on the display state of its owner. 
      */
      public function respondToOwnerWindowMinimizedOrRestored( event:NativeWindowDisplayStateEvent ):void
      {
        switch (true)
        {
           case (event.beforeDisplayState == NativeWindowDisplayState.MINIMIZED):
             this.restore();
             break;
           case (event.afterDisplayState == NativeWindowDisplayState.MINIMIZED):
             this.minimize();
             break;
        }
      }
 
      /**
      * Close this instance when its owner is closed. This 
      *	will be handled automatically if the owner is 
      *	the main application window.  
      */
      public function respondToOwnerWindowClosing( event:Event ):void
      {
        this.close();
      }
      //////////////////////////////////////////////////////////////////////////
      // OVERRIDES
      /////////////////////////////////////////////////////////////////////////
 
      ////////////////////////////////////////////////////////////////////////
      // PRIVATE METHODS
      ///////////////////////////////////////////////////////////////////////
      /**
      * CREATION_COMPLETE event handler. 
      * Ensures this instance responds to 
      * display state changes of the 
      * instance's owner. 
      * @param e
      */		
      private function _onCreationComplete( e:FlexEvent ):void
      {
        if (_windowOwner)
        {
           _windowOwner.addEventListener( Event.ACTIVATE, respondToOwnerWindowActivated, false, 0, true );
           _windowOwner.addEventListener( NativeWindowDisplayStateEvent.DISPLAY_STATE_CHANGE, respondToOwnerWindowMinimizedOrRestored, false, 0, true );
           _windowOwner.addEventListener( Event.CLOSING, respondToOwnerWindowClosing, false, 0, true );
        }
 
        removeEventListener( FlexEvent.CREATION_COMPLETE, _onCreationComplete );
      }
   }
}

I set the windowOwner property when I instantiate the class(es) and I have a skinnable Spark Window(s) that can be owned by another NativeWindow. Downside is that the z-ordering produces a noticeable flicker and only works on the 1st click of the owner window.

Did I have to use an interface? Not at all, but it’s nice to be able to enforce the contract and easily tear it up once it’s no longer needed. Taking a different approach? Share it…

Enter: ANT to the rescue!

By creating an ANT build script, you can alleviate all of the above concerns and stay super-flexible at the same time. Here’s a template that I’ve been using lately with great success:

<?xml version="1.0" encoding="UTF-8"?> 
<project default="4. Package Application" name="[Your Flex Project Name]"> 
	<!-- Framework properties -->
	<property name="FLEX_HOME" value="[/path/to/your/flex/4.5/sdk]" /> 
	<property name="AIR_GLOBAL" value="${FLEX_HOME}/frameworks/libs/air/airglobal.swc" /> 
	<property name="ADL" value="${FLEX_HOME}/bin/adl" /> 
	<property name="ADT" value="${FLEX_HOME}/lib/adt.jar" /> 
	<property name="PFI" value="${FLEX_HOME}/lib/pfi.jar" /> 
	<property name="FLEX_TASKS" value="${FLEX_HOME}/ant/lib/flexTasks.jar" /> 
	<property name="LOCALE" value="en_US" /> 
 
	<!-- Project properties --> 
	<property name="project_root" value="[/path/to/your/flex/mobile/project]" /> 
	<property name="class_path" value="${project_root}/src" /> 
	<property name="lib_path" value="${project_root}/libs" />
	<property name="splash_path" value="${class_path}/Default.png" /> 
	<property name="app_name" value="[YourApp]" /> 
	<property name="app_root_dir" value="." /> 
	<property name="app_type" value="mxml" /> 
	<property name="assets_dir_name" value="[name_of_your_assets_dir]" />
	<property name="debug_mode" value="false" />
 
	<!-- Certificate properties --> 
	<property name="cert_loc" value="${app_root_dir}/[path/to/your/certs]" />
	<property name="ios_keystore" value="${cert_loc}/[your_cert_name].p12" /> 
	<property name="ios_pass" value="[your_cert_password]" />
	<property name="ios_provisioning" value="${cert_loc}/[your_provisioning_profile].mobileprovision" />
 
	<!-- Application properties -->
	<property name="swf_file" value="${app_name}.swf" /> 
	<property name="air_file" value="${app_name}.air" /> 
	<property name="ipa_file" value="${app_name}.ipa" /> 
	<property name="app_descriptor" value="${class_path}/${app_name}-app.xml" /> 
	<property name="main_class" value="${class_path}/${app_name}.${app_type}" />
	<property name="build_dir" location="${app_root_dir}/build" /> 
	<property name="debug_dir" location="${app_root_dir}/build/debug" /> 
	<property name="publish_dir" location="${app_root_dir}/build/deploy" /> 
	<property name="assets_dir" location="${class_path}/${assets_dir_name}" />
	<property name="output_loc" location="${publish_dir}/${swf_file}" />
 
	<!-- Use the Flex ANT tasks for easier compilation -->
	<taskdef name="mxmlc" classname="flex.ant.MxmlcTask" classpath="${FLEX_TASKS}"/>
 
	<!-- Clean existing directories --> 
	<target name="1. Cleanup Directories" description="clean up"> 
		<delete dir="${debug_dir}" /> 
		<delete dir="${publish_dir}" /> 
		<delete dir="${build_dir}" /> 
	</target> 
 
	<!-- Create required directories --> 
	<target name="2. Build New Directories" depends="1. Cleanup Directories"> 
		<mkdir dir="${build_dir}" /> 
		<mkdir dir="${debug_dir}" /> 
		<mkdir dir="${publish_dir}" /> 
	</target>
 
	<!-- Compile SWF to build-directory for packaging --> 
	<target name="3. Compile SWF" depends="2. Build New Directories"> 
		<mxmlc 
			file="${main_class}" 
			output="${output_loc}" 
			locale="${LOCALE}" 
			static-rsls="false" 
			accessible="false" 
			configname="airmobile" 
			debug="${debug_mode}" 
			failonerror="true" 
			fork="true" 
			maxmemory="512m">
			<source-path path-element="${class_path}"/>
			<compiler.library-path dir="${FLEX_HOME}/frameworks" append="true">
				<include name="libs/*" />
			</compiler.library-path>
			<library-path file="${FLEX_HOME}/frameworks/locale/${LOCALE}" append="true"/>
			<library-path dir="${lib_path}" includes="*.swc" append="true"/>
			<external-library-path file="${AIR_GLOBAL}" append="true"/>
		</mxmlc>
	</target>
 
	<!-- Package the application to an ipa file & save it in the publish directory --> 
	<target name="4. Package Application" depends="3. Compile SWF"> 
		<java jar="${ADT}" fork="true" failonerror="true"> 
			<arg value="-package"/>
			<arg value="-target"/>
			<arg value="ipa-test"/>
			<arg value="-provisioning-profile"/>
			<arg value="${ios_provisioning}"/>
 
      			<arg value="-storetype"/>
			<arg value="pkcs12"/>
			<arg value="-keystore"/>
			<arg value="${ios_keystore}"/>
			<arg value="-storepass"/>
			<arg value="${ios_pass}"/>
 
			<arg value="${ipa_file}"/>
			<arg value="${app_descriptor}"/>
			<arg value="${output_loc}"/>
 
			<arg value="-C" /> 
			<arg value="${class_path}"/>
			<arg value="${splash_path}"/>
 
			<arg value="-C" /> 
			<arg value="${class_path}"/>
			<arg value="${assets_dir}/icons/." /> 
		</java> 
	</target>
</project>

UPDATED 3/23/11: changed the Package Application target to use ADT vs PFI now that AIR 2.6 is official.

You should only have to modify the values wrapped in brackets [ ] to match your system setup. Once that’s done, you’ll need to tweak your application’s descriptor file (ie, myapp-app.xml) as follows:

#1 Modify the initialWindow’s content value to match the output path from your ANT script:

<content>[This value will be overwritten by Flash Builder in the output app.xml]</content>

becomes:

<content>/path/to/your/application.swf</content>

#2 Add the following iOS-required data, either before or after the Android data section:

<iPhone>
    <InfoAdditions><![CDATA[
<key>UIDeviceFamily</key>
<array>
<string>1</string>
<string>2</string>
</array>
]]></InfoAdditions>
    <requestedDisplayResolution>high</requestedDisplayResolution>
</iPhone>

After that, you should be able to compile your app using the ANT script without problem from any IDE that supports ANT or even from the CLI. This certainly isn’t the only way to accomplish this, it’s just my take on it. Feel free to hack away at it and share what you come up with.

If you should decide to bypass the template and build a script from scratch, here are a few caveats to remember:

• update your application descriptor to use the output SWF path from your ANT script instead of the default placeholder text provided by Adobe
• add the appropriate iOS tags to your descriptor
• modify the ANT template to point to your system specific config (SDK, project, certs)
• don’t forget to add your certificate’s password
• remember to load the airmobile-config.xml (configname=airmobile vs air)
• change ipa-test to ipa-app-store before publishing to the App Store.

Checkout some of the related resources for alternatives to tackling the same problem and just general information on developing AIR applications for iOS devices.

RELATED RESOURCES
http://www.ivanalvarez.com/2010/10/flex-4-in-ios-3/
http://www.terrenceryan.com/blog/post.cfm/compiling-flex-hero-apps-with-mxmlc-in-ant
http://blogs.adobe.com/cantrell/archives/2010/09/packager-for-iphone-refresher.html
http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac1e63e3d128fc240122-7ff2.html
http://help.adobe.com/en_US/air/build/WSBE9908A0-8E3A-4329-8ABD-12F2A19AB5E9.html
http://help.adobe.com/en_US/as3/iphone/air_deviphoneapps.pdf

Features:
1 GHz dual core processor
1 GB RAM
Pair PlayBook with your BlackBerry smartphone via Bluetooth
Uses the same tech Cisco uses to power the World Wide Web (QNX)
Dual HD cameras (3MP front cam/5MP rear cam)
Video codecs supported: 1080p, h.264, mp4, wmv
HDMI video out
micro USB + HDMI
Weighs < 1lb (400g)
Multitouch gestures (4 touch points)
802.11 a/b/g/n WiFi
Support for POSIX, Open GL, BB 6, WebKit, Flash, Java and AIR

The feature set alone should tempt you and if you're already developing apps with Flash Builder 4, PlayBook dev is as simple as adding another SDK in your config properties and setting up the VMWare simulator for testing. Once you're set up, create a new AS3 project and code away. When you compile your project, the AS3 is compiled into a SWF which is then converted to a BAR file before launching inside the simulator. There are even techniques to convert your APKs from your Android projects to the BAR format.

RIM is serious about helping you get started with your PlayBook development career. They’ve compiled a ton of resources to help you get up and running. Here’s a short list:

us.blackberry.com/developers/tablet/devresources.jsp
supportforums.blackberry.com/t5/Tablet-OS-SDK-for-Adobe-AIR/bd-p/tablet
devblog.blackberry.com
labs.adobe.com/technologies/flash/blackberrytabos
adobe.com/devnet/devices/articles/blackberry_tablet_os_sdk.html

And, RIM not only wants you developing applications, they want you earning money as well. Some of the features of their monetization program include:
- Carrier billing, credit card and PayPal in over 70 countries and 21 currencies
- 70/30 revenue split (70% Developer/30% RIM)
- In-app payments (unlockables, powerups, etc)

They’re also arming you with an integrated advertising service that allows you to earn even more revenue from your PlayBook adventures. Here’s a brief overview of the ad service’s features:
- 60/40 revenue split (60% Developer/40% RIM)
- Ability to leverage RIMs existing vendor network to get you earning more ad revenue faster
- Maintain full control over which ads you want to display
- Benefit from an open/transparent platform whose goal is to enable devs to generate revenue

Now, if you’re still undecided, RIM is even offering a FREE PlayBook. That’s right FREE!! Full details here. The basics are create a PlayBook app, submit it to BlackBerry AppWorld and once it’s approved, you’ll get a free PlayBook when it ships!!

The excitement surrounding the PlayBook is most definitely brewing so, I strongly encourage you to take advantage of RIM’s generosity to join the forefront of this new mobile application revolution.

PROS

• Support SVG + HTML 5

- canvas
- scaleable
- accessible text

• Generate CSS3
• Live, selectable text

- use JS to manipulate

• Lots of power to chop up designs (think PS slices)
• CSS Export!!! (Export Selected as CSS)

- export object
- export object styles
- export text styles via Character Styles tab
- export gradients!!

• Link to exported CSS via DW
• FREE download from Adobe Labs on 9/13 (Get it Today!!)

CONS

• Doesn’t generate HTML; just CSS
• IE9 can render natively; older versions have to use a plugin

Would write more but I’m anxious myself so I’m off to install my copy and start creating!!!

Dear Steve,

After reviewing your recent comments regarding Flash and the recent amendments to the Apple Developer TOS, I decided to share with you my response to a few of your positions. First, with regards to 3.3.1, Apple should only do QA based on app quality and NOT on app origin. Are we to seriously believe that an iPhone app built with Unity, Flash, etc. pails in comparison technologically to one built via Xcode? Are we to further believe that there are ABSOLUTELY NO poorly written Obj-C apps in the app store? If so, where are the benchmarks and metrics to support these claims?

Logical decisions are typically made based on data collection in some form or fashion. In the absence of such information, those “logical” decisions are eventually revealed to be more subjective in nature vs. being purely objective. Again, if there is data to support the claims against iPhone apps developed in Flash and compiled to *.ipa, please point us to that data.

Now, as to your assertion that Flash is the #1 reason Macs crash, again, we’d like to see empirical data that supports this claim. Having used apple desktop and laptop computers for more than a decade, I’d have to respectfully disagree with you. I’ve personally experienced kernel panics resulting from locked up processes with non-Flash applications (eg, iTunes, Safari, etc). To my knowledge, iTunes makes no use of Flash but yet it has caused my system to enter into a kernel panic on several occasions. Are we still to believe that Flash is the only big bad wolf lurking in the OSX forest? I seriously hope that’s not your intention. Will your position change when Adobe produces a Flash Player version that takes full advantage of hardware acceleration? I certainly hope so because then we’ll know that you’re truly the visionary tech leader that we all hope you to be.

Does this absolve the Flash development community from doing our part to improve the situation? NO!!! Unfortunately, many Flash apps are created by would-be developers that have no clue about memory management, garbage collection and the like. It is far too easy to create Flash apps that consume all of a browser’s memory, don’t close properly and eventually obstruct a user. But, I submit that this same fact holds true regardless of the language or platform used to create said applications. In other words, sloppy coding is the problem not the technology. This is from the perspective of a developer fluent in several languages including Obj-C and ActionScript.

I understand you have your business goals and a board of directors to please, but I implore you to work with Adobe rather than against them. Work with Google, Facebook and the like to make the future of technology truly open which benefits us all. Ultimately, we MUST support a free market economy in order to achieve this technological utopia, the results of which will be exponential growth that lasts for a millennium. Yes, it truly can be that explosive. The only thing standing in the way is our present day greed for money and power.

I sincerely hope that you soften your stance and work with the other technology leaders to usher us into that state of tech bliss…

P E A C E

Hasan

First, this will be a rather lengthy pictorial of the last few days here in Amsterdam. For those that have never been, I’ll also share my insights and tips on visiting the city since I’m a seasoned pro now, LOL (4th time).

The City

Amsterdam is a really cool city. It hasn’t changed that much since my last visit about a decade ago. It has a good mixture of rustic Old European charm and 20th century modernism. It’s almost as vibrant as New York City but tends to slow down during the week around 2am

The locals are generally friendly and often find amusement in the confused faces of the American tourists. This is also definitely a bike-friendly city with a lot of the population opting for beach cruisers and mopeds over cars.

The city is filled with quaint little coffee shops, bars and restaurants where one can enjoy an evening of good conversation and more with friends.

Having traveled abroad during an era when technology wasn’t as prevalent, it’s always amazing to see how it has become so deeply integrated into the fabric of life. On that note, if you have an iPhone, (2) useful apps to have are ATM Hunter and Amsterdam GPS Guide. Both are free and can save you a considerable amount of time. ATM Hunter helps you to locate the nearest Geldautomaat so you can gain access to some local currency. Amsterdam GPS Guide provides offline maps for you to use to scour the city. These free apps will have you motoring about like a local in no time.

Here’s a list of some places, in no particular order, worth checking out when in Amsterdam:
- Kadinsky’s (several locations)
- Abraxas
- Supper Club
- Chipsy King
- Renee’s Croissants
- The Greenhouse
- Coffee Shop Reefer

Amsterdam also has its dark side so enjoy but be wary of your surroundings always. While you’re busy watching the sites, someone is always watching you. Should you feel drawn to de Wallen (RLD), try visiting first during the day then return after 10p when it comes to life. DO NOT take pictures of the girls in the windows and if a local approaches you talking about a “party”, politely tell him no thanks and keep moving (either dealer or thief).

Now, these are just a few of the things I’ve come to learn about the city over the past 2 decades of visits. Hopefully they’ll be helpful to 1st timers or those who have visited previously but a lot of time has passed since their last visit. If you think I’ve got it twisted, let me know.

The Conference

FITC was filled with many amazing presentations and workshops. Everything from audio to video to 3d to converting images into sound and even workflows for building iPhone apps with the forthcoming Flash CS5. While the general consensus was that the entire conference was outstanding, the talks by Mario Klingermann, Jared Tarbell and Ralph Hauwert seemed to rank high as the crowd favorites. Additional talks that peeked my interest were Joa Ebart’s overview of his open source project and Sam Agesilas’ preview of the forthcoming Orchid open source framework.

The Fellowship

This alone is worth the price of admission + trip. Being able to hang out with industry geniuses after all the tension of putting on a successful conference has passed is priceless. The post-conference wind down is often just a continuation of the past days’ events but in a much more relaxed and social environment.

Here we’re at the Hotel Ambasade participating in a linkup w/Flash Brighton hosted by Seb Lee-Delisle (a/k/a “Awesome”). Pictured from left to right are Jim Corbett, Grant Skinner and Sam Agesilas discussing the mobile platform.

Later on, Ralph Hauwert chimes in on a response to a question from the Flash Brighton group.

Stacy Mulcahy and Masakazu (Mash) Ohtsuka patiently awaiting their turns to share in the discussion.

Influxis co-founder, Richard Blakely, and Seb discussing Rich Media.

Adobe’s Lee Brimelow and Mike Chambers arrive on the scene to share in the festivities.

The evening was definitely off to a good start. Later that night, in a dark, subterranean and smoke filled room, the leaders of the Flash community gathered to pontificate further on the future of the Flash platform. Sorry, can’t show those pictures as I’m under an NSTPA…;)