With responsive web design, designers and developers can embrace this inherent fluidity from the ground up. As the size of the browser window changes, the content can simply reflow, resize and re-position itself on a sliding scale from the smallest phone to the largest desktop computer.

An example of responsive design. The look of the site changes to fit the visitor's resolution.

My colleague, Kent Rahman, recently authored a great eGuide explaining this approach and providing some guidance around the topic. I would encourage you to download the eGuide today and read more about how you can create engaging experiences for the desktop, web and everything in between.

Check out our own INM.com website for a live example of a responsive design. Our site is built to work on virtually every device, from a mobile phone through to a desktop screen.

A few months ago, USA Today speculated that Apple would become the first $1 trillion company. Earlier this week, Apple made great strides toward this milestone when it surged ahead of ExxonMobile Corp to capture the title of world’s most valuable company.

Whether Apple lives up to this prediction or not, it has already achieved what seemed impossible. The company saw a 300% increase in stock price in less than three years, in a very difficult economic climate.  Today, Apple exceeds Microsoft in market capitalization ($213 Billion for MSFT vs $302 B for AAPL) although, just 14 years ago, Microsoft had to inject $150M into its bank account to keep from going out of business.

These facts are extremely unlikely and unpredictable, but don’t come as a surprise to anyone who has observed the last few decades with objectivity and, amongst other trends, paid attention to principles such as The Black Swan: The Impact of the Highly Improbable.

The most remarkable observation of all, in my opinion, is that Apple achieved this overwhelming success using the exact same strategy as the one used the 80′s with the Macintosh. The company continues to design technologies that best interface with humans and thus empower them in their ability to learn fast and feel gratified by increased accomplishments and productivity. This is the essence of addictive technologies and products; concept that Apple has mastered. The first buyer is already standing in line for the iPhone 5 – a product that has yet to even be announced.

In other words, Apple remained firm on its course to cater to fundamental human needs and instincts: It’s the world that has evolved around it.

The interface borrows heavily from the Flash UI.  So Flash users will be up and running in no time with Edge.  There are five main panels: Tools, Properties, Elements, Stage and Timeline. 

Elements are added to the stage either by creating them from the tools panel, or by import (SVG, PNG, JPG, GIF).  For now the tool set is limited to text, rectangle and rounded rectangle but that will certainly expand as the product develops. 

Animation within the UI is done using keyframes and tweens that are graphically represented on the timeline.  Unlike Flash however, tweens are generated automatically between two keyframes, and the concept of “blank” frames is removed entirely. You can also select and modify the length of all the tweens for one element simultaneously, something that I found myself using constantly.  Layers have changed as well, with each element in the animation becoming its own layer, so no ability to create empty layers and group elements at all.  The result is a greatly simplified and streamlined experience.  Think of it as Flash lite.  We’ll see how this handles the increasing complexity of successive releases, but for now it works quite well.   Within a few hours I was able create an animation that would have otherwise taken much, much longer had I coded it by hand.  In this respect, Edge is already on the right track.

The animation is rendered using JSON, the JQuery javascript library and CSS3.  Despite being billed as an HTML5 tool, Edge doesn’t generate HTML5 code at all.  That means no SVG or Canvas (you can import SVG, however).  According to Adobe support for HTML5 animations will be included in future releases. 

One of the major drawbacks in this release is that Edge outputs non-semantic HTML.  For example, there is no way to assign <p> or <h1> tags from within the UI.  All elements are wrapped in meaningless <div> tags, to be manipulated externally via Javascript.  This poses a number of problems in terms of accessibility, browser rendering, validation and SEO.  According to Adobe, they are aware of the problem, but chose to sacrifice semantics in order to get this version out quickly and accumulate feedback.  We’ll be following closely, as this is certainly a deal-breaker in its current form.

Another important feature that didn’t make the cut is interactivity.  Currently there is no way to add links or other interactive elements to your animations without modifying the Edge-generated code externally.  Again, this being only a limited preview, we can certainly expect to see this functionality added as development continues.

Since Edge uses the latest CSS3 animations, only newer Webkit browsers and mobile devices can render the output.  This means no IE support below version 9, making its use impractical for most production scenarios today.  That being said, this puts Adobe in a much better position moving forward, as more and more people adopt standards friendly browsers.

