eWeek Microsoft Watch
Advertisement
Advertisement
March 10, 2008 2:03 AM

What Does Microsoft's Expression Mean?



Joe Wilcox
Joe Wilcox

News Analysis. One analyst suggests that Expression Studio 2.0 got the short shrift during last week's MIX08 keynotes. He's probably right.

Microsoft spent a whole lot of time evangelizing Silverlight, clearly as an attack on Flash. But development/design software Expression got a big version two-oh beta release that pretty much anyone can download, but not much talk about it—at least during the MIX keynote.

The beta is big news itself. For starters, Microsoft just made Expression Studio free to anyone during what could be a long version 2.0-2.5 beta process. Already, at $320 street price upgrade and $500 full version, Expression costs less than Adobe's Creative Suite 3, which street price ranges from about $399 for Design Standard upgrade to more than $1,700 for Design Premium. Sure, Microsoft will eventually charge for the final product. Meanwhile, it's a free—and impressive—alternative to CS3 or to Expression 1.0, for that matter.

Chris Swenson, NPD's director Software Industry Analysis, said there was too much for Microsoft to squeeze into the main MIX08 keynote. He sees the Expression Studio 2.0 beta and three of its benefits as being hugely important but too overlooked:

  • Silverlight 2.0 integration
  • PHP support
  • .NET 3.5 support

The beta Expression Studio release, combined with Visual Studio 2008, gives designers and developers tools for immediately trying out Silverlight 2.0. They can do so using either development tool.

Swenson said that PHP support in Expression Web 2.0 "is a huge, huge deal. How much PHP support? Enough to cover about 80 percent to 90 percent of the usage scenarios in my estimation."

Swenson described the PHP support as an "incredibly large first step. There are so many Web designers and developers that use PHP that Expression Web 1.0 wasn't included in their consideration set." PHP support gives more developers and designers reason for "kicking the tires of Expression Web."

Microsoft provided full beta software for them to do just that.

"The support for .NET 3.5 is a big deal, too, because of the improved support for AJAX, Swenson said. "There are so many RIAs [Rich Internet Applications] built with AJAX today, and it's going to be that way for many years to come. The improved support for AJAX will lead many developers to adopt Microsoft's tooling to develop their AJAX RIAs, irrespective of Silverlight."

.NET is, after all, the centerpiece of Microsoft's Web services strategy.

Swenson also emphasized the importance of what comes next. He observed that "it's been 10 months since Expression Studio 1.0 shipped, and already we're talking about Blend 2.5."

He emphasized: "Microsoft said that they are committed to innovating on a 12-month release cycle so they can rapidly close the feature gap with Adobe, and so far, they are delivering on that promise. Adobe, with their 18 month or so release cycle for its CS products, can't innovate as rapidly."

The lead up to the one-dot-oh release took longer. Microsoft purchased the core Expression product from Creature House in second half 2003. First beta, codename "Acrylic," released in summer 2005. A few months later, Microsoft officially announced its Expression family of products. In summer 2006, Microsoft purchased iView Media, which became Expression Media (other suite products are Blend, Design and Web). Expression Studio released to manufacturing a year ago at MIX07.

Swenson said that Microsoft's rapid-fire Expression development may do to Adobe what it did to Quark. After Quark's late 1990s failed Adobe takeover, Adobe made a push back into the design market with the 1999 release of InDesign.

"Quark was taking forever with their releases, especially when it came to supporting Mac OS X [in 2001], and Adobe adopted a rapid development schedule to quickly close the gap between InDesign and QuarkXPress," Swenson said. "By all accounts, Adobe succeeded, pushing out one release after another."

In making Adobe-Microsoft comparisons, the NPD analyst acknowledged the difference in release cycles—about 18 months for InDesign versus several years for QuarkXPress.

"I think you're seeing Microsoft emulate a tried-and-true strategy in the professional graphics software market: Adopt short release cycles, innovate rapidly [and] close the feature gap as quickly as possible," Swenson said. "It's what you have to do if you want to succeed." It's a "very smart strategic move in my opinion."

Create, Communicate, Collaborate with IT Professionals at Ziff Davis Enterprise IT Link.

