<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>aiaio - the Alexander Interactive blog</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/" />
    <link rel="self" type="application/atom+xml" href="http://www.alexanderinteractive.com/blog/atom.xml" />
    <id>tag:www.alexanderinteractive.com,2008-11-14:/blog//1</id>
    <updated>2010-02-05T19:18:58Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.23-en</generator>

<entry>
    <title>The sum of its parts</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/02/the-sum-of-its-parts.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.318</id>

    <published>2010-02-05T18:13:36Z</published>
    <updated>2010-02-05T19:18:58Z</updated>

    <summary>I&apos;ve been reading and thinking a lot about the iPad (how do you not?) since posting my initial, underwhelming reaction to its launch announcement last week. And, suffice to say, I&apos;ve changed my opinion rather drastically. The iPad will be,...</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="gadgets" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>I've been reading and thinking a lot about the iPad (how do you not?) since posting my initial, underwhelming reaction to its launch announcement last week. And, suffice to say, I've changed my opinion rather drastically.</p>

<p>The iPad will be, for many, greater than the sum of its parts.</p>

<p>Because on a checklist, the iPad <a href="/blog/2010/01/first-thoughts-ipad.html">disappoints</a>. But then, this happens a lot. Consider the first iPhone: no physical keyboard, no picture messaging, no video, etc. But the device quickly overcame those detractions.</p>

<p>What the iPhone had, and what the iPad probably has, is totality. Apple's genius in start-to-finish user experience design is well documented, and the iPad will be no exception. Interactions large and small, short and long, will all be easy to execute and fun to try. And it won't take long before people yearn for one.</p>

<p>I noted last week that it's likely a perfect complement for someone with a desktop computer: one device for heavy lifting, one for casual use. And the more I consider it, the more I think that's the likely scenario.</p>

<p>This gadget is also a harbinger of the future. Apple is banking on people working more in the cloud, using shared and networked services, and interacting in new ways. It's already happening; Ai, for one, despite griping about its flaws, uses Google Docs extensively. I know my own life has shifted from POP email and file hierarchies to IMAP and file search. Throw in a few multimedia subscriptions and the entire paradigm could shift for good.</p>

<p>Plenty of people have said this similarly and more eloquently than me; I particularly like <a href="http://weblog.muledesign.com/2010/02/the_failure_of_empathy.php">Mike Monteiro's observation</a>, that the iPad is the cinema's device of the future. So add me to the list of believers, with a dollop of humility.</p>]]>
        
    </content>
</entry>

<entry>
    <title>HTML5, Round 2: Semantic Markup</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/02/html5-round-2-semantic-markup.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.316</id>

    <published>2010-02-03T14:12:03Z</published>
    <updated>2010-02-05T16:05:36Z</updated>

    <summary>The semantic web is an ever-evolving development to define the meaning of content viewed on the web. It is the responsibility of an HTML developer to build web pages with a sharp understanding of how the front-end markup should be...</summary>
    <author>
        <name>Skottey Forden</name>
        
    </author>
    
        <category term="code" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="web development" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="html" label="html" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="html5" label="html5" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="semanticweb" label="semantic web" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>The semantic web is an ever-evolving development to define the meaning of content viewed on the web. It is the responsibility of an HTML developer to build web pages with a sharp understanding of how the front-end markup should be structured. With the upcoming release of HTML5, new tags will be introduced to the language that will enable more fluid communication between the web and the people and machines that use it.</p>

<p>The common practice of laying out HTML markup these days is the use of the <span style="font-family: monaco; font-size: 12px;">&lt;div&gt;</span> tag, using <span style="font-family: monaco; font-size: 12px;">id</span> or <span style="font-family: monaco; font-size: 12px;">class</span> attributes to block out content. New tags included in HTML5 will display a much more readable layout when defining areas of a web page. Some of the important tags in this group are <span style="font-family: monaco; font-size: 12px;">&lt;section&gt;</span>, <span style="font-family: monaco; font-size: 12px;">&lt;aside&gt;</span>, <span style="font-family: monaco; font-size: 12px;">&lt;header&gt;</span>, <span style="font-family: monaco; font-size: 12px;">&lt;footer&gt;</span>, and <span style="font-family: monaco; font-size: 12px;">&lt;nav&gt;</span>. It is likely that most of these tags clearly state what they are doing, but each still deserves it's own explanation:</p>