Despite the drawbacks, Adobe Edge is an important first step towards a future of cross-compatible, standards based web development.  It will be interesting to see how Edge will be incorporated into the Adobe family; whether it will be released as a stand-alone or simply amalgamated into future products.  And let’s not forget about poor old Flash.  What impact with this have on Flash in the long term?  Is this a signal that Adobe is ready to transition away from one of their core products, or perhaps narrow Flash’s focus into an area where it can maintain its competitive advantage, like gaming, for example?  In any case, there’s no question that Edge has the potential to be a game-changer.

With the introduction of Edge, Adobe is taking a huge step outside its comfort zone and embracing a vision of the future of the web that many people have been advocating for quite some time.  Let’s hope that they continue moving in this direction.

A few weeks ago, WordPress announced that it was dropping support for Internet Explorer 6. For now, this will only affect blog writers and publishers, but this could soon affect viewers and readers of these blogs as well.

WordPress is definitely not the first to make this kind of announcement. Google announced that it will not support IE6 when it makes new improvements to its YouTube, Gmail Notifier and Google Docs services. Facebook, White Pages, Digg and many more sites are also on-board.

Microsoft, the maker of IE6, has been actively promoting its website http://www.ie6countdown.com to encourage and explain why people should move away from the browser. IE6 is two-months short of its tenth birthday, making it a real relic in a technology landscape where new browser versions are announced every 3-4 months. In fact, trying to load most websites on IE6 will bring up a very intrusive graphic encouraging the user to upgrade.

IE6 Compatibility Warning

Since many of our clients are concerned with how their site performs and how it looks across different browsers, I’ve kept up-to-date with this ever-growing list of companies that are no longer willing to support older browsers. Most modern websites and online applications take advantage of newer technologies and formatting capabilities that were not around 10 years ago, making it nearly impossible for older technology like IE6 to provide full functionality or even render the pages properly.

Unfortunately, 10% of the connected world still uses IE6. This means that a good portion of internet users do not even realize that their web user experience is being compromised. They don’t know that the website they’re viewing isn’t supposed to look strange with overlapping graphics and missing components. They also don’t know about features like tabbed browsing, the omnibar (a unique bar for entering the URL or the desired search terms) or even about the world of plug-ins and extensions available to maximize productivity and enhance their user experience.

The truth is, however, that it is rarely the individual’s home or small business computer that is stuck on such an old browser. For consumers, Microsoft has a good way of pushing updates. It is typically large organizations like pharmaceutical companies, banks, and governments that choose to impose a closed technology environment, where the general culture is not to adopt new solutions. Company-wide upgrades are deemed too costly, and very often, other inter-connected applications come into play where those other applications do not support newer browser versions.

Even though we are discussing a 10-year old piece of software, it is definitely a very hot topic in the industry. With broader support for HTML5, we could finally see the real death of IE6. With HTML5, standard browsers are now able to embed and recognize tags such as “video” and “audio” without complicated coding or third-party player integration. When applications and sites start taking advantage of these functions, suddenly it won’t just be the design of the pages that displays incorrectly. Vital information will be missing and the user experience will be compromised on some of the most popular websites.

This doesn’t come as much of a surprise to me, as I never really understood Apple’s reasoning for forcing subscription model changes. Asking publishers to change a successful multi-channel subscription model just wasn’t realistic, even for Apple. This to me is parallel to Apple’s initial requirement that all iPhone applications had to be natively built using Objective C. The company soon realized that while this approach would protect the application quality and user experience, that the trade-offs were too high in terms of limited developer adoption. They simply needed to open up additional options for building iPhone applications to ensure that there were compelling titles available to sell the hardware. 

Apple’s subscription changes come hot on the heels of the Financial Time’s announcement that it was abandoning its native iOS application in favor of offering a paid web application (in turn circumventing the 30% Apple fee). In addition to the Financial Times, many smaller publications were looking for other ways to package and deliver their content without surrendering one-third of their revenue.