TrackBack

TrackBack

http://www.microsoft-watch.com/cgi-bin/mte/mt-tb.cgi/12971

Comments (4)

Gerardo Tasistro :

Microsoft is clearly in a "me too" mode this year. I'm not particularly impressed by what I'm seeing either. They are playing catch up and Swenson's words prove it. Adobe doesn't need a 12 month cycle because they are in the lead. Microsoft needs it so it can offer, in a year or two, what Adobe has today.

There are a few comments/questions I'd like to make on this product and your previous post on Silverlight.

1) Microsoft is a marketing company and has no software development creativity. If they did have why would they be playing catch up to Adobe? More important than that is where will they go once they do catch up to Adobe?

2) What will happen to the 12 month release cycle after they catch up? Will it become a 72 month release cycle like it was with Internet Explorer after it "caught up" to Netscape?

3) What is the impact of a 12 month release cycle on productivity? We know very well how Microsoft just remakes their products and sometimes (most times) they are not very backward compatible. Say you make your site today with the current version. How will it break in 12 months when the new "Expression" comes out? How much time will it take you to fix it?

4) Microsoft with all their nice talk is leading us to believe that somehow for them the desktop is no longer relevant. There is nothing more distant from the truth than this. They can not and will not let their flagship products (Windows/Office) become irrelevant. Thus Silverlight, Expressions and all their software stack will continue to be Windows and Intel centric. To embrace such technologies is to limit ones flexibility in regards to platforms. I can not believe Microsoft's talk about mobility, communication and communities while their software platform is so centralized in a heavyweight like the PC.

readr :

@Gerardo, if you read the IE team's blog, the "72 months" you refer to is due to the IE team working on WPF. It was a big reboot for them -- they weren't idly sitting around, contrary to popular opinion.

Gerardo Tasistro :

@readr, regardless of the reason they didn't work on IE my perception as an end user is that of no improvement over a 72 month period.

portuno :

Wait a minute. Microsoft has only one team of developers? In other words, they have only one group of people qualified to work on one project until they finish that and then they can work on the other project?

There's so much simplistic BS floating around justifying Microsoft's many failures to ship any next-generation products it's getting hard to read this stuff with a straight face.

" It was a big reboot for them -- they weren't idly sitting around, contrary to popular opinion."

I nearly blew my Costco bottled water out my nose when I saw that.

You do realise 72 months is 6 years, right?

You do realize MSFT claimed Longhorn and WinFS and all their other next-gen XML work was almost complete? What needed to "reboot"? Did Microsoft suddenly realize they could not rightly claim ownership of IP that was the foundation for all their work?

No? Then, come up with a better reason and please make it something an adult with average intelligence will believe.

Post a Comment

 
 


RSS Syndication
Advertisement
Advertisement
Microsoft Watch     Contact Us | Advertise | Site Map
Ziff Davis Enterprise

Ziff Davis Enterprise Home | Contact Us | Advertise | Link to Us | Reprints | Magazine Subscriptions | Newsletters
RSS Feeds | White Papers | ROI Calculators | Tech Podcasts | Tech Video |

Baseline | Careers | Channel Insider | CIO Insight | DesktopLinux | DeviceForge | DevSource | eSeminars |
eWEEK | LinuxDevices | Linux Watch | Microsoft Watch | Mid-market | Networking | PDF Zone |
Publish | eWeek Security | Strategic Partner | Web Buyer's Guide | Windows for Devices

Developer Shed | Dev Shed | ASP Free | Dev Articles | Dev Hardware | SEO Chat | Tutorialized | Scripts |
Code Walkers | Web Hosters | Dev Mechanic | Dev Archives | IT Marketplace | igrep

Use of this site is governed by our Terms of Use and Privacy Policy

Copyright ©1996-2007 Ziff Davis Enterprise Inc. All Rights Reserved. Microsoft Watch is a trademark of Ziff Davis Enterprise, Inc. Reproduction in whole or in part in any form or medium without express written permission of Ziff Davis Enterprise Inc. is prohibited.

Ziff Davis Enterprise