<ul>
<li><span style="font-family: monaco; font-size: 12px;">&lt;section&gt;</span>
<br />
This tag will be used to define generic content within a document. While <span style="font-family: monaco; font-size: 12px;">id</span> and <span style="font-family: monaco; font-size: 12px;">class</span> attributes will still be needed, this will still lay out a cleaner mode of blocking content than the now-standard <span style="font-family: monaco; font-size: 12px;">&lt;div&gt;</span> tag, thought the latter tag will not be deprecated and can still be used.</li>
<li><span style="font-family: monaco; font-size: 12px;">&lt;aside&gt;</span>
<br />
Sidebar content will be separated using this tag to show content that is "to the side" of main content areas. Generally this content is partially related to the primary focus of a given web page.</li>
<li><span style="font-family: monaco; font-size: 12px;">&lt;header&gt;</span> and <span style="font-family: monaco; font-size: 12px;">&lt;footer&gt;</span>
<br />
The topmost and bottommost blocks of content are often referred to as the "header" and "footer." Naturally, HTML5 introduces tags that clearly define this. It is likely that <span style="font-family: monaco; font-size: 12px;">id</span> and <span style="font-family: monaco; font-size: 12px;">class</span> attributes will no longer be needed with the use of the tags, unless a developer opts to use the <span style="font-family: monaco; font-size: 12px;">&lt;header&gt;</span> tag inside of a <span style="font-family: monaco; font-size: 12px;">&lt;section&gt;</span> tag.</li>
<li><span style="font-family: monaco; font-size: 12px;">&lt;nav&gt;</span>
<br />
Navigation menus will have their own tag in the markup, however it is uncommon for modern websites to have less than three nav menus on a single page, so <span style="font-family: monaco; font-size: 12px;">id</span> and <span style="font-family: monaco; font-size: 12px;">class</span> attributes would still be needed.</li>
</ul>

<p>Below is a screenshot of how this code might look. The new tags form a much more readable structure to the markup of the page. It creates a much cleaner view and gives the viewer a better of understanding of what is being displayed.<br />
 <br />
<img alt="semantic_screenshot.jpg" src="http://www.alexanderinteractive.com/blog/semantic_screenshot.jpg" width="520" height="672" class="mt-image-none" style="" /></p>

<p><a href="/entries/semantic.html">View a live example</a> (it may not be the prettiest site, but it's more for the markup than anything)</p>

<p>One of the most beautiful aspects of the above examples is the HTML Document Type Declaration, or DOCTYPE. It is the absolute first statement in every single web page, and is used to trigger standards mode in a browser and then determines what iteration of the language is in use. In earlier versions, there was specific data required as part of the declaration, which may look something like this:</p>

<p><span style="font-family: monaco; font-size: 12px;padding-left:15px;">&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"&gt;</span></p>

<p>Earlier versions of HTML were based on SGML, Standard Generalized Markup Language, but HTML5 is not and therefore has no need for the extra junk in the DTD. Here is the new one:</p>

<p><span style="font-family: monaco; font-size: 12px;padding-left:15px;">&lt;!DOCTYPE html&gt;</span></p>

<p>As previously stated - beautiful.</p>

<p>There are a few other new tags that are still worthy of mention: <span style="font-family: monaco; font-size: 12px;">&lt;article&gt;</span> to block content for blog entries or news articles, <span style="font-family: monaco; font-size: 12px;">&lt;dialog&gt;</span> used for marking up a conversation, and <span style="font-family: monaco; font-size: 12px;">&lt;figure&gt;</span> to be used when associating a caption with embedded content (audio or video).</p>

<p>It is debatable whether these new standards should be used, considering that full cross-browser support for HTML5 is not there yet. Firefox, Safari, Chrome, Opera, and a few smaller browsers will support most of these new tags, but older versions of Internet Explorer will not. Allegedly, there is a way to use JavaScript to force Internet Explorer to acknowledge that the new tags exist, but if a user has JavaScript disabled in their browser, the page will not render properly. Given that IE6 and IE7 still have a large-enough share on the browser market, this hack method does not seem sound enough to use in common markup yet.</p>

<p>The direction the semantic web is going will no doubt enhance the overall user experience of the web, even if the user is not consciously aware of it. This markup overhaul will create a better environment to display content and has the potential to make web pages even just slightly faster and more scalable. These are all good things.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Coming on too strong</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/02/coming-on-too-strong.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.315</id>

    <published>2010-02-02T16:37:27Z</published>
    <updated>2010-02-02T16:40:17Z</updated>

    <summary>GrokDotCom has a nice writeup of a too-eager lead-generation strategy on rent.com. Try too hard, ask for too much too soon, and instead of securing leads, a site just scares people away. I like the post&apos;s takeaway, which summarizes things...</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="ecommerce" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="user experience" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>GrokDotCom has a nice writeup of a <a href="http://www.grokdotcom.com/2010/02/01/avoid-asking-for-the-lead-too-early/">too-eager lead-generation strategy</a> on rent.com. Try too hard, ask for too much too soon, and instead of securing leads, a site just scares people away.</p>

<p>I like the post's takeaway, which summarizes things well: "Remember, it's not about you or your sales process. Your visitors are volunteers in the process and are coming to your site with motivations and intent."</p>

<p>Whether on a home page, a product page, or deep into checkout, visitors have their own reasons for being on a website. The site can only do so much to steer those users into a set action. Don't try so hard! Give people accessible options and let them do what works for them.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Ai and Internet Retailer</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/02/ai-and-internet-retailer.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.314</id>

    <published>2010-02-01T18:29:03Z</published>
    <updated>2010-02-01T18:38:21Z</updated>

    <summary>Ai is pleased to be mentioned not once but twice in this month&apos;s Internet Retailer. (We&apos;re in the print magazine as well as the website.) The cover story, The dollars are in the details, quotes this author as well as...</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="ai" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="conferences" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>Ai is pleased to be mentioned not once but twice in this month's Internet Retailer. (We're in the print magazine as well as the website.)</p>

