Adobe Steps up to the HTML5 Design/Development Plate with Edge{1}

by Robert M
In this article, Wired’s Tim Carmody, starts by giving a brief history of Adobe’s relationship with the Internet. Specifically the importance of Flash for a long period of time, and it’s subsequent downfall in recent years as a result of both the mobile web, and, by extension, HTML5. The impact of the mobile web and it’s lack of support for flash were highlighted more so than creation of HTML5 itself, though obviously HTML5 is a big part of the equation. Afterward, Carmody goes into a preview of Adobe Edge, the new platform being developed to cover up Adobe’s lack of mobile web presence. The program was very early in the development cycle last August when the article was written, but version 1.0 is set to ship sometime this year. Carmody wrote that “the Company’s not even calling it a beta. It can’t do much right now other than simple animations.”  Though he adds that by release it aims to be substantial enough to “potentially be equivalent to Flash or Dreamweaver.” As the lack of mobile platform is Adobe’s biggest weakness at this point, Edge is almost completely focused on mobile development, with desktop development being “almost an afterthought.” Lastly, Carmody states that the program is not made to be an extremely extensive tool for hardcore developers. Instead, it is focused on “the not-so-hardcore web developer, the designer who needs to publish on the web.” (Carmody, 2011)

Our discussion of the various versions of HTML in class this week is the most obvious connection to the content presented above. However, I think even more important than simply the presence of a new HTML version is its effect on both the business and development side of web development. HTML 5 has been a long time coming, and Adobe’s failure to get on the ball with adequate time is causing them to shift into high development gear in order to get up to speed with the market. As someone who has used Adobe software extensively since High School, I would hate to see them get left behind, as I trust they can put out a good product (except for Acrobat reader. Those updates…).

On the other hand, if they throw out cobbled together mess of a program in attempt to get it out as fast as possible, they’re going to be putting themselves in an even worse position. I think that the program being targeted toward designers who don’t want to use Javascript, CSS, or HTML extensively makes the program more marketable, but it may alienate experienced developers who have a strong grasp on what features they want/need


Carmody, Tim. (2011). Adobe’s New HTML5 Tool is Web-Designer Duct Tape. Wired