Chasing success on the web at Adobe
Published: 05 Oct 2007 14:25 BST
…it's not like there's going to be an overnight shift from the way we currently build software. But you'll start seeing new products built for the web that draw from that heritage.
So for example with Premiere — it's a great video-editing tool built on the classic way of a software package that you get in a box. We are now hosting Premiere on the web so you can go to YouTube and Photobucket... That's branded Premiere Express. The Premiere team is building it, they're using web technologies [like scripting languages] to build it.
Same with Photoshop. Our chief executive Bruce Chizen mentioned that we're working on Photoshop Express, [which is] very similar to Premiere. So you'll see a lot of that happening from us.
You'll see AIR, for example, start to be used in some of our software in different aspects. Maybe you like using Premiere Express — you don't need all of Premiere, yet you want to put it on your desktop. That could be a bridge... That's not something we're currently doing, but you can imagine us doing it. There will be a spectrum.
What's the business model behind these hosted applications?
Well, with Premiere Express, it's an ad-share model. The site that it's hosted on, it's advertising-supported and we share in that revenue for people who are spending time using the Express editor. So ad-supported, subscription-based — all in new ways that people are monetising software.
How do developers make use of these web services?
We're going to make a bunch of APIs to these services available to integrate things like voice into your application. With Share, for example, there is a document repository, file repository that we're hosting. Everybody's got a free gigabyte of space, and there are some web APIs that anyone can use to access and make use of a data store. So you can build a file-browsing user interface or you can build your own image editor and use Share to hold the documents behind it. Developers can do whatever they like to make use of that — there's just APIs available.
On the business side of that, there is an amount of free storage and, beyond that, we will provide premium services that could have revenue associated with them either through ads or subscriptions and models like that.
Read this
Leader: Adobe's price isn't right
Adobe expects Europeans to pay twice as much as American customers for the most comprehensive Creative Suite 3 package. That's a pricey expectation…
You are doing a lot more in tools and, of course, Microsoft is very strong in tools and they're doing more with web development as well. How do you compete with that big machine over at Redmond?
We've actually had a long relationship with Microsoft. So there are areas where we co-operate in their areas; where we compete we are one of the biggest software vendors on Windows in the world.
The areas that we do compete, in web tooling for example, we've been competing for a long time. In the early days of web authoring, I worked on the Dreamweaver project at the time and we were basically last to market. FrontPage was already out; there were already a dozen tools already out there. None of them had really had gotten predominance or really popular with pro web developers and there was an opening for us to do that. We got in and designed a tool that really resonated with a community. We listened well and fed that feedback in. That managed to get an incredible level of popularity really fast. What we saw there was great success with Dreamweaver with pro web developers that beat FrontPage and other tools.
So even though Microsoft works on software, they don't always win in these markets. From what I've seen in these situations, you just have to be close to the customer, not be distracted by what the competition is doing in terms of trying to catch up with you or whatever, and stay on the leading edge and think about the next thing that is happening. And let the competition chase where you've been.
For us in the rich-internet-application space, that's brought us more into developer tools. Things like Flex Builder — that's a new tool for us and it's doing very well. We've made the Flex Framework open-source and free. A lot of the frameworks for the web now, of course, are free and open-source. So to play, that's kind of the table stakes. So we've anted up.
Thermo [a planned tool to let designers write their own web applications] got a lot "oohs" and "aahs" from attendees. But people have been trying to make development tools for people who aren't programmers for a long time, probably as long as code has been around. What are the limitations there?
I know! But we're not doing a general solution for anyone to build an application. That's one of the key things — we had to be specific…











