Skip to page content or Skip to Accesskey List.


Main Page Content

Macromedia S Struggle

Rated 3.09 (Ratings: 23)

Want more?

Picture of DevilM

Matt Liotta

Member info

User since: 11 Mar 2002

Articles written: 6

Macromedia started out as a developer of animation products for the CD-ROM world only to find that market being quickly replaced by the burgeoning World Wide Web. Their product line was quickly changed to attack this new market. Two of the products it introduced, DreamWeaver and Flash, became the most widely used products in their respective categories. More recently, Macromedia acquired Allaire, which brought with it three important products: HomeSite, ColdFusion, and JRun. HomeSite, like DreamWeaver, was the most widely used product in its category and seemly competed with DreamWeaver. ColdFusion and JRun were both pioneers in the Web application world that had strong followings. These five products effectively guaranteed Macromedia a spot on almost every Web developer’s desktop, and in some cases, their servers as well.

However, the heady days of the dot-com boom were ending, and Macromedia’s balance sheet wasn’t pretty.

J2EE Proved to Be a Stiff Competitor

While the Flash player was having unparalleled success, sales of Flash the application and DreamWeaver were down. At the same time, the industry was standardizing on J2EE, and ColdFusion was suffering as a result. Furthermore, JRun wasn’t competing that well. This all left Macromedia with a fat payroll and suffering sales. What they needed was a way to make ColdFusion competitive, a way to generate revenue from Flash, and, of course, cut costs. The solution the company saw was the MX product line.

Their first step was to rebuild ColdFusion as an application on top of J2EE. This allowed Macromedia to maintain a single application server (JRun) instead of two as well as make ColdFusion competitive with the rest of the J2EE market. Next, they extended Flash to become a complete GUI toolkit, allowing it to emerge from its days as a simple animation plug-in. Thus, Flash fulfilled the undelivered promise of Java applets; a cross-platform browser based GUI platform.

Finally, they built support for Web services into Flash, ColdFusion, and JRun. With support for Web services, Flash developers could build GUIs for Web applications without worrying about back-end integration. Further, ColdFusion and Java developers could build back-end services with Flash as their presentation tier instead of HTML. Macromedia coined the term Rich Internet Application for applications, based on the integration of Flash with a back-end based on Web services.

Macromedia is back in the black now, but apparently without much help from their new MX product line, which to date has generated only lackluster sales. The Flash and ColdFusion communities are abuzz with excitement over the new capabilities of these products. However, all is not right at the top for Macromedia.

Why Macromedia’s Own Employees Are Squabbling

The Flash community--dominated by designers--is having a tough time adapting to the object-oriented approach of developing with Flash MX components. This leads to a realization that while the new capabilities of Flash are quite exciting, you have to be an engineer to make use of them. Worse, the ColdFusion community is having a hard time accepting ColdFusion MX. The promised backward compatibility is only superficially there; the syntax is backward compatible, but the behavior is often not. Also, to make use of Web services and integrate with Flash requires an understanding of object-oriented concepts most ColdFusion developers have been able to avoid. This is made absurdly obvious by Macromedia’s own employees; those with object-oriented backgrounds often can be seen squabbling with those who don’t on various public mailing lists.

Also of note is DreamWeaver MX, which replaced not only the previous version of DreamWeaver, but also HomeSite. Much to the chagrin of Macromedia, neither former DreamWeaver or HomeSite users have been excited by the latest offering. The complaints range from it being buggy to slow to just too much. What is clear is that people who formerly bought DreamWeaver for its Web-site design functionality aren’t too interested in a back-end development IDE, while the people who formerly bought HomeSite for its plain and simple tag-based text editing aren’t too happy with the overhead of a full-on Web site design tool.

A person might also ask what Macromedia’s true focus is these days. From all indications, it is Flash, while many might argue it should be ColdFusion, because Flash’s revenue-generating potential is significantly smaller. Their latest developer convention also shows their bias toward designers, because most of the sessions are not meant for developers.

Maybe it is simply that Allaire spent a great deal of energy on the ColdFusion community, and things just aren’t the same with Macromedia. It’s hard to say, because there does seem to be more community participation from Macromedia, but it doesn’t seem focused or well organized. In fact, a person could find one’s self both praised and criticized by different members of the company. Some have even gone as far as penalizing people who ask hard questions publicly (e.g. removal of beta access).

It’s Not Too Late for the Company to Change Direction

No one can deny that Macromedia is a significant player in the Web industry and has the attention of many Web developers. The question is whether Macromedia has climbed to the top only to fall because they are forgetting the very people who got them there.

The MX product line holds great potential, but its managers need to better take into account what the users are saying. We are excited by the promise of the MX product line, but we want good products and a company committed to them. That company could be Macromedia, or it could be the next company that wants a shot at the top.

Will Macromedia’s struggle to the top ultimately be for nothing? Only Macromedia can decide.

Matt Liotta started his development career at the age of twelve by building C applications for faculty at Emory University. He built his first web page soon after the release of Mosaic 1.0. Excited by early web applications, Matt saw the potential to replace legacy client server applications. At Emory University he built an enterprise calendaring system, the faculty poster project, a Y2K compliance tracking application, and a prototype for an electronic research administration system.

Since then he worked with an early ASP, Cignify, to build their transaction processing system for payroll time data. For this project, Matt created a message queuing system to connect significant bodies of code in C++ and VB with the main application server. He also built a code distribution system for Consumer Financial Networks, as well as the first online account management system for Grizzard Communications. Matt did consulting around San Francisco for companies such as Williams Sonoma and Yipes Communications.

Soon after, he built gMoney's Group Transaction System using an innovative XML messaging architecture for ColdFusion that matches conceptually with the now popular web services paradigm. He also wrote a C++ knapsack algorithm to realize nearly a 20-fold improvement over a similar approach written entirely in CFML. Later at TeamToolz, he designed a highly secure and scalable network architecture for ColdFusion to support N-tier transport agnostic distributed applications. He then went on to implement a cutting-edge content management system for DevX. He is now President & CEO of Montara Software, which he recently founded.

Matt is also a frequent speaker on web architecture:

  • Moving Legacy Applications to the Web (Emory Web Developers Users Group, Atlanta --Feb, 98)
  • The Benefits of Web-based Enterprise Calendaring (Emory Web Developers Users Group, Atlanta -- Aug, 98)
  • Monitoring and Managing Services Remotely Using TAPI (Atlanta Visual Basic Users Group, Atlanta -- Nov, 99)
  • Scalable, Extensible Cold Fusion Architecture (Bay Area ColdFusion Users’ Group, San Francisco; Aug, 00)
  • Scalable, Extensible Cold Fusion Architecture II (CF_Scale Conference, Washington, D.C. -- Nov, 00)
  • Cold Fusion Scalability Panel (CF_Scale Conference, Washington D.C. -- Nov, 00)
  • Introducing CF Espresso (including white paper) (CF_South Conference, Orlando -- Feb, 01)
  • Utilizing Reverse Proxies (Web Services World, San Jose -- Apr, 01)
  • Cold Fusion on Linux (A CF Odyssey Conference, Washington, D.C. -- Jun 01)
  • Architecting Web Services (Web Show 2001, San Francisco -- Sep, 01)
  • Code Techniques in MX Panel (Bay Area ColdFusion Users' Group, San Francisco -- Jul, 02)
  • ColdFusion Cruise, May, 03

The access keys for this page are: ALT (Control on a Mac) plus: is an all-volunteer resource for web developers made up of a discussion list, a browser archive, and member-submitted articles. This article is the property of its author, please do not redistribute or use elsewhere without checking with the author.