<p>The cover story, <a href="http://www.internetretailer.com/article.asp?id=33323">The dollars are in the details</a>, quotes this author as well as other industry experts on how to nail the details in UXD. Ai's angle, as always, is to combine analytical research with active listening and observation of users' needs and behaviors.</p>

<p>More expansively, Alex Schmelkin and Josh Levine are quoted at length in <a href="http://www.internetretailer.com/article.asp?id=33343">a profile on customer-centric web design</a>. Our mantra, as always: understand motivations, empower users, and test, test, test!</p>

<p>In addition to being mentioned in IR, Team Ai is also going <em>to</em> IR: in two weeks we'll be in sunny Orlando for the <a href="http://www.irwd2010.com/">Internet Retailer Web Design</a> 2010 conference. Ai has some serious coverage this year, which we'll be detailing in a news item shortly but includes:</p><ul><li>Two days of private design consultations, run by Josh Levine and Ed Samour</li><li>Two live on-the-fly site critique presentations, featuring yours truly</li><li>Ai's first expo floor booth; stop by and say hi!</li></ul>With numerous clients in the Internet Retailer 500, we're excited to be such active participants this winter.<br />]]>
        
    </content>
</entry>

<entry>
    <title>First thoughts: iPad</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/01/first-thoughts-ipad.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.313</id>

    <published>2010-01-27T19:29:20Z</published>
    <updated>2010-01-27T19:58:33Z</updated>

    <summary>I&apos;ve been monitoring the Engadget feed like everyone else, and I can&apos;t give a full verdict until I play with it, but at a glance, I&apos;m not excited by Apple&apos;s new iPad. Why? First, because of what it is:A big...</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="gadgets" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>I've been monitoring the <a href="http://www.engadget.com/2010/01/27/live-from-the-apple-tablet-latest-creation-event/">Engadget feed</a> like everyone else, and I can't give a full verdict until I play with it, but at a glance, I'm not excited by Apple's new iPad.</p>

