<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">

    <title type="text">Good Egg Design</title>
    <subtitle type="text">Good Egg Design:</subtitle>
    <link rel="alternate" type="text/html" href="http://goodeggdesign.net/index.php/site/index/" />
    <link rel="self" type="application/atom+xml" href="http://goodeggdesign.net/index.php/site/atom/" />
    <updated>2008-03-29T20:55:37Z</updated>
    <rights>Copyright (c) 2007, goodegg</rights>
    <generator uri="http://expressionengine.com/" version="1.6.0">ExpressionEngine</generator>
    <id>tag:goodeggdesign.net,2007:10:07</id>


    <entry>
      <title>Good Egg at Adobe Max 2007</title>
      <link rel="alternate" type="text/html" href="http://goodeggdesign.net/index.php/site/good_egg_at_adobe_max_2007/" />
      <id>tag:goodeggdesign.net,2007:index.php/site/index/2.3</id>
      <published>2007-10-07T19:29:00Z</published>
      <updated>2008-03-29T20:47:26Z</updated>
      <author>
            <name>goodegg</name>
            <email>creative@goodeggdesign.net</email>
            <uri>http://www.goodeggdesign.net</uri>      </author>

      <content type="html"><![CDATA[
        <p>Obviously, one of the main goals of the keynote address is to &#8220;Wow!&#8221; the audience - and this keynote certainly did just that. They began with an overview of what makes a great user experience--something of a feat in itself, given the ever-shifting web design climate.&nbsp; Adobe Max addressed five key issues that Good Egg has always taken to heart:
</p>
<p>
1. Content is king. 
<br />
2. Adapting to the personality of the user.
<br />
3. Simplicity.
<br />
4. Guiding and rewarding the users.
<br />
5. Improving the experience for the user (not necessarily the UI).
</p>
<p>
Many of the five points overlap - ultimately, they key is to provide site visitors with meaningful content in an accessible, unobtrusive way.
</p>
<p>
The next section of the keynote address involved product updates. Flash now supports HD video in full screen. If you&#8217;re not familiar with Flash, just visit YouTube. All of those videos are Flash-based. Now imagine being able to watch high-definition videos on YouTube. That&#8217;s where things are heading. This is pretty cool. 
</p>
<p>
Next up was a demonstration of some of the cool features found in Dreamweaver. While none of this was particularly new, it was still pretty neat to see. Built into Dreamweaver CS3 is a framework known as Spry. You know how you hear the term &#8220;Ajax&#8221; bandied about all the time? Well, Spry is a quick and simple way to incorporate Ajax into your website. Now you can add tabs and panels and data feeds without having to know anything about programming. Spry just makes it simple.
</p>
<p>
Now, one of the biggest releases for Adobe this year is AIR. AIR allows you take any online websites and applications and run them from your desktop. No more launching a web browser, you&#8217;ll be able to run internet-based applications directly from your computer.
</p>
<p>
Because AIR is such a big deal for Adobe, there was a LOT of focus on it. A lot. Pretty much the rest of the first day&#8217;s keynote was devoted to AIR. There was an amazing showcase of AIR applications from companies such as eBay and Disney and AOL and Anthropologie. There were just so many fascinating ways that Adobe AIR has been utilized to make work and play much more exciting. 
</p>
<p>
The next day&#8217;s keynote focused a lot on server-side technology&#8230; Moving on.
</p>
<p>
They demoed some improvements to VoIP. That was fine. They showed the next version of Adobe Connect Professional, a live online meeting application. Formerly built using Flash, they&#8217;ve completely revamped it from the ground up using Flex and making it more extensible. 
</p>
<p>
Finally, quite possibly the coolest demo was a future application code-named &#8220;Thermo.&#8221; It&#8217;s essentially a tool that allows designers to take a layered Photoshop document and, through a few mouse clicks, convert that fully designed image into a functional Flex-based Rich Internet Application. Aral Balkan (whose &#8220;Inspire Session,&#8221; about SWX, I attended), has a couple videos (<a href="http://aralbalkan.com/1050">http://aralbalkan.com/1050</a>) showing the process behind it all. It&#8217;s pretty impressive in a geeky sort of way. How much will this impact Good Egg? It&#8217;s hard to say. But, seeing as this application won&#8217;t even be available until next year, we&#8217;ll have some time to prepare.
</p>
<p>
And this is just scratching the surface. There were many other demos and surprises delivered at Max. 
</p>
<p>
We had such a great time at Adobe Max this year and can&#8217;t wait for next year&#8217;s event in San Francisco. Maybe we&#8217;ll see you there too.
<br />

</p> 
      ]]></content>
    </entry>

    <entry>
      <title>Why web standards?</title>
      <link rel="alternate" type="text/html" href="http://goodeggdesign.net/index.php/site/why_web_standards/" />
      <id>tag:goodeggdesign.net,2007:index.php/site/index/2.2</id>
      <published>2007-09-27T03:03:00Z</published>
      <updated>2008-03-29T20:55:37Z</updated>
      <author>
            <name>goodegg</name>
            <email>creative@goodeggdesign.net</email>
            <uri>http://www.goodeggdesign.net</uri>      </author>

      <content type="html"><![CDATA[
        <p>As a web designer, I get asked this question a lot.&nbsp; My simple answer, which might seem glib on the surface, is this: They&#8217;re like green beans—they&#8217;re good for you. 
</p>
<p>
For the uninitiated, web standards are a set of industry best practices, the purpose of which is to deliver web content for universal consumption—i.e., in a way both accessible and presentable to more people and more types of browsing devices.&nbsp; It levels the playing field for site design, and without layers of browser-specific hacks and workarounds, you can virtually guarantee forward- and backward-compatibility.
</p>
<p>
But does building a standards-compliant site provide tangible benefits to the client?&nbsp; Absolument!&nbsp; Lowered production costs? Check.&nbsp; Improved organic search engine ranking?&nbsp; Check.&nbsp; Cost savings on bandwidth and server space?&nbsp; Check.&nbsp; And when it comes time to revamp your site, your content can be easily repurposed and reused, thus realizing further savings on development and project management time.
</p>
<p>
So really, the question becomes, &#8220;Why NOT web standards?&#8221;
</p> 
      ]]></content>
    </entry>


</feed>