<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Galvin Blog &#187; Technology</title>
	<atom:link href="http://blog.galvintech.com/tag/technology/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.galvintech.com</link>
	<description>We Build Websites / Applications / Relationships.</description>
	<lastBuildDate>Fri, 03 Feb 2012 20:58:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Christmas DrivenTablet Explosion &#8211; How Do We Handle It?</title>
		<link>http://blog.galvintech.com/application-development/christmas-driventablet-explosion-how-do-we-handle-it-1248.htm</link>
		<comments>http://blog.galvintech.com/application-development/christmas-driventablet-explosion-how-do-we-handle-it-1248.htm#comments</comments>
		<pubDate>Thu, 22 Dec 2011 20:59:20 +0000</pubDate>
		<dc:creator>Adam Staples</dc:creator>
				<category><![CDATA[Application Development]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[Mobile Development]]></category>
		<category><![CDATA[Mobile Web]]></category>
		<category><![CDATA[New Technology]]></category>
		<category><![CDATA[User Experience Design]]></category>
		<category><![CDATA[Graphic Design]]></category>
		<category><![CDATA[Online Test]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[user experience]]></category>
		<category><![CDATA[Web Design]]></category>

		<guid isPermaLink="false">http://blog.galvintech.com/?p=1248</guid>
		<description><![CDATA[Adam Staples &#8211; Tablet Owner&#8230;.sort of. Technically it&#8217;s my wife&#8217;s, or at least it will be come Christmas Day. (Don&#8217;t worry, she&#8217;s not a regular visitor to Galvin Blog, so I&#8217;m not worried about ruining the surprise.) When I made the decision a few weeks ago to purchase a tablet I started to do some [...]]]></description>
			<content:encoded><![CDATA[<p>Adam Staples &#8211; Tablet Owner&#8230;.sort of. Technically it&#8217;s my wife&#8217;s, or at least it will be come Christmas Day. (Don&#8217;t worry, she&#8217;s not a regular visitor to Galvin Blog, so I&#8217;m not worried about ruining the surprise.)</p>
<p>When I made the decision a few weeks ago to purchase a tablet I started to do some preliminary research.  <a href="http://blog.galvintech.com/application-development/christmas-driventablet-explosion-how-do-we-handle-it-1248.htm/attachment/tablets-pile" rel="attachment wp-att-1266"><img class="alignleft size-medium wp-image-1266" title="tablets-pile" src="http://66.147.242.155/~galvinte/wp-content/uploads/2011/12/tablets-pile-300x203.jpg" alt="tablets pile 300x203 Christmas DrivenTablet Explosion   How Do We Handle It?" width="300" height="203" /></a>To that point in time, I really hadn&#8217;t investigated what was available. Sure, I&#8217;d heard about the e-reading manufacturers branching out in to the mobile browsing market, but I wasn&#8217;t quite sure to what extent.</p>
<p>What I found I really surprised me. There were no fewer than 12 seemingly good options from a hardware standpoint that were available.  This got me to thinking about how we, as the web and software development industry, will deal with the explosion of available devices that should be accounted for from both a technical and strategic standpoint.</p>
<p>Do we test against Amazon&#8217;s Kindle Fire Browser? If so, how do we account for the upgrade that will be released mid-way through a project? I would think that they&#8217;ll be enough browser versions, hardware types, and screen sizes to make all of our heads spin.</p>
<p>I&#8217;m not sure that the businesses we serve have fully adapted to the explosion in HTML browser compatible smart phones yet. Now they need to be budgeting for design and testing considerations for screens ranging in size from 3 to over 10 inches in size as well? What a challenge awaits our industry, along with the marketing industry, as we go through these changes!</p>
<p>For the time being, I suppose that we&#8217;ll all do our best to identify key systems and audiences like we always have, we&#8217;ll just have to broaden our view of what the possible answers could be. It probably won&#8217;t be so simple as to account for iPhone, Blackberry, and Android devices any longer. You&#8217;d have to expect that budgets will be raised to account for these key users and their respective platforms. 2012 is going to be an interesting year for our industry and I am excited to see how these changes affect the way in which we approach our work.</p>
<p>And&#8230;for the record, I did end up going with the Samsung Galaxy Tab 10.1. I&#8217;ve had good luck with the Android platform to date, although the app selection does seem to be a little less well-developed than the iPad offerings, but I&#8217;ll save that for another post on another day.</p>
<p>Merry Christmas Everyone and happy Tablet-ing!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.galvintech.com/application-development/christmas-driventablet-explosion-how-do-we-handle-it-1248.htm/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mobile Friendly Doesn&#8217;t = Mobile</title>
		<link>http://blog.galvintech.com/business-strategies/mobile-friendly-doesnt-mobile-640.htm</link>
		<comments>http://blog.galvintech.com/business-strategies/mobile-friendly-doesnt-mobile-640.htm#comments</comments>
		<pubDate>Fri, 19 Aug 2011 18:45:06 +0000</pubDate>
		<dc:creator>Adam Staples</dc:creator>
				<category><![CDATA[Business Strategies]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Interface Design]]></category>
		<category><![CDATA[User Experience Design]]></category>
		<category><![CDATA[Website Marketing]]></category>
		<category><![CDATA[best practice]]></category>
		<category><![CDATA[Graphic Design]]></category>
		<category><![CDATA[mobile friendly website]]></category>
		<category><![CDATA[mobile website design]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://blog.galvintech.com/?p=640</guid>
		<description><![CDATA[It’s a common misconception that the good strategies employed on a traditional website naturally make the transition over to a mobile environment. As convenient as that would be, it’s just not the case. The first step in understanding the differences in strategy between the two is to understand the difference between a mobile website and [...]]]></description>
			<content:encoded><![CDATA[<p>It’s a common misconception that the good strategies employed on a traditional website naturally make the transition over to a mobile environment. As convenient as that would be, it’s just not the case.</p>
<p>The first step in understanding the differences in strategy between the two is to understand the difference between a mobile website and a<br />
“mobile friendly” website.</p>
<p>“Mobile Friendly” websites on the other hand, utilize traditional web design, but are developed in such a way that they will display accurately on a mobile device. In this way, the website will work on a mobile device, but because of the difference in the size of the display area, the user must manipulate the site to find the information they seek.</p>
<p>Because of this difference in display size, and the poor user experience it can create, a best practice is to account for the mobile user while design your website. This specialized mobile interface is customized to the smaller display areas of mobile devices and is automatically loaded when a user visits your site via a mobile device.</p>
<p>In order to make maximum the use of the smaller display area, while ensuring the smoothest user experience, you should streamline the immediately available information within the mobile design. This is probably done shortening the navigation of the site.</p>
<p>Another difference between a traditional website made to be ‘mobile friendly’ and a truly mobile website, is the bandwidth, and subsequent load times, of a mobile device. With this consideration in mind, you should also look to limit the size and quality of the images you select. Smaller, less high resolution images load faster and, due to the smaller overall display, look no different than their traditional (full high resolution coupled with large display area) counterparts.</p>
<p>Combine all three of these techniques and you’ll have a good looking, fast loading, and easy to navigate version of your website that caters to the mobile user. This leads to a positive user experience and an increased awareness of your company and your products or services.</p>
<p>Let’s take a quick look at Panera Bread as an example. The first photo below is of their traditional website. Large high resolution images highlight a full featured website with a full navigation system. This works splendidly in a traditional desktop environment where a high speed connection<br />
and full display is readily available.</p>
<p><a rel="attachment wp-att-641" href="http://blog.galvintech.com/website-marketing/mobile-friendly-doesnt-mobile-640.htm/attachment/panera-standard"><img class="alignleft size-medium wp-image-641" title="Panera Standard" src="http://66.147.242.155/~galvinte/wp-content/uploads/2011/08/Panera-Standard-300x268.png" alt="Panera Standard 300x268 Mobile Friendly Doesnt = Mobile" width="300" height="268" /></a></p>
<p>This second photo from Panera Bread is of their mobile website interface. As you can see, they shortened the navigation system and made use of smaller images. This causes the site to load faster, while presenting users with specific information that a mobile user might be looking for. The end result is a great case study on understanding the differences between traditional and mobile environments.</p>
<p><a rel="attachment wp-att-644" href="http://blog.galvintech.com/website-marketing/mobile-friendly-doesnt-mobile-640.htm/attachment/panera-mobile"><img class="alignleft size-medium wp-image-644" title="Panera Mobile" src="http://66.147.242.155/~galvinte/wp-content/uploads/2011/08/Panera-Mobile-230x300.png" alt="Panera Mobile 230x300 Mobile Friendly Doesnt = Mobile" width="230" height="300" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.galvintech.com/business-strategies/mobile-friendly-doesnt-mobile-640.htm/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>The Home Hub Reinvented, I Miss Audrey</title>
		<link>http://blog.galvintech.com/new-technology/the-home-hub-reinvented-i-miss-audrey-101.htm</link>
		<comments>http://blog.galvintech.com/new-technology/the-home-hub-reinvented-i-miss-audrey-101.htm#comments</comments>
		<pubDate>Mon, 06 Apr 2009 12:52:54 +0000</pubDate>
		<dc:creator>Gary Galvin</dc:creator>
				<category><![CDATA[New Technology]]></category>
		<category><![CDATA[3Com]]></category>
		<category><![CDATA[Audrey]]></category>
		<category><![CDATA[Ergo Audrey]]></category>
		<category><![CDATA[Gary Galvin]]></category>
		<category><![CDATA[Internet Appliance]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://blog.galvintech.com/?p=101</guid>
		<description><![CDATA[The Verizon Hub is similar to 3Com's Ergo Audrey.  Back in 2000 - 2001 Gary Galvin was part of a team that helped bring Audrey to life.]]></description>
			<content:encoded><![CDATA[<p>My first job out of college was with <a title="3Com" href="http://www.3com.com" target="_blank">3Com</a> in Chicago, IL and I was part of a team that brought a new internet product to life &#8211; <a title="Information about Ergo Audrey" href="http://en.wikipedia.org/wiki/3Com_Audrey" target="_blank">Audrey</a>.  Audrey was to do for the home life what <a title="Palm Pilot" href="http://en.wikipedia.org/wiki/Palm_Pilot" target="_blank">Palm Pilot</a> did for the business life.  It was supposed to be the central hub for the home.  It had everyone&#8217;s calendar, email, browse the web, to-do list, you can leave notes, gather your favorite news, stocks and scores, view and store recipes and shop online.  We went to market in October 2000 and it sold for $499.  I remember being so excited to go to Best Buy and see it on the shelves and say to myself  &#8220;I helped build that&#8221;.  Heck, we even got on <a title="Oprah" href="http://www.oprah.com/index" target="_blank">Oprah</a>. Looking back this was a great first job out of college.  I got to live the dot-com boom, travel the country from dot-com start up to dot-com start up, stay in 5-star hotels, eat at fancy restaurants, work very late and long hours and most importantly I got to be a part of team that invented this product.  There were a lot of smart people on our team who came from all over the country to work on this.  I got to work with the channel team (I still miss those folks).  We designed and developed web channels so people could browse from cached website to website.</p>
<div class="wp-caption aligncenter" style="width: 329px"><img title="3Com Ergo Audrey" src="http://images.pcworld.com/news/graphics/n_101700_audreyb.jpg" alt="n 101700 audreyb The Home Hub Reinvented, I Miss Audrey" width="319" height="325" /><p class="wp-caption-text">Ergo Audrey </p></div>
<p>But Audrey was short lived.  Shortly after launch the <a title="Dot-Com Burst" href="http://en.wikipedia.org/wiki/Dot-com_bubble#The_.22Bubble_Bursts.22" target="_blank">dot-com</a> bust began.  We began to see our content providers go out of business one by one.  People began losing trust in the internet and were not buying Audrey.  But we felt the biggest issue was that we were ahead of the times.  Consumers were still buying buying their first computers and were getting online for the first time.  So buying a fancy internet appliance was not something conceivable and so <a title="3Com Cuts Audrey" href="http://news.cnet.com/2100-1040-254497.html" target="_blank">3Com cut Audrey and the Internet Appliance division</a>.</p>
<div class="wp-caption aligncenter" style="width: 437px"><img title="Verizon Hub" src="http://news.cnet.com/i/bto/20090123/Verizon_Hub_-_Application_Screen_610x343.JPG" alt=" The Home Hub Reinvented, I Miss Audrey" width="427" height="240" /><p class="wp-caption-text">Verizon Hub</p></div>
<p>Just recently I began seeing TV commercials about Verizon Wireless&#8217; new phone &#8211; the <a title="Verizon Hub" href="http://www.verizonwireless.com/b2c/vzhub/overview.jsp" target="_blank">Verizon Hub</a>.  I nearly jumped out of my chair when I saw the first commercial.  It was almost like seeing Audrey all over again.  I have to admit that although envious I am excited to see the Hub launch.  The Hub is meant to serve as the family hub &#8211; similar to Audrey&#8217;s approach.  Yes, Audrey was ahead of the times but I am convinced that it paved the way for products like The Hub and hopefully more to come in the future.  I also believe that everything happens for a reason so because of Audrey&#8217;s failure I have been able to start up my own business.  I learned a lot during my days at 3Com and I thank the guys at 3Com and especially Jen, Daniel and Chris for showing me the ropes, giving a rookie a chance and being a pretty darn good team.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.galvintech.com/new-technology/the-home-hub-reinvented-i-miss-audrey-101.htm/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