<p>Why? First, because of what it is:</p><ul><li>A big iPhone. Truly, that's how it is modeled, from the OS outward. Which means it has a similar form factor, the same beautiful glossy screen, and the same interfaces... which makes it just as scary to drop and very hard to put in one's pocket. True, the niche is different; Apple is targeting the "I don't want to lug my laptop" crowd with the iPad's 9.7" screen, half-inch depth and 1.5-lb. weight, all good things. But it's not a true laptop replacement, as I'll detail later.</li><li>A 3G device--on AT&amp;T's network. The last thing AT&amp;T needs (and that anyone is going to want) is more devices crowding its 3G bandwidth with unlimited-use devices. If this product is a hit, T is in for a rough year.</li></ul>More important, though, is what it isn't. Apple, of course, is often ahead of the game with its focus. The first iPod did nothing but play music; the iPhone didn't do copy-paste or Exchange sync; and so on. And perhaps the iPad will be more successful because of what Apple deliberately left out of it.<br /><br />For my $499 and up, though, I'd expect to have some of these things in the iPad, all of which are purposefully missing:<br /><br /><ul><li>Multitasking. Apple spent a long time demonstrating iWork, but without multitasking, users can't pingpong between apps to reference data, copy-paste or preview. Productivity is decidedly secondary.</li><li>Featherlight specs. Yes, one and a half pounds for this device is very nice. But a Kindle weighs 11 ounces, an iPhone less than 5. It's a portable device that's only somewhat portable. More like a coffee-table device (as expected) than one to tuck under the arm.<br /></li><li>A camera. What self-respecting Internet-centric gadget ships without a camera in 2010? Between chat, photo and video, cameras have become an expectation, not a perk. And the last thing an iPod user will want is wired peripherals. (Also, as reminded by @chrisfahey: no <a href="http://twitter.com/chrisfahey/statuses/8291017512">handwriting</a> or <a href="http://twitter.com/chrisfahey/statuses/8291022599">voice</a> recognition.)<br /></li><li>Enticing pricing. Sure, the $499 starting point is alluring, but at $829 for an all-in model, it's not as cheap as it looks.</li></ul>I'm no gadget prognosticator, and as an Apple shareholder, I hope I'm wrong. But this looks like it's going to be a bit of a niche product, at least at first. It may turn out to be an incredible gaming and reading platform, in which case I will gladly make my retractions and add one to my own gadget stable. But from here, thus far? Color me iUnderwhelmed.<br /><br />Of course, <a href="http://daringfireball.net/linked/2010/01/27/alan-kay">I could always be wrong</a>.]]>
        
    </content>
</entry>

<entry>
    <title>Designing for every audience</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/01/designing-for-every-audience.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.312</id>

    <published>2010-01-22T21:25:16Z</published>
    <updated>2010-01-22T21:41:05Z</updated>

    <summary>Did you know Google&apos;s Chrome browser already has 5 percent of the global browser market? That it&apos;s bigger than Safari? And are you aware that, despite your (or your designer&apos;s) disinclination toward it, Internet Explorer 6 still commands roughly 12-15%...</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="usabilty" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>Did you know Google's Chrome browser already has <a href="http://arstechnica.com/software/news/2010/01/chrome-grabs-market-share-from-ie-and-firefox-passes-safari.ars">5 percent of the global browser market</a>? That it's bigger than Safari?</p>

