Blog to discuss Midnight Coders products features, ideas and trends in development of Rich Internet Applications

Tuesday, October 24, 2006

Mindshare management: What Adobe could do next

Attending MAX has been a fantastic experience. Being here makes one realize how grand the opportunity Adobe has with Flex and Apollo. People familiar with Flx rave about it, its ease of use, and simplicity of development. However the number of people not familiar with Flex (based on the discussions I had here) is staggering, hence is my question: how can Adobe start winning the mindshare? Having developers mindshare directly translates to new applications written, which inherently effects the bottom line. Very few software development companies really mastered how to inject information about tools and products or just ideas into developer heads. Microsoft in particular knows how to do it really well. So what could Adobe do:
  1. Position Flex and Apollo as the focal point of the Adobe's 'development tools' product line. Right now these products are just one of many. For example, the both for Flex and Apollo at MAX is for some reason on the outskirts of the exhibition floor.
  2. Make the Apollo buzz more 'material' by releasing an early alpha or a preview of the product, let people experiment with it.
  3. Embrace other development platforms and make them equal from the backend support perspective. Exclusivity with Java is not a winning strategy.
  4. Stop comparing Flex with Ajax. The "Go Beyond Ajax" ads do not accomplish anything. I think comparing it with something like ASP.NET or WPF would be a lot more effective.
  5. Do grandiose marketing campaign. Remember Microsoft's tv ads for .NET? :)
  6. Get community portal going. Yes, there is flex.org, but its mostly a reference site with a bunch of [helpful] links, but not more than that.
  7. Engage development community with app development contests. Something like Flex Derby should be an ongoing contest with winners selected monthly or quaterly.
  8. Expose and standardize proprietary protocols: AMF0, AMF3, RTMP, etc.
I am sure there is more. If I can think of any additional ideas I will do a follow on post.

7 Comments:

Anonymous John Farrar said...

Yes, you got some good points there! Don't compare... rather teach and build the community!

8:51 PM

 
Anonymous Anonymous said...

Not comparing to AJAX is big. AJAX is so far behind Flash, it is silly to give it credit. With ActionScript 3, you gotta figure the HTML/JS world is never gonna catch up technologically.

11:14 PM

 
Anonymous bigred said...

I search for Apollo both on Adobe and Adobe Labs Web site. What I get back as search results is an endless list of Apollo font descriptions. So please tell us what Apollo is and what it provides.

6:14 AM

 
Anonymous bigred said...

Mark,

I totally agree. Adobe is doing a lousy job of marketing Flex. Comparing and integrating with Ajax is a total waste of time. Instead spend marketing bandwidth on Flex 2 developer productivity and the killer Rich Client apps one can create--to say nothing about no cross browser layout compatibility issues, etc.

And yes, expose and standardize proprietary protocols: AMF0, AMF3, RTMP, etc. Not a good move to keep these closed. If these were open, it would be to Adobe's significant advantage.

6:24 AM

 
Anonymous John Dowdell said...

"bigred", a Google search on term "site:adobe.com apollo" turns up the most useful links in the top positions:
http://www.google.com/search?q=site%3Aadobe.com+apollo

It's a browser-independent, OS-independent clientside runtime environment.

Most formats are "open". Some are licensed from other companies and are not. You do not need source-level manipulation of all formats to reap the benefits, just as you do not need to be able to rewire the logic of other people's CPUs to work effectively with computers.

6:25 PM

 
Anonymous Mike Chambers said...

Apollo is the code name for a cross-operating system runtime being developed by Adobe that allows developers to leverage their existing web development skills (Flash, Flex, HTML, JavaScript, Ajax) to build and deploy Rich Internet Applications (RIAs) to the desktop.


You can find info on Apollo here:

http://www.adobe.com/go/apollo

mike chambers

mesh@adobe.com

7:23 PM

 
Blogger Gosh! said...

#3 bears repeating: Embrace other development platforms and make them equal from the backend support perspective. Exclusivity with Java is not a winning strategy.

11:22 PM

 

Post a Comment

<< Home