<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: Podcast 47: The mobile web</title>
	<atom:link href="http://boagworld.com/podcast/podcast-47-the-mobile-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://boagworld.com/podcast/podcast-47-the-mobile-web/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=podcast-47-the-mobile-web</link>
	<description>Advice on web design and digital strategy from Paul Boag</description>
	<lastBuildDate>Fri, 10 May 2013 03:27:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: dress up games</title>
		<link>http://boagworld.com/podcast/podcast-47-the-mobile-web/#comment-1998</link>
		<dc:creator>dress up games</dc:creator>
		<pubDate>Thu, 06 Mar 2008 17:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://wpboagworld:83/uncategorized/podcast-47-the-mobile-web#comment-1998</guid>
		<description><![CDATA[&lt;p&gt;thanks...&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>thanks&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pirkka Rannikko</title>
		<link>http://boagworld.com/podcast/podcast-47-the-mobile-web/#comment-1997</link>
		<dc:creator>Pirkka Rannikko</dc:creator>
		<pubDate>Fri, 27 Oct 2006 09:26:43 +0000</pubDate>
		<guid isPermaLink="false">http://wpboagworld:83/uncategorized/podcast-47-the-mobile-web#comment-1997</guid>
		<description><![CDATA[&lt;p&gt;Hi!
I did listen this podcast just a couple of days ago and found it very interesting because I have been tackling with mobile output of websites lately.
I would like to share some of my thoughts about mobile websites to ease up my mind :) (Although people seemed to be more interested in the Mac question). Don&#039;t get bored.
I live in Finland and just this year service providers got the permission to sell mobile phones along with phone deals just like in the UK for years. Before it was illegal to do this and you had to buy your device separetly from the deal. (Hope you understand :) Because of this 3G phone sales have increased rapidly and atleast I have high hopes that mobile browsing will come more popular.
Tarifs are still too high unless you take some kind of data deal (I have a 384 kbs connection and it costs 30 € a month in comparison to my 2048 kbs broadband connection which costs 36 € per month). As more and more people are getting these it comes important to think if your website needs an out put for mobile devices. But like you said in the podcast the time isn&#039;t probably right to invest a lot of time and money to this unless it&#039;s critical to your business.
The browser differences are too big to ensure a website design that would look as supposed on every device.  I&#039;ve come to the conclusion that it is best to design with standards and hope that the different browsers show your site atleast in an understandable way. I hate this as like my sites to render the same way in every browser but it just isn&#039;t possible.
Ofcourse you must test your site with different mobile devices and browsers but this could be more easily said than done. For starters who owns or can access more than one or two mobile devices for test purposes. Your friends will hate you if you are always after their phones and the cost will be high if you are planning to buy several 3G or highend phones (which people are using for browsing if any). There are some emulators from different companies but it just isn&#039;t the same. As you said there are about 160 different devices and over 40 browsers to begin with :)
Some browsershave Flash players, JavaScript, Cookies and CSS support or some combination of these. Usually the execution of these features is lacking so you can&#039;t really trust anything just hope. Some are plain XHTML browsers showing nothing but the fact if you have designed your site well with standards or poorly. There are also those browsers (Opera Mini)  that strip elements away and transform your site&#039;s out put to fit the small screen. The horrors of the designer :)
The Opera 9 is a very good tool for developing mobile sites because it can emulate a small screen browser. Ofcourse it has an outstanding CSS support compared to actual mobile browsers so it tells you the truth very positively.
In Finland we are big Nokia enthusiasts and some of the new genaration S60 (like N73) devices have a browser which shows web sites just like desktop browsers. Even if you provide an alternative CSS stylesheet using the media=&quot;handheld&quot; atribute. It is absolutely horrible to browse a site with 240x320 px screen which is designed to computer screens. I don&#039;t know what the engineers at Nokia have thought  when dropping this standard.  In theory life of the designer would be more easy if you just could provide two stylesheets in this way.
Well the browser supports JavaScript and Cookies so I got an idea (after reading some A List Apart) why not to allow users to change the whole stylesheet on the fly by clicking a button or link. I begged my friend to write this script and it actually works. The Nokia users (and other not getting the mobile stylesheet the normal way by defining the media atribute for CSS links) can now view the site in a more convenient way if they choose so. Ofcourse it is a whole different thing to teach people to use this kind of feature. The other thing with this is that if you design you mobile stylesheet in a flexible way not only the mobile users can benefit from it. Users having probles accessing the site for example due to poor sight can use also this alternative browsing view for better accessibility because it works also when using a desktop computer. I think it would be unreasonable to use this much work and effort for just for one mobile browser. Unless if you are getting paid for it ;P
The script uses JavaScript (we used the Prototype  library to ease up the work) and Cookies so its not a perfect solution and needs a lot of developement still.  Anyway it is nice to develope and learn something new and geeting your satisfaction from it. Sorry for writing this novel but I had to purge my mind and share this idea with others.
The script is running on two different sites:
&lt;a href=&quot;http://www.bf-engineering.fi&quot; rel=&quot;nofollow&quot;&gt;http://www.bf-engineering.fi&lt;/a&gt; (It is in Finnish so beware but you can find the magic button from the the top left of the browser view.)
&lt;a href=&quot;http://www.avecmobile.com&quot; rel=&quot;nofollow&quot;&gt;http://www.avecmobile.com&lt;/a&gt; (This site was updated just yesterday and some history payload needs to be corrected still. The site is running on Typo3 CMS. Magic link is in the left navigation bar.)
A couple of links for the mobile web designer:
&lt;a href=&quot;http://www.w3.org/TR/2005/WD-mobile-bp-20051017/&quot; rel=&quot;nofollow&quot;&gt;http://www.w3.org/TR/2005/WD-mobile-bp-20051017/&lt;/a&gt;
&lt;a href=&quot;http://www.forum.nokia.com/info/sw.nokia.com/id/7f3f1424-b51e-4067-a3ef-acaab08e484f/XHTML_Guidelines_For_Creating_Web_Content_v1_3_en.pdf.html&quot; rel=&quot;nofollow&quot;&gt;http://www.forum.nokia.com/info/sw.nokia.com/id/7f3f1424-b51e-4067-a3ef-acaab08e484f/XHTML_Guidelines_For_Creating_Web_Content_v1_3_en.pdf.html&lt;/a&gt;
&lt;a href=&quot;http://www.forum.nokia.com/info/sw.nokia.com/id/1e66bc62-0a3e-4e36-b8c9-4e20e8b8cdd8/Overview_of_AJAX_Support_in_Nokia_Web_Browser_v1_0_en.pdf.html&quot; rel=&quot;nofollow&quot;&gt;http://www.forum.nokia.com/info/sw.nokia.com/id/1e66bc62-0a3e-4e36-b8c9-4e20e8b8cdd8/Overview_of_AJAX_Support_in_Nokia_Web_Browser_v1_0_en.pdf.html&lt;/a&gt;&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Hi!<br />
I did listen this podcast just a couple of days ago and found it very interesting because I have been tackling with mobile output of websites lately.<br />
I would like to share some of my thoughts about mobile websites to ease up my mind :) (Although people seemed to be more interested in the Mac question). Don&#8217;t get bored.<br />
I live in Finland and just this year service providers got the permission to sell mobile phones along with phone deals just like in the UK for years. Before it was illegal to do this and you had to buy your device separetly from the deal. (Hope you understand :) Because of this 3G phone sales have increased rapidly and atleast I have high hopes that mobile browsing will come more popular.<br />
Tarifs are still too high unless you take some kind of data deal (I have a 384 kbs connection and it costs 30 € a month in comparison to my 2048 kbs broadband connection which costs 36 € per month). As more and more people are getting these it comes important to think if your website needs an out put for mobile devices. But like you said in the podcast the time isn&#8217;t probably right to invest a lot of time and money to this unless it&#8217;s critical to your business.<br />
The browser differences are too big to ensure a website design that would look as supposed on every device.  I&#8217;ve come to the conclusion that it is best to design with standards and hope that the different browsers show your site atleast in an understandable way. I hate this as like my sites to render the same way in every browser but it just isn&#8217;t possible.<br />
Ofcourse you must test your site with different mobile devices and browsers but this could be more easily said than done. For starters who owns or can access more than one or two mobile devices for test purposes. Your friends will hate you if you are always after their phones and the cost will be high if you are planning to buy several 3G or highend phones (which people are using for browsing if any). There are some emulators from different companies but it just isn&#8217;t the same. As you said there are about 160 different devices and over 40 browsers to begin with :)<br />
Some browsershave Flash players, JavaScript, Cookies and CSS support or some combination of these. Usually the execution of these features is lacking so you can&#8217;t really trust anything just hope. Some are plain XHTML browsers showing nothing but the fact if you have designed your site well with standards or poorly. There are also those browsers (Opera Mini)  that strip elements away and transform your site&#8217;s out put to fit the small screen. The horrors of the designer :)<br />
The Opera 9 is a very good tool for developing mobile sites because it can emulate a small screen browser. Ofcourse it has an outstanding CSS support compared to actual mobile browsers so it tells you the truth very positively.<br />
In Finland we are big Nokia enthusiasts and some of the new genaration S60 (like N73) devices have a browser which shows web sites just like desktop browsers. Even if you provide an alternative CSS stylesheet using the media=&#8221;handheld&#8221; atribute. It is absolutely horrible to browse a site with 240&#215;320 px screen which is designed to computer screens. I don&#8217;t know what the engineers at Nokia have thought  when dropping this standard.  In theory life of the designer would be more easy if you just could provide two stylesheets in this way.<br />
Well the browser supports JavaScript and Cookies so I got an idea (after reading some A List Apart) why not to allow users to change the whole stylesheet on the fly by clicking a button or link. I begged my friend to write this script and it actually works. The Nokia users (and other not getting the mobile stylesheet the normal way by defining the media atribute for CSS links) can now view the site in a more convenient way if they choose so. Ofcourse it is a whole different thing to teach people to use this kind of feature. The other thing with this is that if you design you mobile stylesheet in a flexible way not only the mobile users can benefit from it. Users having probles accessing the site for example due to poor sight can use also this alternative browsing view for better accessibility because it works also when using a desktop computer. I think it would be unreasonable to use this much work and effort for just for one mobile browser. Unless if you are getting paid for it ;P<br />
The script uses JavaScript (we used the Prototype  library to ease up the work) and Cookies so its not a perfect solution and needs a lot of developement still.  Anyway it is nice to develope and learn something new and geeting your satisfaction from it. Sorry for writing this novel but I had to purge my mind and share this idea with others.<br />
The script is running on two different sites:<br />
<a href="http://www.bf-engineering.fi" rel="nofollow">http://www.bf-engineering.fi</a> (It is in Finnish so beware but you can find the magic button from the the top left of the browser view.)<br />
<a href="http://www.avecmobile.com" rel="nofollow">http://www.avecmobile.com</a> (This site was updated just yesterday and some history payload needs to be corrected still. The site is running on Typo3 CMS. Magic link is in the left navigation bar.)<br />
A couple of links for the mobile web designer:<br />
<a href="http://www.w3.org/TR/2005/WD-mobile-bp-20051017/" rel="nofollow">http://www.w3.org/TR/2005/WD-mobile-bp-20051017/</a><br />
<a href="http://www.forum.nokia.com/info/sw.nokia.com/id/7f3f1424-b51e-4067-a3ef-acaab08e484f/XHTML_Guidelines_For_Creating_Web_Content_v1_3_en.pdf.html" rel="nofollow">http://www.forum.nokia.com/info/sw.nokia.com/id/7f3f1424-b51e-4067-a3ef-acaab08e484f/XHTML_Guidelines_For_Creating_Web_Content_v1_3_en.pdf.html</a><br />
<a href="http://www.forum.nokia.com/info/sw.nokia.com/id/1e66bc62-0a3e-4e36-b8c9-4e20e8b8cdd8/Overview_of_AJAX_Support_in_Nokia_Web_Browser_v1_0_en.pdf.html" rel="nofollow">http://www.forum.nokia.com/info/sw.nokia.com/id/1e66bc62-0a3e-4e36-b8c9-4e20e8b8cdd8/Overview_of_AJAX_Support_in_Nokia_Web_Browser_v1_0_en.pdf.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary</title>
		<link>http://boagworld.com/podcast/podcast-47-the-mobile-web/#comment-1996</link>
		<dc:creator>Gary</dc:creator>
		<pubDate>Fri, 29 Sep 2006 09:09:04 +0000</pubDate>
		<guid isPermaLink="false">http://wpboagworld:83/uncategorized/podcast-47-the-mobile-web#comment-1996</guid>
		<description><![CDATA[&lt;p&gt;Paul recommends another book in this episode, a designer&#039;s introduction to javascript - does anyone know where I can get this book from?&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Paul recommends another book in this episode, a designer&#8217;s introduction to javascript &#8211; does anyone know where I can get this book from?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://boagworld.com/podcast/podcast-47-the-mobile-web/#comment-1995</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Tue, 26 Sep 2006 15:56:46 +0000</pubDate>
		<guid isPermaLink="false">http://wpboagworld:83/uncategorized/podcast-47-the-mobile-web#comment-1995</guid>
		<description><![CDATA[&lt;p&gt;Great show, I have just discovered BoagWorld recently and am slowly catching up.
I agree with your MAC reasoning.  The MAC users are dying a slow and horrible death, but it isn&#039;t too far off in the future.
Also, with all the phonebrowser talk, why isn&#039;t there and example of BoagWorld in a phone format...muhahahahaha!
Last but not least do you have recommendations to see what type of formatting works best in small format.
Like should we use tables or not, since CSS sounds out for now, what will work.  A great link would be helpful.
Thanks for the great show!!!!
Ron&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Great show, I have just discovered BoagWorld recently and am slowly catching up.<br />
I agree with your MAC reasoning.  The MAC users are dying a slow and horrible death, but it isn&#8217;t too far off in the future.<br />
Also, with all the phonebrowser talk, why isn&#8217;t there and example of BoagWorld in a phone format&#8230;muhahahahaha!<br />
Last but not least do you have recommendations to see what type of formatting works best in small format.<br />
Like should we use tables or not, since CSS sounds out for now, what will work.  A great link would be helpful.<br />
Thanks for the great show!!!!<br />
Ron</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://boagworld.com/podcast/podcast-47-the-mobile-web/#comment-1994</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Fri, 01 Sep 2006 14:50:27 +0000</pubDate>
		<guid isPermaLink="false">http://wpboagworld:83/uncategorized/podcast-47-the-mobile-web#comment-1994</guid>
		<description><![CDATA[&lt;p&gt;Mobile web:
I live in South Africa where broadband is still mostly for the fairly wealthy. People with dial-up also can&#039;t really afford to surf the internet either.
I am creating a mobile site for my scout troop so that our scouts can access calendar details etc from their cellphones whenever they have the need.
Our cost is R2/mb of data and with no graphics on the site, it&#039;s not really a viable commercial exercise in terms of branding, but by giving the user information that they want quickly will make people have a &quot;better online experience&quot;.
It should also work well in South Africa because I definitely believe that way more people here have cellphones than computers that can connect to the web.
&quot;Poorer&quot; countries (in my opinion) will embrace the mobile web faster than the &quot;richer&quot; countries, because in the UK or USA you cud probably just pull out your laptop and connect through wi-fi whenever you want to.
Here you can&#039;t. Perhaps you don&#039;t own a laptop, or there is no real wi-fi infrastructure. That&#039;s why people here (especially the teens) are far more clued up on cellphone capabilities - because they are less likely to have a computer and therefore spend more time using the internet/chat rooms etc on their cellphones.
Time will tell though.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Mobile web:<br />
I live in South Africa where broadband is still mostly for the fairly wealthy. People with dial-up also can&#8217;t really afford to surf the internet either.<br />
I am creating a mobile site for my scout troop so that our scouts can access calendar details etc from their cellphones whenever they have the need.<br />
Our cost is R2/mb of data and with no graphics on the site, it&#8217;s not really a viable commercial exercise in terms of branding, but by giving the user information that they want quickly will make people have a &#8220;better online experience&#8221;.<br />
It should also work well in South Africa because I definitely believe that way more people here have cellphones than computers that can connect to the web.<br />
&#8220;Poorer&#8221; countries (in my opinion) will embrace the mobile web faster than the &#8220;richer&#8221; countries, because in the UK or USA you cud probably just pull out your laptop and connect through wi-fi whenever you want to.<br />
Here you can&#8217;t. Perhaps you don&#8217;t own a laptop, or there is no real wi-fi infrastructure. That&#8217;s why people here (especially the teens) are far more clued up on cellphone capabilities &#8211; because they are less likely to have a computer and therefore spend more time using the internet/chat rooms etc on their cellphones.<br />
Time will tell though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek</title>
		<link>http://boagworld.com/podcast/podcast-47-the-mobile-web/#comment-1993</link>
		<dc:creator>Derek</dc:creator>
		<pubDate>Fri, 01 Sep 2006 13:21:45 +0000</pubDate>
		<guid isPermaLink="false">http://wpboagworld:83/uncategorized/podcast-47-the-mobile-web#comment-1993</guid>
		<description><![CDATA[&lt;p&gt;The problem with including images as attachments in your email is that it&#039;s a HUGE increase in size and bandwidth and can be particularly annoying to lower bandwidth users who need to wait to download images when popping mail.
I&#039;ve always thought linking works, but PDF is universal, an attached PDF will be guaranteed to be viewable across every platform with PDF viewers.  Of course this adds to size as well.
-D&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>The problem with including images as attachments in your email is that it&#8217;s a HUGE increase in size and bandwidth and can be particularly annoying to lower bandwidth users who need to wait to download images when popping mail.<br />
I&#8217;ve always thought linking works, but PDF is universal, an attached PDF will be guaranteed to be viewable across every platform with PDF viewers.  Of course this adds to size as well.<br />
-D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Boag</title>
		<link>http://boagworld.com/podcast/podcast-47-the-mobile-web/#comment-1992</link>
		<dc:creator>Paul Boag</dc:creator>
		<pubDate>Fri, 01 Sep 2006 09:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://wpboagworld:83/uncategorized/podcast-47-the-mobile-web#comment-1992</guid>
		<description><![CDATA[&lt;p&gt;Oh its so easy! lol&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Oh its so easy! lol</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard (Pasty Man) Quick</title>
		<link>http://boagworld.com/podcast/podcast-47-the-mobile-web/#comment-1991</link>
		<dc:creator>Richard (Pasty Man) Quick</dc:creator>
		<pubDate>Fri, 01 Sep 2006 03:55:18 +0000</pubDate>
		<guid isPermaLink="false">http://wpboagworld:83/uncategorized/podcast-47-the-mobile-web#comment-1991</guid>
		<description><![CDATA[&lt;p&gt;I doubt you need a mac to test it on, since most users use Opera or Firefox on Macs.&quot;
Where did you get that from?
I&#039;d say most Mac users use Safari.  That&#039;s based on persoanl experience not hard stats, but I&#039;d be interested if you&#039;ve got stats otherwise.
BTW - Firefox on the Mac doesn&#039;t render 100% the same as on the PC.  Font sizes and margins can vary.  It&#039;s close - but not 100%.
Much more than someone who is visually impaired visiting your site once in a million years. Worrying about that long shot
That&#039;s totally different.  It&#039;s a human rights issue.
If you decide to support Safari on a Mac or not that&#039;s a business decision which you&#039;re entitled to make.
You&#039;re not entitled to make a decision as to whether a disabled person is able to access your site.
You&#039;ve got a legal and moral responsibility to make reasonable efforts to ensure your site&#039;s accessible to people with disabilties.
Besides - if you&#039;re using web standards your site will pretty much be bascially accessible with minimal effort - and if you&#039;re not then you shouldn&#039;t be entitled to call yourself a professional web designer (not my idea).&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>I doubt you need a mac to test it on, since most users use Opera or Firefox on Macs.&#8221;<br />
Where did you get that from?<br />
I&#8217;d say most Mac users use Safari.  That&#8217;s based on persoanl experience not hard stats, but I&#8217;d be interested if you&#8217;ve got stats otherwise.<br />
BTW &#8211; Firefox on the Mac doesn&#8217;t render 100% the same as on the PC.  Font sizes and margins can vary.  It&#8217;s close &#8211; but not 100%.<br />
Much more than someone who is visually impaired visiting your site once in a million years. Worrying about that long shot<br />
That&#8217;s totally different.  It&#8217;s a human rights issue.<br />
If you decide to support Safari on a Mac or not that&#8217;s a business decision which you&#8217;re entitled to make.<br />
You&#8217;re not entitled to make a decision as to whether a disabled person is able to access your site.<br />
You&#8217;ve got a legal and moral responsibility to make reasonable efforts to ensure your site&#8217;s accessible to people with disabilties.<br />
Besides &#8211; if you&#8217;re using web standards your site will pretty much be bascially accessible with minimal effort &#8211; and if you&#8217;re not then you shouldn&#8217;t be entitled to call yourself a professional web designer (not my idea).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd</title>
		<link>http://boagworld.com/podcast/podcast-47-the-mobile-web/#comment-1990</link>
		<dc:creator>Todd</dc:creator>
		<pubDate>Fri, 01 Sep 2006 02:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://wpboagworld:83/uncategorized/podcast-47-the-mobile-web#comment-1990</guid>
		<description><![CDATA[&lt;p&gt;Hi
Was irritated to hear Paul suggesting testing for a mac wasn&#039;t worth the effort, you need to read more. With virus free macs, the ipod, the strength of products/stores/stocks coming from Apple, you should be thinking about it. Much more than someone who is visually impaired visiting your site once in a million years. Worrying about that long shot
Next, the comment print designers can&#039;t do the web. That was the kicker, you are once again misinformed. Web designers can&#039;t do print. Know nothing about resolution, colour spaces, trapping, RIP&#039;s, and a million other details that make up a proper print job. When you mentioned simply making a &#039;page look pretty&#039;, you indicated how little you know outside of only what you do.
In closing, if I understand Paul&#039;s role correctly, he is purely a designer for Headscape? Not able to develop/program. I would suggest before you disregard the skills of a print professional as only someone who makes a &#039;page look pretty&#039;, you should spend more time at least developing the skills required for what you are currently doing. Designing is only a small part of web development....making a page look pretty is only a small part of print.
My 2bits.
tj&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>Hi<br />
Was irritated to hear Paul suggesting testing for a mac wasn&#8217;t worth the effort, you need to read more. With virus free macs, the ipod, the strength of products/stores/stocks coming from Apple, you should be thinking about it. Much more than someone who is visually impaired visiting your site once in a million years. Worrying about that long shot<br />
Next, the comment print designers can&#8217;t do the web. That was the kicker, you are once again misinformed. Web designers can&#8217;t do print. Know nothing about resolution, colour spaces, trapping, RIP&#8217;s, and a million other details that make up a proper print job. When you mentioned simply making a &#8216;page look pretty&#8217;, you indicated how little you know outside of only what you do.<br />
In closing, if I understand Paul&#8217;s role correctly, he is purely a designer for Headscape? Not able to develop/program. I would suggest before you disregard the skills of a print professional as only someone who makes a &#8216;page look pretty&#8217;, you should spend more time at least developing the skills required for what you are currently doing. Designing is only a small part of web development&#8230;.making a page look pretty is only a small part of print.<br />
My 2bits.<br />
tj</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcus</title>
		<link>http://boagworld.com/podcast/podcast-47-the-mobile-web/#comment-1989</link>
		<dc:creator>Marcus</dc:creator>
		<pubDate>Thu, 31 Aug 2006 20:01:38 +0000</pubDate>
		<guid isPermaLink="false">http://wpboagworld:83/uncategorized/podcast-47-the-mobile-web#comment-1989</guid>
		<description><![CDATA[&lt;p&gt;&quot;Macs are dead,&quot;
depends on your market actually, I ran a couple sites one I got about 20% mac users, anther I got about 5%. I doubt you need a mac to test it on, since most users use Opera or Firefox on Macs.&lt;/p&gt;
]]></description>
		<content:encoded><![CDATA[<p>&#8220;Macs are dead,&#8221;<br />
depends on your market actually, I ran a couple sites one I got about 20% mac users, anther I got about 5%. I doubt you need a mac to test it on, since most users use Opera or Firefox on Macs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced

 Served from: boagworld.com @ 2013-05-19 08:11:47 by W3 Total Cache -->