<p>And are you aware that, despite your (or your designer's) disinclination toward it, Internet Explorer 6 still commands roughly 12-15% of the space?</p>

<p>These figures--and the specifics of browser traffic on one's own website--matter, a lot, when new projects get underway. Google's 5% market share means it's officially a player in the browser wars and not just a side project. That means adding it to QA plans and considering some of its innovations, like proper use of HTML5.</p>

<p>At the same time, the continued prevalence of IE6, however sad, means that cutting-edge site design still needs to degrade gracefully to support the many corporate web surfers that can't upgrade their browsers. Certain b2b or enterprise-positioned websites may have an even greater percentage of IE6 traffic, just as sites with a more academic or creative bent often have an outsize share of visits using Safari.</p>

<p>All of which just serves as a reminder that multiple browser testing and compatibility remain crucial in web design in 2010. The same hurdles the industry faced when balancing Netscape and IE in 1999 exist today, perhaps even more so. Expect the cries for standardized code to get louder this year and next as the market shifts and fragments. And in the meantime, don't forget to give your site a proper run-through. Or four.</p>]]>
        
    </content>
</entry>

<entry>
    <title>HTML5, Round 1: The Video Tag</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/01/html5-round-1-the-video-tag.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.311</id>

    <published>2010-01-21T16:17:28Z</published>
    <updated>2010-02-03T18:38:10Z</updated>

    <summary>As an Ai Fender, I live in a world of HTML markup. The next revision of this language is HTML5, though it is currently not fully supported across all browsers. Some of the core ideas behind HTML5 are to create...</summary>
    <author>
        <name>Skottey Forden</name>
        
    </author>
    
        <category term="code" scheme="http://www.sixapart.com/ns/types#category" />
    
    <category term="html" label="html" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="html5" label="html5" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="video" label="video" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>As an Ai Fender, I live in a world of HTML markup. The next revision of this language is HTML5, though it is currently not fully supported across all browsers. Some of the core ideas behind HTML5 are to create more semantic markup based on usage of modern browsers, and to say farewell to the necessity of proprietary plugins required to access certain types of media on the web - namely audio and video content.</p>

<p>For the first in my series of emerging front-end web technologies, I am going to detail the new <span style="font-family: monaco; font-size: 12px;">&lt;video&gt;</span> tag feature. This may not be the most important new feature of HTML5, but I am certain it will be the most widely-used by the general population of internet users. Video content on the web has evolved immensely over the last five years - YouTube, Hulu, Vimeo, and the list goes on. It would be difficult to find a person who has used the internet and never watched a single video on YouTube.</p>

<p>Currently, users need the Shockwave plugin to view Adobe Flash content, or the Silverlight plugin to view Microsoft Silverlight content. The <span style="font-family: monaco; font-size: 12px;">&lt;video&gt;</span> tag will now allow internet users to view video content without the need to download such third-party plugins to view said content. This could easily boost a site's traffic and page views if more users can access the video content.</p>

<p>Below is a simple example of the <span style="font-family: monaco; font-size: 12px;">&lt;video&gt;</span> tag in action. Unfortunately, it will only be viewable in Mozilla Firefox, Apple Safari, or Google Chrome (more to come on those browsers after the video).</p>

<p><video tabindex="0" controls="" width="480" height="270"><br />
<source src="/static/flash/ai_video.mp4" type="video/mp4"><!-- Safari needs MPEG4--><br />
<source src="/static/flash/ai_video.ogg" type="video/ogg"><!-- Firefox needs Ogg --><br />
</video></p>

<p>For those not using a browser capable of handling the <span style="font-family: monaco; font-size: 12px;">&lt;video&gt;</span> tag, I have also included screenshots of what the players in each browser look like.</p>

<p><img alt="firefox.jpg" src="http://www.alexanderinteractive.com/blog/firefox.jpg" class="mt-image-none" style="margin-bottom: 0pt;" width="480" height="270" /><span style="font-style: italic;">Firefox Video Player</span></p>

<p><img alt="safari.jpg" src="http://www.alexanderinteractive.com/blog/safari.jpg" class="mt-image-none" style="margin-bottom: 0pt;" width="480" height="270" /><span style="font-style: italic;">Safari Video Player</span></p>

<p><img alt="chrome.jpg" src="http://www.alexanderinteractive.com/blog/chrome.jpg" class="mt-image-none" style="margin-bottom: 0pt;" width="480" height="270" /><span style="font-style: italic;">Chrome Video Player</span></p>

<p>Each browser has it's own unique user interface for displaying video content. The player controls all have the basic, fundamental features one would expect: play/pause, scrub through timeline, view time, and ability to control volume. Negative points to Safari for a lack of volume level slider and only giving mute functionality. Though I am sure that all browsers are still fine-tuning their interfaces as this technology is more or less a work-in-progress.  </p>

<p>The major drawback to this new method of displaying video content is the formatting of the files used. Safari and Chrome both require their video files to have an H.264 codec or most other Quicktime codecs (Adobe Flash also utilizes the H.264 codec for Flash Video/FLV files), where Firefox requires the OGG Vorbis codec. What this means for developers is the need for multiple video file formats included in the markup, which is actually quite simple and not time-consuming. </p>

<p>The real problem exists with OGG and how difficult it is to find a means to export a video file to that format. It is not impossible, but a plugin is required to use with video conversion software in order to export a video to .ogg format. Ultimately, it is now the task of the developer to install a third-party plugin needed in conjunction to this <span style="font-family: monaco; font-size: 12px;">&lt;video&gt;</span> tag, even though the plugin is not for a browser. But if it aids in creating a better experience for the end user, I am absolutely okay with it.</p>

<p>YouTube has an opt-in experimental version of their video player built using HTML5, but it will only work in browsers that support both HTML5 and H.264 codec. Give it a try: http://www.youtube.com/html5</p>]]>
        
    </content>
</entry>

<entry>
    <title>Duane Reade, testing customer loyalty</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/01/duane-reade-testing-customer-loyalty.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.310</id>

    <published>2010-01-17T03:24:04Z</published>
    <updated>2010-01-17T05:05:16Z</updated>

    <summary>Duane Reade introduced a new rewards program today. I happened to be in a Duane Reade this afternoon, where the cashier swiftly upgraded me to the new system and gave me a thick coupon book for my loyalty. The pharmacy...</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="business" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="crm" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="marketing" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>Duane Reade introduced a <a href="https://secure.duanereade.com/Rewards.aspx">new rewards program</a> today. I happened to be in a Duane Reade this afternoon, where the cashier swiftly upgraded me to the new system and gave me a thick coupon book for my loyalty.</p>

<p>The pharmacy and quick-shop chain is promoting its new program, Flex Rewards, as a consumer-friendly upgrade. They cite the new system's non-expiring reward points and paperless redemption as the main improvements.</p>

<p>Which is great, until the consumer finds out the real meat behind the change:<blockquote><strong>What Rewards will I receive?</strong><br />
      You will receive a $5 Reward for every 500 FlexRewards points earned.</blockquote>The old Duane Reade Dollar Rewards Club offered a one-point-per-dollar system that was blissfully simple: spend $100, earn 100 points, get $5 in store credit. It was simple and useful enough that I actually kept my rewards card handy, and I earned a handful of redemptions.</p><p>The new program is more confusing and far less valuable. Consumers now get two points per dollar spent and the same $5 reward now comes at 500 points. Or, in layman's terms, after $250 spent rather than $100. Earning the five bucks just became two and a half times as difficult.</p>

<p>Flex Rewards also has a couple of gimmicks in the system, such as <a href="https://secure.duanereade.com/SuperSaver.aspx">SuperSaver</a>, which encourages customers to not redeem their points in exchange for bonus points back when they finally spend the credit. It's a cash-back system that feeds itself.</p>

<p>If any of this has heads spinning, I suspect it's by design. Duane Reade has devalued its loyalty program by a minimum of 60 percent. It cloaked the bad news in technical upgrades and new schemes that try to divert attention away from the devaluing.</p>

<p>With Flex Rewards, Duane Reade stands to give away a lot less value in 2010 than it did in 2009. If I had a stake in the company, I'd be pleased with the new program. As a regular Duane Reade customer, though, I'm probably just going to stop using my card.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Ecommerce news, January 14</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/01/ecommerce-news-january-14.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.309</id>

    <published>2010-01-14T21:51:21Z</published>
    <updated>2010-01-14T21:57:07Z</updated>

    <summary>Spotted around the Internet: Recommended best practices for 2010 are all customer-centric: access to phone numbers, user-focused testing, trust marks, simplified processes. One survey of the holidays puts December 2009 online retail at +18%. And if you&apos;re wondering, it&apos;s not...</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="ecommerce" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>Spotted around the Internet:</p>

<p><a href="http://www.practicalecommerce.com/blogs/post/632-Best-Practices-Review">Recommended best practices for 2010</a> are all customer-centric: access to phone numbers, user-focused testing, trust marks, simplified processes.</p>

<p>One survey of the holidays puts <a href="http://www.internetretailer.com/dailyNews.asp?id=33141">December 2009 online retail at +18%</a>.</p>

<p>And if you're wondering, it's not too soon to pitch <a href="http://www.retailemailblog.com/2010/01/am-inbox-first-reference-to-st-patricks.html">St. Patrick's Day</a> to your readers.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Getting reviews on your ecommerce site</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/01/getting-reviews-on-your-ecommerce-site.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.308</id>

    <published>2010-01-08T19:38:05Z</published>
    <updated>2010-01-08T19:41:41Z</updated>

    <summary>Good little piece on customer reviews from Retail Customer Experience. I like the data points cited, which are worth repeating: 70% of users trust reviews, 64% find them important, and 47% place greater value on reviews than the manufacturer information...</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="ecommerce" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>Good little piece on customer reviews from <a href="http://www.retailcustomerexperience.com/article.php?id=1585&na=1">Retail Customer Experience</a>. I like the data points cited, which are worth repeating: 70% of users trust reviews, 64% find them important, and 47% place greater value on reviews than the manufacturer information provided. Crazy? Only if you ignore it....</p>]]>
        
    </content>