Now, Apple is giving publishers the choice. For some publishers, the Apple subscription model, even with its 30% fee, does make perfect sense. It provides a ready-made subscription handling process and it offers significant opportunities for promotion through iTunes and the upcoming Apple Newsstand. But for publishers with an existing, successful multichannel strategy, there is now a choice to make.

This is where the Adobe CQ5 platform comes into play. The technology, acquired by Adobe last year from Day Software, is a robust, modular platform that encompasses web content management, digital asset management, and social collaboration. It is truly an enterprise caliber solution that delivers a balance of effectiveness, improved client experience and multi-channel optimization. 

What’s really impressive about CQ5 is the platform’s capability to deliver great user experiences at a reasonable cost. It natively supports rich content, and leverages standard components for organizations to easily craft rich experiences and deliver contextual content to different user profiles.

CQ5 is like the Mercedes of web technology. It’s refined, finely engineered, robust, and economical to operate. Everyone would love to have the power and prestige it delivers, but it won’t be a fit for every client, or every project budget. But we with this in our toolbox, it does equip us to serve a broader range of clients on web projects and it will enable us to push the boundaries further for certain projects.

There are several different paths to building a mobile application, including:

• Native Development: This involves building a separate application for each platform using the recommended native language.  
• Titanium Appcelerator: An open source platform that allows developers to build mobile apps in Javascript and to package them for delivery on different platforms (Mac, Windows, mobile).
• Open Plug: A software developer kit (SDK) to build cross-platform native mobile apps using ActionScript/Flex.
• QT: A cross-platform application and UI framework that enables developers to build once and deploy across many platforms.

