Flash Platform Discussion follow-up — news and some philosophy, too

Posted June 9, 2005 4:52 pm
Filed under: ActionScript, Articles by Paul, Flash, Opinions

Yesterday I attended Macromedia’s Flash Platform Live Discussion and Q & A session hosted by Kevin Lynch. I expected the aggregators to light up with posts during/after the presentation, but things were pretty quiet — I have only found one follow-up post so far. Personally I had to get back to other projects at work, and wanted to take some time to think about things a bit before giving my thoughts. So here they are, in three parts:

  1. The presentation
  2. Juicy news (things I hadn’t read anywhere else)
  3. Why was this meeting held, again?

The presentation

First of all, if you weren’t at the meeting and want to know what was said, I would strongly suggest that you read Kevin’s whitepaper about the Flash Platform — his presentation (text and slides) were almost 100% out of the whitepaper. This surprised me — are there really so few people who read the whitepaper? It’s a good, easy read — mostly stuff you may already know, but plenty of juicy bits about the various products that are in development/beta right now.

He started off explaining that what he would be sharing is a presentation they’ve been giving to analysts, with the goal of giving us (the audience) insight into how they’re communicating about the Flash Platform. In particular, the goal of the Flash Platform announcement is to try to change the perception of Flash from “a tool for animations” to “a development platform.”

As you can read in the whitepaper, the Platform is centered around the Flash Player (the “runtime” or “virtual machine” if you want to call it that). Building on top of that are the tools, servers, developer programs and components/patterns; and finally on top of it all are the solutions we build on the platform.

Personally I was pleased that Kevin gave a strong acknowledgement, both in the presentation and in the Q & A, to the importance of third-party tools to the platform. I think he’s right-on about this. Over the past several months I have seen that all the new tools that are being built to support developers, whether they cost money or not, have really ignited a new excitement for Flash developers. Personally I consider the MTASC compiler to be the most exciting thing for ActionScript since ActionScript 2.0 was announced. Even if these new tools mean that it may soon be (or is now) possible to create significant ActionScript-based Flash applications without needing to pay Macromedia anything, the net effect of having more and better applications out there will still be a benefit to Macromedia. Even if a really exciting Flash application is built entirely without using Macromedia products, it still runs in the Flash Player and the good press it generates will still be associated in the public eye with Macromedia and Flash.

Juicy news

For most people, I expect that the highlight of the meeting was probably the second part, which was an open question and answer session. I assumed that would mean“questions about the presentation” but the questions covered a pretty good range — mostly related to the future of various products, of course. It became apparent that a significant portion of the audience (or at least of those whose questions were picked to answer) hadn’t read the whitepaper — I would guess that about half of the questions that were answered by Kevin were already answered in the whitepaper. Another 20% or so of the questions were given the “sorry, we haven’t made that public yet” treatment. But there were still plenty of things that I hadn’t heard/read anywhere before, both in the presentation and especially in the Q & A, so here they are for your reading pleasure:

Note: any details about upcoming products that I had already heard somewhere else aren’t included in this list. That means previously announced details about the upcoming Flash Player/Studio releases and especially the plentiful new details in Kevin’s whitepaper. I suggest you read those, if you haven’t already. I have included a few points that I was already familiar with, simply because I think they are important ones to share.

Disclaimer: these are taken from notes I typed as I was listening to the presentation. They are most certainly not word-for-word transcriptions of what was said, and it is possible that any of them could be wrong!

Things that were new to me:

Why was this meeting held, again?

Ironically, the biggest question I had going in to the presentation was just “What’s the reason for this meeting? Why was this particular group of people (especially me!) invited to this ‘private’ meeting?” Fortunately, through a bit of luck my question was answered. After the presentation and questions, the “presenter chat” screen (which was apparently a private chat for the MM people right before the actual presentation began) was inadvertently left visible on the Breeze window. Right there in the conversation was a discussion about how many participants were expected, and one of the answers was that the entire Flash category of MXNA weblogs had been invited. So that was the big secret — I have a weblog that is aggregated by MXNA, in the Flash category, so I was invited.

Like so many questions, getting this one answered led to an even bigger question. Why were Flash bloggers (and presumably some others) invited to this special presentation on the Flash Platform? In the presentation Kevin explicitly stated that:

  1. He would be giving us a presentation that they’ve been giving to industry analysts;
  2. It represents how they’re communicating about the Flash Platform; and
  3. He acknowledged that most of the attendees probably already think of Flash as a platform and are familiar with most of the ideas in the presentation.

Now, I’m making some assumptions here, but I think that (just as Kevin suggested with point 3) in an audience that consists primarily of Flash bloggers, chances are

Which once again leads to the question, why give a presentation on “what is the Flash Platform and how is Macromedia communicating about it” to the people who are most likely (again, by Kevin’s own admission) to already know what the Flash Platform is, be firm believers in it, and be very aware of Macromedia’s communications about it? There is only one answer I have come up with (but please feel free to present alternative ideas in the comments).

Macromedia must think that we, the Flash bloggers of the world, have (at least potentially) big influence in spreading the word about the Flash Platform and what it can mean for application development. It makes sense, of course. Chances are good that a blogger is a person who likes to learn new things and especially likes to share them with others. The Flash community certainly isn’t shy about sharing information. Here’s our chance to (once again) open up and spread the word to bosses, colleagues, friends, etc. about the value of the Flash Platform.

Macromedia thinks we can do it! Pretty flattering. Now they’ve shown us how they’re communicating about it, and they’ve given us some great ammunition in the form of Kevin’s whitepaper. And they are “paying us in advance” so to speak by continuing to be even more open than ever about the future of the Platform and Macromedia products.

Anyway, enough sappy “rallying the troops.” Time to go find some more ammunition for sharing the benefits of the Flash Platform with the boss. Can I get my employer to pony up for a Flex license? I still have my doubts, but I feel newly motivated to go out and try. I have to admit, the Adobe buyout announcement came like a slap in the face, a reminder that Macromedia is a business and has to care about stockholders (even over customers). But today I feel like restoring a little credit to them for caring about their developer community, too.

You can leave a comment, or trackback from your own site.

1 Comment so far

  1. December 2nd, 2005 at 1:53 pm
    ouifm is reported to have said:

    That’s excellent news!

Add your comment





Comment notes

Please keep comments on topic. Comments that are inappropriate or offensive will be edited or removed.

Paragraphs and line breaks are automatically converted to HTML, and quotation marks are converted to “smart” quotes.

The following XHTML tags can be used: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> . All others will be removed.

Articles by Type

Articles by Topic

Random Reading

Currently...

Subscribe