</entry>

<entry>
    <title>Ecommerce news, January 7</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/01/ecommerce-news-january-7.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.307</id>

    <published>2010-01-07T14:54:10Z</published>
    <updated>2010-01-07T15:05:20Z</updated>

    <summary>Spotted around the Internet: Mobile ecommerce visits have grown tremendously in the past year; eBay and Amazon are getting millions of sessions monthly, and Netflix mobile traffic is up 240%. Email performed well in holiday 2009, with higher open and...</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="ecommerce" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>Spotted around the Internet:</p>

<p>Mobile ecommerce visits have <a href="http://www.internetretailer.com/dailyNews.asp?id=33080">grown tremendously</a> in the past year; eBay and Amazon are getting millions of sessions monthly, and Netflix mobile traffic is up 240%.</p>

<p>Email performed well in holiday 2009, with <a href="http://www.mediapost.com/publications/?fa=Articles.showArticle&art_aid=119721">higher open and click rates</a> than in years past, likely a reflection of the bargain-hunting online masses this past season.</p>

<p>Those bargain hunters mentioned above <a href="http://www.emarketer.com/Article.aspx?R=1007454">cite deals and cool site features</a> as the reasons they're shopping online.</p>

<p>And a trend alert: Macy's experienced 1% same-store growth in December, a good-enough result for the season&#8212;but macys.com was <a href="http://www.earthtimes.org/articles/show/macyrsquos-inc-same-store-sales-up-1-in-december,1110480.shtml">up almost 30 percent</a>.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Why the Nexus One isn&apos;t exciting</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/01/why-the-nexus-one-isnt-exciting.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.306</id>

    <published>2010-01-06T14:49:48Z</published>
    <updated>2010-01-06T15:46:54Z</updated>

    <summary>The public release of Google&apos;s phone was news but not an event yesterday. (The New York Times used &quot;some polite applause&quot; and &quot;shakes but doesn&apos;t upend&quot; in its coverage headlines.) Why? Because Google didn&apos;t physically make the phone. In partnering...</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="business" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="gadgets" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>The public release of Google's phone was news but not an event yesterday. (The New York Times used <a href="http://www.nytimes.com/2010/01/06/technology/internet/06google.html?ref=business">"some polite applause"</a> and <a href="http://www.nytimes.com/2010/01/06/technology/personaltech/06pogue.html">"shakes but doesn't upend"</a> in its coverage headlines.)</p>

