
<?phpxml 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/"
>
<channel>
<title>jigphone - mobile development links  / Mobile Web</title>
<link>http://jigphone.com</link>
<description>Discover and share news, articles, applications and websites for mobile software development</description>
<pubDate>Sun, 05 Jul 2009 09:43:27 MST</pubDate>
<language>en</language>
<item>
<title><![CDATA[Masabists: How Do Transcoders Affect HTTPS?]]></title>
<link>http://jigphone.com/story.php?title=Masabists_How_Do_Transcoders_Affect_HTTPS</link>
<comments>http://jigphone.com/story.php?title=Masabists_How_Do_Transcoders_Affect_HTTPS</comments>
<pubDate>Sun, 05 Jul 2009 09:43:27 MST</pubDate>
<dc:creator>jigphone</dc:creator>
<category>Mobile Web</category>
<guid>http://jigphone.com/story.php?title=Masabists_How_Do_Transcoders_Affect_HTTPS</guid>
<description><![CDATA[After reading the interesting discussion about mobile transcoders and HTTPS security on the MoMo London mailing list (may require sign-in), based on some related discussion around the new W3C guidelines for transcoding, I thought there was some value in a blog post which explains the issues from more of a layman's perspective. ]]></description>
</item>

<item>
<title><![CDATA[W3C: Mobile Web Best Practices 1.0]]></title>
<link>http://jigphone.com/story.php?title=W3C_Mobile_Web_Best_Practices_1-0</link>
<comments>http://jigphone.com/story.php?title=W3C_Mobile_Web_Best_Practices_1-0</comments>
<pubDate>Thu, 09 Oct 2008 06:12:49 MST</pubDate>
<dc:creator>javame</dc:creator>
<category>Mobile Web</category>
<guid>http://jigphone.com/story.php?title=W3C_Mobile_Web_Best_Practices_1-0</guid>
<description><![CDATA[This document specifies Best Practices for delivering Web content to mobile devices. The principal objective is to improve the user experience of the Web when accessed from such devices. ]]></description>
</item>

<item>
<title><![CDATA[Mobile Browser Based Applications (Gears  and BONDI)]]></title>
<link>http://jigphone.com/story.php?title=Mobile_Browser_Based_Applications_Gears__and_BONDI</link>
<comments>http://jigphone.com/story.php?title=Mobile_Browser_Based_Applications_Gears__and_BONDI</comments>
<pubDate>Sat, 20 Sep 2008 16:55:27 MST</pubDate>
<dc:creator>jigphone</dc:creator>
<category>Mobile Web</category>
<guid>http://jigphone.com/story.php?title=Mobile_Browser_Based_Applications_Gears__and_BONDI</guid>
<description><![CDATA[Two requirements need to be met before browser based technologies are capable being a general replacement for applications. ... There are at least two cross platform initiatives dedicated to solving these problem, Google's Gears and the OMTP's BONDI project. ]]></description>
</item>

<item>
<title><![CDATA[Make you Mobile Site Visible With Meta Data]]></title>
<link>http://jigphone.com/story.php?title=Make_you_Mobile_Site_Visible_With_Meta_Data</link>
<comments>http://jigphone.com/story.php?title=Make_you_Mobile_Site_Visible_With_Meta_Data</comments>
<pubDate>Wed, 10 Sep 2008 09:34:46 MST</pubDate>
<dc:creator>jigphone</dc:creator>
<category>Mobile Web</category>
<guid>http://jigphone.com/story.php?title=Make_you_Mobile_Site_Visible_With_Meta_Data</guid>
<description><![CDATA[Discovery is one biggest problems for mobile web sites.  A user wants to visit a site on her mobile phone.  Let's say the site is example.com. Does she go to example.com and hope the example.com designers are sharp enough to identify her browser and redirect to suitable mobile content? Or does she try example.mobi, m.example.com, mobile.example.com, wap.example.com or example.com/mobile?  Not only do users have trouble with this but so do search engines. ]]></description>
</item>

<item>
<title><![CDATA[Mobile design web resources]]></title>
<link>http://jigphone.com/story.php?title=Mobile_design_web_resources</link>
<comments>http://jigphone.com/story.php?title=Mobile_design_web_resources</comments>
<pubDate>Fri, 05 Sep 2008 20:16:21 MST</pubDate>
<dc:creator>coolguy</dc:creator>
<category>Mobile Web</category>
<guid>http://jigphone.com/story.php?title=Mobile_design_web_resources</guid>
<description><![CDATA[What I put here is good stuff for getting started in mobile design. Contents include feeds from leading mobile design bloggers, links to key online and paper resources, and a bookmark feed. ]]></description>
</item>

<item>
<title><![CDATA[Google co-founder expects Chrome for Android]]></title>
<link>http://jigphone.com/story.php?title=Google_co-founder_expects_Chrome_for_Android-1</link>
<comments>http://jigphone.com/story.php?title=Google_co-founder_expects_Chrome_for_Android-1</comments>
<pubDate>Wed, 03 Sep 2008 14:41:41 MST</pubDate>
<dc:creator>javame</dc:creator>
<category>Mobile Web</category>
<guid>http://jigphone.com/story.php?title=Google_co-founder_expects_Chrome_for_Android-1</guid>
<description><![CDATA[Google's new Chrome browser is for PCs today, but company co-founder Sergey Brin expects the technology will make its way to Android, the company's mobile phone operating system and software suite. ]]></description>
</item>

<item>
<title><![CDATA[New WebKit 3 Features SVG, XPath, Developer Tools]]></title>
<link>http://jigphone.com/story.php?title=New_WebKit_3_Features_SVG_XPath_Developer_Tools</link>
<comments>http://jigphone.com/story.php?title=New_WebKit_3_Features_SVG_XPath_Developer_Tools</comments>
<pubDate>Sun, 31 Aug 2008 20:51:13 MST</pubDate>
<dc:creator>jigphone</dc:creator>
<category>Mobile Web</category>
<guid>http://jigphone.com/story.php?title=New_WebKit_3_Features_SVG_XPath_Developer_Tools</guid>
<description><![CDATA[WebKit, the open-source browser toolkit that's behind Apple's Safari, KDE Konqueror, Adobe's AIR, Google's Android, and numerous mobile browsers, saw a 3.0 release recently, supporting SVG, some of the CSS 3 standard, XPath, and many performance and feature improvements. ]]></description>
</item>

</channel>
</rss>
