<?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"
	>
<channel>
	<title>Comments on: dotMobi Mobile Web Developers Guide</title>
	<atom:link href="http://jamesangus.ucantblamem.com/general/dotmobi-mobile-web-developers-guide/82/feed/" rel="self" type="application/rss+xml" />
	<link>http://jamesangus.ucantblamem.com/general/dotmobi-mobile-web-developers-guide/82/</link>
	<description>Hi, I'm James Angus. I have a greed for learning, an obsession with all things web; I am in love with standards, accessibility, creating things for use by people and yes, this site was designed on a mac.</description>
	<pubDate>Fri, 16 May 2008 11:58:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Grace</title>
		<link>http://jamesangus.ucantblamem.com/general/dotmobi-mobile-web-developers-guide/82/#comment-101</link>
		<dc:creator>Grace</dc:creator>
		<pubDate>Mon, 30 Apr 2007 14:38:38 +0000</pubDate>
		<guid isPermaLink="false">http://jamesangus.ucantblamem.com/general/dotmobi-mobile-web-developers-guide/82/#comment-101</guid>
		<description>Hi James
Great list! I work on a service called www.zinadoo.com that provides users with an easy to use tool to create a mobile site. All mobile sites created are automatically compliant with .mobi’s style guides, many of which you mentioned above. We've a new version due out next Monday (7th) and many of our new features cover some of the site features you’ve mentioned above also (Click to dial, assigning access keys etc)
Would love you to check it out and let us know what you think.
P.S.  it's all free!</description>
		<content:encoded><![CDATA[<p>Hi James<br />
Great list! I work on a service called <a href="http://www.zinadoo.com" rel="nofollow">http://www.zinadoo.com</a> that provides users with an easy to use tool to create a mobile site. All mobile sites created are automatically compliant with .mobi’s style guides, many of which you mentioned above. We&#8217;ve a new version due out next Monday (7th) and many of our new features cover some of the site features you’ve mentioned above also (Click to dial, assigning access keys etc)<br />
Would love you to check it out and let us know what you think.<br />
P.S.  it&#8217;s all free!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ucantblamem</title>
		<link>http://jamesangus.ucantblamem.com/general/dotmobi-mobile-web-developers-guide/82/#comment-95</link>
		<dc:creator>ucantblamem</dc:creator>
		<pubDate>Fri, 23 Mar 2007 03:21:31 +0000</pubDate>
		<guid isPermaLink="false">http://jamesangus.ucantblamem.com/general/dotmobi-mobile-web-developers-guide/82/#comment-95</guid>
		<description>@lee - to answer your questions:

1.  While some of the "Desktop" companies we're familiar with like Microsoft and Opera do offer Mobile browsers, there isn't really a majority stakeholder like IE6 in the Mobile environment (yet). By default, most phones will have a browser built by the Manufacturer. So, what we have is a number of different browsers (think one per manufacturer), which all have enough market share to warrant adequate testing. To make matters worse, on the desktop we're used to having periodic updates that we can simply download, but there is no viable mechanism like this for phones. The result is that every new phone gets the latest version of the browser, which means: Multiple browsers (from multiple manufacturers), with multiple versions of each out in the wild - all of which have similar market share. GOOD TIMES HUH? :P

Luckily, thanks to the &lt;a href="http://www.openmobilealliance.org/tech/affiliates/wap/wapindex.html" title="Wireless Application Protocol" rel="nofollow"&gt;WAP &lt;/a&gt; standards, their rendering engines are pretty basic/similar.

2.  Yes and no. If you're a standards-based developer who knows that "Pixel-perfection" is a dead religion, then you're probably not going to have any issues. There are many different resolutions, some portrait and some landscape, so text will wrap etc... The only major issue you'll want to avoid is images being too large for small devices. Images should be used sparingly anyway, but if you keep them less than 120 pixels wide, you shouldn't have any troubles in about 99% of cases.</description>
		<content:encoded><![CDATA[<p>@lee - to answer your questions:</p>
<p>1.  While some of the &#8220;Desktop&#8221; companies we&#8217;re familiar with like Microsoft and Opera do offer Mobile browsers, there isn&#8217;t really a majority stakeholder like IE6 in the Mobile environment (yet). By default, most phones will have a browser built by the Manufacturer. So, what we have is a number of different browsers (think one per manufacturer), which all have enough market share to warrant adequate testing. To make matters worse, on the desktop we&#8217;re used to having periodic updates that we can simply download, but there is no viable mechanism like this for phones. The result is that every new phone gets the latest version of the browser, which means: Multiple browsers (from multiple manufacturers), with multiple versions of each out in the wild - all of which have similar market share. GOOD TIMES HUH? :P</p>
<p>Luckily, thanks to the <a href="http://www.openmobilealliance.org/tech/affiliates/wap/wapindex.html" title="Wireless Application Protocol" rel="nofollow">WAP </a> standards, their rendering engines are pretty basic/similar.</p>
<p>2.  Yes and no. If you&#8217;re a standards-based developer who knows that &#8220;Pixel-perfection&#8221; is a dead religion, then you&#8217;re probably not going to have any issues. There are many different resolutions, some portrait and some landscape, so text will wrap etc&#8230; The only major issue you&#8217;ll want to avoid is images being too large for small devices. Images should be used sparingly anyway, but if you keep them less than 120 pixels wide, you shouldn&#8217;t have any troubles in about 99% of cases.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee</title>
		<link>http://jamesangus.ucantblamem.com/general/dotmobi-mobile-web-developers-guide/82/#comment-94</link>
		<dc:creator>Lee</dc:creator>
		<pubDate>Fri, 23 Mar 2007 02:55:34 +0000</pubDate>
		<guid isPermaLink="false">http://jamesangus.ucantblamem.com/general/dotmobi-mobile-web-developers-guide/82/#comment-94</guid>
		<description>Great to see a shorter put together list of items to pay attention to when it comes to the development of pages for mobiles. I think a lot of those items would come from learning from your mistakes more then anything.

Whilst I have never delged into the mobile websites side of things, its something I think I may be having to look into down the track. Whilst in my opinion this isn't a high enough demand for it at the moment to justify the learning time in it I think that you already having the experience with would work as a great aide for you down the track if/when mobile websites really start to take off.

Some questions:

1. There's obviously different browsers out there for different phones (mine using IE as standard [windows mobile] and have seen Opera taking some good share), do you encounter as many browser differences as you do in a 'real' web environment as you do in the mobile environment.

2. Screen resolutions, phones have different resolutions just like computers, do these have a great affect on the design of these mobile websites?</description>
		<content:encoded><![CDATA[<p>Great to see a shorter put together list of items to pay attention to when it comes to the development of pages for mobiles. I think a lot of those items would come from learning from your mistakes more then anything.</p>
<p>Whilst I have never delged into the mobile websites side of things, its something I think I may be having to look into down the track. Whilst in my opinion this isn&#8217;t a high enough demand for it at the moment to justify the learning time in it I think that you already having the experience with would work as a great aide for you down the track if/when mobile websites really start to take off.</p>
<p>Some questions:</p>
<p>1. There&#8217;s obviously different browsers out there for different phones (mine using IE as standard [windows mobile] and have seen Opera taking some good share), do you encounter as many browser differences as you do in a &#8216;real&#8217; web environment as you do in the mobile environment.</p>
<p>2. Screen resolutions, phones have different resolutions just like computers, do these have a great affect on the design of these mobile websites?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