<p>Why? Because Google didn't physically make the phone.</p>

<p>In partnering with HTC, a company that produces cell phones for every US carrier and two different operating systems, Google ceded control of the overall experience. Never mind that the handset is slim and fairly attractive. It's also generic, and apparently imperfect. When David Pogue pushes your phone's home button, you really don't want it to fail.</p>

<p>There's a huge difference between designing and engineering a device, as Apple did with the iPhone and Palm with the Pre, and a company having a device <a href="http://ptech.allthingsd.com/20100105/googles-nexus-one-is-bold-new-face-in-super-smartphones/">"built to its specifications"</a>. Google was telling HTC, "We want our phone to do this," and HTC was putting the requisite componentry in place. This tends to minimize holistic product definition and by its very nature waters down the innovation. In contrast, Palm and Apple (and Motorola and Nokia, for that matter) manage the entire process, and their software is designed to complement the hardware, maximizing user experience. Google, a company that is strictly virtual, doesn't know how to do this.</p>

<p>Software companies that venture into hardware have to embrace the role of hardware manufacturer. This is true beyond smartphones: consider how Microsoft, which built an empire on software, hit a home run with its Xbox by controlling the end-to-end product creation. (Microsoft makes great computer accessories, too; I'm using a Microsoft <a href="http://www.microsoft.com/hardware/mouseandkeyboard/productdetails.aspx?pid=043">keyboard</a> and <a href="http://www.microsoft.com/hardware/mouseandkeyboard/ProductDetails.aspx?pid=068">mouse</a> right now.) But we never saw a Microsoft-branded PC produced by Compaq in the 1990s. All or nothing.</p>

<p>Google is a formidable company with incredible technological prowess. I'm not placing bets against Android just yet. The relative mediocrity of the Nexus One, though, is exactly what we should have expected.</p>]]>
        
    </content>
</entry>

<entry>
    <title>The next Apple gadget </title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2010/01/the-next-apple-gadget.html" />
    <id>tag:www.alexanderinteractive.com,2010:/blog//1.305</id>

    <published>2010-01-05T20:12:55Z</published>
    <updated>2010-01-05T20:38:26Z</updated>

    <summary>With sources as authoritative as the Wall Street Journal confirming the pending introduction of a tablet computer from Apple, one can assume the cat&apos;s out of the bag for the big Apple news on January 27. But what does it...</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="business" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="gadgets" scheme="http://www.sixapart.com/ns/types#category" />
    
        <category term="iphone" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>With sources as authoritative as the Wall Street Journal confirming the <a href="http://online.wsj.com/article/SB10001424052748703580904574638630584151614.html">pending introduction of a tablet computer from Apple</a>, one can assume the cat's out of the bag for the big Apple news on January 27. But what does it mean?</p>

<p>I'm throwing my hat in the kill-the-small-laptop camp. The iPhone proved that people will use computing power in a portable manner and without a physical keyboard. Despite the name, the iPhone is indeed a computer, with a clever 3.5" form factor. And people use it as such. Indeed, Ai has ecommerce clients generating sales from iPhone browsers on non-mobile-optimized websites.</p>

<p>Given that, why not continue to redefine the portable computing space? Steve Jobs must scoff at netbooks, with their minuscule keyboards and compromised feature sets. Better to <a href="http://daringfireball.net/2009/12/the_tablet">redefine the experience</a> with a new kind of device. Just like the iPhone has redefined pocket-sized power, so too can the tablet redefine the small-laptop market.</p>

<p>Apple is shooting for the personal, casual computing market, folks like me who like to get online sitting on the couch and folks like <a href="http://www.alexanderinteractive.com/company/nathan.html">Nathan</a> who want a three-pound computer to travel with. It will be big enough to type on and clear enough for reading, gaming and web browsing.</p>

<p>I bet the tablet's pixels per inch will be impressively high, like the 160 ppi of the iPhone. Most Mac desktop and laptop displays hover around <a href="http://en.wikipedia.org/wiki/List_of_displays_by_pixel_density">110 ppi</a>. An 11" screen at 160 ppi will provide almost the same amount of pixel real estate as a 13.3" MacBook screen does now. This will help minimize people's perception that they're giving up detail for size.</p>

<p>Yesterday I postulated to my coworkers that the 13" MacBook is going to disappear. But now I suspect it will turn Pro a few months after the tablet comes out. Portable computing power is important, and with a tricked-out technology package, the MacBook will differentiate itself. Expect MacBooks to shift in price from $1199 and up to $1499 or higher, with the tablet coming in around the thousand-dollar mark.</p>

<p>Whatever it turns out to be, expect irrational and unrivaled consumer desire and interest for it, on a scale that only Apple creates. Google's phone news is a business story: "Look at Google aiming for the smartphone market." But Apple's news is cultural. Which is why they may succeed in their latest attempt to change the game.</p>]]>
        
    </content>