Native development provides the broadest scope of functionality and ensures that an app is adapted to work well for the specific OS/device. However, development requires specific expertise in proprietary technology (Objective C for iPhone/iPad/iPod, C#/Silverlight for WP7, Java for Android and for Blackberry), and creating a cross-platform app means essentially starting from scratch each time.

For organizations that are looking to package websites and web applications as native apps, solutions like PhoneGap may be a good fit. This open source framework wraps your application to create a native app that leverages a web viewer component. Organizations can also take the web application route, where they build an HTML5-driven application that will run on most systems and devices. This can work if the application is very simple and leverages only the common denominator functionality of HTML5 that is supported across all browsers.

Titanium, Open Plug, and QT all provide efficiencies as they leverage existing skills and allow developers to use a common base of code to package an app for each platform. They also allow for programmers to work in the language they know best, which means fewer errors and faster coding. However, the features they support are the “lowest common denominator”, which limits the functionality of the applications you can create.

Adobe is also releasing more mobile support with its next generation of Flex/AIR and will have tools to cover all mobile platforms.

The best path for an organization really depends on the team’s expertise, budget and time-to-market requirements. While native development offers the most functionality and more options, alternatives like Titanium, QT and OpenPlug provide massive advantages in leveraging a team’s existing skills to deliver an application that is faster-to-market and ultimately cheaper to build.

The answer is not black and white either, as you can use a mix of tools to accomplish your business objectives. For example, you can build an application for one platform using native development and use a tool like Titanium to deliver to other, less important platforms. Or you can use Titanium to quickly deliver a prototype or first version app of an app to the market for user validation and feedback while you are working on a more full-featured native application.

So, which is best? This will depend on the desired functionality of your app, the team you have working on it and their programming knowledge, your budget, and your time to market strategy. There really is no one-solution-fits-all option.

Google’s goal was to improve the relevance of search results and reduce rankings for sites that simply scrape content from others and pool it together to boost their rankings. These sites, dubbed as “content farms”, use other people’s keyword-loaded content to boost their rankings and draw in visitors, which in turn, drives up their advertising dollars.

What does this mean for your business? There are two main groups affected – those that aggregate or reuse content from other sites and those that rely heavily on article submissions as part of their marketing mix. If you aggregate content from other sites, and don’t supplement this with original content, your search rankings with Google will fall. Likewise if you submit articles to sites like eHow, EzineArticles and Associated Content as a way to boost site referrals, you will likely see a big drop in referral traffic as these sites are seeing significant drops in their own traffic due to Google’s change.

The other change rolled out by Google around the same time was a new document-level classifier that analyzes page content and looks for keyword repetition and spammy words. Sites that load their pages with keywords to improve rankings will in fact now see the opposite result and will be pushed down in the rankings. Many credible businesses resorted to this keyword repetition strategy in order to compete with the illegitimate businesses that monopolized the top search slots prior to this change. If this is strategy you attempted, you may be due for a content review on your key pages.

On the plus side, sites with original and relevant content should be rewarded by this algorithm change. This just reinforces the fact that content is still king and providing insightful information is the key to a successful Google ranking.

Last week I spent a busy couple of days connecting with the publishing community at O’Reilly’s Tools of Change for Publishing Conference in New York. It’s been a few years since we’ve attended this show, but with our recent surge in publishing related projects, I felt it was a great venue to hear what others were doing and what emerging trends we should keep our eyes on.

The overwhelming message from the show was that “The book is not dead”. The format that’s been around for the past 500 years is not going anywhere. However, there are tons of new market opportunities around the book that publishers must begin experimenting with new business opportunities. What publishers need to keep in mind is their core focus and their business objectives. Technology providers are pushing publishers to quickly adopt new technology, in some cases, even before it is fully ready for mass adoption. A good example of this is the new draft specification for the ePub 3 standard that leverages rich elements based on HTML5 and CSS3. This standard does provide so much more for publishers, but there are significant limitations, as the functionalities of these technologies only really work in Safari or iBooks, which severely limits the publisher’s market. What publishers need to realize is that HTML5 is a continuum, that will roll out in progressive implementations and will take years for all features to be supported by all browsers. It’s a great direction but is still in its early days.

The other interesting message I took home from TOC was that there is no magic bullet for publishers in terms of technology choice. From the outside, it appears that the big players like Adobe are well entrenched and have the market cornered, but the reality is that most publishers are leveraging free and open source technologies and are building their own package of solutions. This may be a result of the fact that the current ePub standard is quite loose, with lots of room for interpretation. Publishers’ approaches and results can vary greatly yet still be in compliance.

Mobile content delivery is also an area that I had many conversations about, particularly packaging books as stand-alone applications for tablet devices. Many publishers, particularly those that don’t concentrate on periodicals, are struggling with their strategy for developing mobile apps and are questioning the business value they deliver versus the cost to develop. Many book publishers are taking a wait and see approach and are looking for examples of successful implementations from peers.

Overall, it was a very interesting show with some great takeaways.

Just this morning, Google announced at the World Mobile Congress in Spain, that Android 2.4 will combine both Gingerbread and Honeycomb into a single OS. This simplifies things for users and makes for a more harmonious experience for Android users across their phones and tablets.

 Google also launched the Android Market, a centralized web hub for accessing apps. In the past, Android users could only access the App Market through their device and some carriers even opted to link users to a proprietary store with their own selection of apps, which made distribution of Android apps across carriers complicated for developers and publishers. With the Android Market website, users can easily browse and share apps and can even push apps out to their device remotely.

And finally this week, there were two big announcements for content publishers. Since the launch of the iPad, the lack of a viable subscription-based content delivery model has been problematic for magazine publishers. This single factor has been the biggest deterrent for adoption of tablets for digital magazines. Both Apple and Google came out this week with a solution for this. Apple rolled out its much anticipated subscription model on Tuesday, with a few surprises. Publishers anticipated that Apple would apply its standard 30 percent cut to all subscriptions sold and would retain subscriber data. However, in the official announcement, Apple surprised many by stating that it would not take any cut for subscriptions driven by the publisher. If apple brings the subscriber to the table, then they get their standard cut, but if the publisher delivers the reader, there is no fee. On the same note, Apple also agreed to put in an option that would allow the subscriber to decide whether their data is passed along to the publisher. These are two signs that Apple has decided to play nice with publishers. Perhaps they got wind of Google’s planned announcement for today and decided to extend the olive branch to publishers.

Google followed up Apple’s big announcement yesterday with the launch of One Pass, a content purchase platform that enables publishers to charge for content on a website, a smart phone or a tablet. Publishers keep 90 percent of the revenue, as compared to the 70 percent they get through the Apple App Store.

All in all, we can say that competition in the tablet market just got serious and the real winners here are the consumers and the publishers as there are several viable options for the delivery of content to mobile consumers, both free and now paid.