</entry>

<entry>
    <title>Jack Vs Spider</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2009/12/jack-vs-spider.html" />
    <id>tag:www.alexanderinteractive.com,2009:/blog//1.304</id>

    <published>2009-12-24T15:23:40Z</published>
    <updated>2009-12-24T15:24:52Z</updated>

    <summary>One last one before the new year Our VP of Security takes on an 8 legged intruder...</summary>
    <author>
        <name>Tim Broder</name>
        <uri>http://www.alexanderinteractive.com/</uri>
    </author>
    
        <category term="ai" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>One last one before the new year</p>

<p>Our VP of Security takes on an 8 legged intruder</p>

<p><object width="425" height="344"><param name="movie" value="http://www.youtube.com/v/HZB3N9bqBSg&hl=en&fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/HZB3N9bqBSg&hl=en&fs=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="344"></embed></object></p>]]>
        
    </content>
</entry>

<entry>
    <title>Happy holidays from Ai</title>
    <link rel="alternate" type="text/html" href="http://www.alexanderinteractive.com/blog/2009/12/happy-holidays-from-ai.html" />
    <id>tag:www.alexanderinteractive.com,2009:/blog//1.303</id>

    <published>2009-12-23T20:27:39Z</published>
    <updated>2009-12-23T20:28:27Z</updated>

    <summary>Barring a last-second epiphany from one of our contributors, aiaio is going into its winter hibernation, returning in January. See you in 2010....</summary>
    <author>
        <name>David Wertheimer</name>
        
    </author>
    
        <category term="ai" scheme="http://www.sixapart.com/ns/types#category" />
    
    
    <content type="html" xml:lang="en" xml:base="http://www.alexanderinteractive.com/blog/">
        <![CDATA[<p>Barring a last-second epiphany from one of our contributors, aiaio is going into its winter hibernation, returning in January. See you in 2010.</p>]]>
        
    </content>
</entry>

</feed>
