<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://mobiforge.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>mobiForge Recent Content</title>
 <link>http://mobiforge.com/rssfeed</link>
 <description>mobiForge Content Feed</description>
 <language>en</language>
<item>
 <title>HTML5 for the Mobile Web - Part I: Introduction</title>
 <link>http://mobiforge.com/developing/story/html5-mobile-web-part-i-introduction</link>
 <description>&lt;p&gt;There has been much interest lately around HTML5 and its readiness for production environments and whether HTML5 apps should be used over native apps. This has been due, in large part, to the high-profile defections of tech behemoths such as Facebook and LinkedIn away from HTML5 to native apps for their core mobile services. &lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/html5-mobile-web-part-i-introduction&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/html5-mobile-web-part-i-introduction#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/browsers">Browsers</category>
 <category domain="http://mobiforge.com/tutorial">Tutorial</category>
 <category domain="http://mobiforge.com/html5-0">HTML5</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/7991</wfw:commentRss>
 <pubDate>Thu, 16 May 2013 14:57:05 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">7991 at http://mobiforge.com</guid>
</item>
<item>
 <title>Facebook Home, Google and Android: who wins and who loses?</title>
 <link>http://mobiforge.com/testing/blog/facebook-home-google-and-android-who-wins-and-who-loses</link>
 <description>&lt;p&gt;After the &lt;a href=&quot;http://mobiforge.com/testing/blog/what-facebook-home-and-how-install-it-android-phones&quot; class=&quot;bb-url&quot;&gt;Overview of Facebook Home and how to install it on Android&lt;/a&gt;, it&#039;s time to have a look at Facebook Home from a business and developer perspective.&lt;/p&gt;
&lt;p&gt;From a strategic point of view, &lt;span style=&quot;font-weight:bold&quot;&gt;Facebook Home&lt;/span&gt; certainly &lt;span style=&quot;font-weight:bold&quot;&gt;has the potential&lt;/span&gt; to capture Android users, divert them away from Google’s services and draw them closer to the Facebook platform. So it is certainly a threat to Google in that it reduces Android’s flexibility, and therefore the strength of Google’s position.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/blog/facebook-home-google-and-android-who-wins-and-who-loses&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/blog/facebook-home-google-and-android-who-wins-and-who-loses#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/analysts">Analysts</category>
 <category domain="http://mobiforge.com/business">Business</category>
 <category domain="http://mobiforge.com/android">Android</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/7989</wfw:commentRss>
 <pubDate>Fri, 10 May 2013 10:27:16 +0000</pubDate>
 <dc:creator>Veruska Anconitano</dc:creator>
 <guid isPermaLink="false">7989 at http://mobiforge.com</guid>
</item>
<item>
 <title>Overview of Facebook Home and how to install on Android</title>
 <link>http://mobiforge.com/testing/blog/overview-facebook-home-and-how-install-android</link>
 <description>&lt;p&gt;Facebook Home made a big splash late last month, but early indications show that users are &lt;a href=&quot;http://www.dazeinfo.com/2013/04/25/facebook-home-looses-ground-thanks-to-user-experience-study/&quot; class=&quot;bb-url&quot;&gt;far from considering&lt;/a&gt; this a &quot;revolution&quot; despite smartphone users around the world &lt;a href=&quot;http://www.androidauthority.com/smartphone-users-spend-time-gaming-183698/&quot; class=&quot;bb-url&quot;&gt;spending 18% of their time&lt;/a&gt; on Facebook.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/blog/overview-facebook-home-and-how-install-android&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/blog/overview-facebook-home-and-how-install-android#comments</comments>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/testers">Testers</category>
 <category domain="http://mobiforge.com/android">Android</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/7983</wfw:commentRss>
 <pubDate>Wed, 08 May 2013 16:31:48 +0000</pubDate>
 <dc:creator>Veruska Anconitano</dc:creator>
 <guid isPermaLink="false">7983 at http://mobiforge.com</guid>
</item>
<item>
 <title>Tracking mobile with Google Analytics</title>
 <link>http://mobiforge.com/running/blog/tracking-mobile-with-google-analytics</link>
 <description>&lt;p&gt;Mobile is becoming more important by the day and the figures speak for themselves: about 1 page out of every 8 was viewed using a mobile device (including tablets and phones) according to recent comScore research and last month Google released a &lt;a href=&quot;http://www.google.com/think/research-studies/creating-moments-that-matter.html&quot;&gt;study&lt;/a&gt; which showed that 77% of mobile searches were performed at home or at work &lt;em&gt;even if a desktop PC was available&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/running/blog/tracking-mobile-with-google-analytics&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/running/blog/tracking-mobile-with-google-analytics#comments</comments>
 <category domain="http://mobiforge.com/Running">Running</category>
 <category domain="http://mobiforge.com/analysts">Analysts</category>
 <category domain="http://mobiforge.com/business">Business</category>
 <category domain="http://mobiforge.com/analytics">Analytics</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/7978</wfw:commentRss>
 <pubDate>Wed, 01 May 2013 17:45:39 +0000</pubDate>
 <dc:creator>mclancy</dc:creator>
 <guid isPermaLink="false">7978 at http://mobiforge.com</guid>
</item>
<item>
 <title>Usability on the mobile Web: best practices and guidelines for designers and developers</title>
 <link>http://mobiforge.com/designing/blog/usability-mobile-web-best-practices-and-guidelines-designers-and-developers</link>
 <description>&lt;p&gt;In this era of technology, &lt;em&gt;we are continuously interacting with things&lt;/em&gt; so it is vital that these interactions form positive experiences for us. This is true not only for objects or products we can physically touch, but equally so for intangibles such as websites.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/usability-mobile-web-best-practices-and-guidelines-designers-and-developers&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/usability-mobile-web-best-practices-and-guidelines-designers-and-developers#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/analysts">Analysts</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/7566</wfw:commentRss>
 <pubDate>Thu, 25 Apr 2013 08:24:33 +0000</pubDate>
 <dc:creator>Editor</dc:creator>
 <guid isPermaLink="false">7566 at http://mobiforge.com</guid>
</item>
<item>
 <title>The most common mistakes in smartphone sites according to Google</title>
 <link>http://mobiforge.com/designing/blog/the-most-common-mistakes-smartphone-sites-according-google</link>
 <description>&lt;p&gt;Google are paying ever more attention to the mobile market and so, developers pay attention when the Big G is making recommendations. Google recently published a &lt;a href=&quot;https://developers.google.com/webmasters/smartphone-sites/common-mistakes&quot; class=&quot;bb-url&quot;&gt;document&lt;/a&gt; on the main mistakes people make when working on mobile websites for smartphones. If you look through the list you can definitely recognize a cornerstone of Google&#039;s approach: &lt;span style=&quot;font-weight:bold&quot;&gt;focus on the end user&lt;/span&gt;. Or put another way, &quot;adopt the approach you want but be aware of your audience&quot;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/the-most-common-mistakes-smartphone-sites-according-google&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/the-most-common-mistakes-smartphone-sites-according-google#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/analysts">Analysts</category>
 <category domain="http://mobiforge.com/business">Business</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/accessibility">Accessibility</category>
 <category domain="http://mobiforge.com/usability">Usability</category>
 <category domain="http://mobiforge.com/gomobi">goMobi</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <category domain="http://mobiforge.com/dotmobi">dotMobi</category>
 <category domain="http://mobiforge.com/mobiforge">mobiForge</category>
 <category domain="http://mobiforge.com/publishing">Publishing</category>
 <category domain="http://mobiforge.com/messaging">Messaging</category>
 <category domain="http://mobiforge.com/public">Public</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/6944</wfw:commentRss>
 <pubDate>Wed, 17 Apr 2013 08:46:46 +0000</pubDate>
 <dc:creator>Veruska Anconitano</dc:creator>
 <guid isPermaLink="false">6944 at http://mobiforge.com</guid>
</item>
<item>
 <title>Global reach and dynamic page weight – is there a correlation?</title>
 <link>http://mobiforge.com/designing/blog/global-reach-and-dynamic-page-weight-%E2%80%93-there-a-correlation</link>
 <description>&lt;p&gt;Many reports on web page sizes issued in recent years point to the same conclusion: the web has a weight problem. The web seems to be gaining weight each year despite the fact that &lt;a href=&quot;http://www.websiteoptimization.com/speed/tweak/psychology-web-performance/&quot;&gt;study&lt;/a&gt; after &lt;a href=&quot;http://www.zdnet.com/blog/btl/googles-marissa-mayer-speed-wins/3925&quot;&gt;study&lt;/a&gt; has shown a strongly negative reaction from users to heavy web pages and resulting loading times.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/global-reach-and-dynamic-page-weight-%E2%80%93-there-a-correlation&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/global-reach-and-dynamic-page-weight-%E2%80%93-there-a-correlation#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/testers">Testers</category>
 <category domain="http://mobiforge.com/analysts">Analysts</category>
 <category domain="http://mobiforge.com/business">Business</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/gomobi">goMobi</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <enclosure url="http://mobiforge.com/sites/mobiforge.com/files/alexa_100.xlsx" length="97497" type="application/vnd.openxmlformats-officedocument.spreadsheetml.sheet" />
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/6323</wfw:commentRss>
 <pubDate>Fri, 05 Apr 2013 17:52:09 +0000</pubDate>
 <dc:creator>ronan</dc:creator>
 <guid isPermaLink="false">6323 at http://mobiforge.com</guid>
</item>
<item>
 <title>Why HTML5 still presents some problems on mobile</title>
 <link>http://mobiforge.com/developing/blog/why-html5-still-presents-some-problems-mobile</link>
 <description>&lt;p&gt;One of the debates of 2013 centres on which approach you should adopt to deliver a great user experience, while keeping costs at an acceptable level. This question often gets parsed as &lt;span style=&quot;font-style:italic&quot;&gt;“HTML5 or native applications?”&lt;/span&gt; or &lt;span style=&quot;font-style:italic&quot;&gt;“HTML or mobile site builders”&lt;/span&gt; or even something else entirely. But with all the vaunted promise of HTML5, just what does that ‘5’ mean when it comes to real world deployments?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/why-html5-still-presents-some-problems-mobile&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/why-html5-still-presents-some-problems-mobile#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/business">Business</category>
 <category domain="http://mobiforge.com/browsers">Browsers</category>
 <category domain="http://mobiforge.com/mobile-design">Mobile Design</category>
 <category domain="http://mobiforge.com/usability">Usability</category>
 <category domain="http://mobiforge.com/dotmobi">dotMobi</category>
 <category domain="http://mobiforge.com/html5-0">HTML5</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/6287</wfw:commentRss>
 <pubDate>Thu, 04 Apr 2013 14:14:46 +0000</pubDate>
 <dc:creator>Veruska Anconitano</dc:creator>
 <guid isPermaLink="false">6287 at http://mobiforge.com</guid>
</item>
<item>
 <title>Why Responsive Web Design is not always the best option for a mobile SEO strategy</title>
 <link>http://mobiforge.com/starting/blog/why-responsive-web-design-not-always-best-option-a-mobile-seo-strategy</link>
 <description>&lt;p&gt;There are a lot of &lt;span style=&quot;font-weight:bold&quot;&gt;misconceptions about what Google is saying about mobile SEO&lt;/span&gt;. First and foremost, Google doesn&#039;t mandate the use of Responsive Web Design (RWD) as best practice for SEO. Google &lt;a href=&quot;https://developers.google.com/webmasters/smartphone-sites/details&quot; class=&quot;bb-url&quot;&gt;expressly says&lt;/a&gt; &lt;span style=&quot;font-style:italic&quot;&gt;&quot;Google does not favor any particular URL format as long as they are all accessible to both Googlebot and Googlebot-Mobile”&lt;/span&gt; the bots Google uses to crawl desktop and Smartphone specific content. And it’s worth noting here that Google is crawling desktop and mobile content separately.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/starting/blog/why-responsive-web-design-not-always-best-option-a-mobile-seo-strategy&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/starting/blog/why-responsive-web-design-not-always-best-option-a-mobile-seo-strategy#comments</comments>
 <category domain="http://mobiforge.com/Starting">Starting</category>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <category domain="http://mobiforge.com/public">Public</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/5942</wfw:commentRss>
 <pubDate>Thu, 21 Mar 2013 14:27:57 +0000</pubDate>
 <dc:creator>Veruska Anconitano</dc:creator>
 <guid isPermaLink="false">5942 at http://mobiforge.com</guid>
</item>
<item>
 <title>Performance is money, part 1: the end-user&#039;s wallet</title>
 <link>http://mobiforge.com/designing/blog/performance-money-part-1-end-users-wallet</link>
 <description>&lt;p&gt;Most web developers are familiar with the maxim that light is good: the idea that page performance matters to the end user experience is a truism at this point, backed up by a tremendous amount of real-world evidence, summarised quite nicely at &lt;a href=&quot;http://www.websiteoptimization.com/speed/tweak/psychology-web-performance/&quot; class=&quot;bb-url&quot;&gt;websiteoptimization.com&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/performance-money-part-1-end-users-wallet&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/performance-money-part-1-end-users-wallet#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/5901</wfw:commentRss>
 <pubDate>Tue, 12 Mar 2013 17:43:44 +0000</pubDate>
 <dc:creator>ronan</dc:creator>
 <guid isPermaLink="false">5901 at http://mobiforge.com</guid>
</item>
<item>
 <title>BB10 tutorial: create Web apps that seamlessly integrate BlackBerry 10 native functions</title>
 <link>http://mobiforge.com/developing/story/bb10-tutorial-create-web-apps-seamlessly-integrate-blackberry-10-native-functions</link>
 <description>&lt;p&gt;The much-anticipated BlackBerry 10 operating system is already creating a splash with customers, analysts and developers alike. In this tutorial, BlackBerry developer evangelist Luca Sale teaches us how to develop a Web app for the new OS that hooks into the native functions of BlackBerry devices such as the camera and the ever-popular BlackBerry Messenger (BBM).
&lt;h2&gt;From 0 to BlackBerry 10&lt;/h2&gt;&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/bb10-tutorial-create-web-apps-seamlessly-integrate-blackberry-10-native-functions&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/bb10-tutorial-create-web-apps-seamlessly-integrate-blackberry-10-native-functions#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/apps">Apps</category>
 <category domain="http://mobiforge.com/blackberry">Blackberry</category>
 <category domain="http://mobiforge.com/tutorial">Tutorial</category>
 <category domain="http://mobiforge.com/html5-0">HTML5</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/5895</wfw:commentRss>
 <pubDate>Tue, 12 Mar 2013 16:49:28 +0000</pubDate>
 <dc:creator>BlackBerryLuca</dc:creator>
 <guid isPermaLink="false">5895 at http://mobiforge.com</guid>
</item>
<item>
 <title>Developing custom pictograms for the mobile Web</title>
 <link>http://mobiforge.com/designing/story/developing-custom-pictograms-mobile-web</link>
 <description>&lt;h2&gt;A matter of trade-offs&lt;/h2&gt;

&lt;p&gt;
Pictograms &amp;#8211; miniature graphical representations of states, actions and 
objects &amp;#8211; made their way into the mobile Web over 15 years ago. 
Several normalized (UNICODE, WAP) and proprietary (Japanese emojis, Openwave) 
mechanisms are in place to enrich Web applications with pre-defined images.
&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/story/developing-custom-pictograms-mobile-web&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/story/developing-custom-pictograms-mobile-web#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/browsers">Browsers</category>
 <category domain="http://mobiforge.com/pictograms">Pictograms</category>
 <category domain="http://mobiforge.com/standards">Standards</category>
 <category domain="http://mobiforge.com/html">HTML</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/5872</wfw:commentRss>
 <pubDate>Wed, 06 Mar 2013 16:11:04 +0000</pubDate>
 <dc:creator>casaise</dc:creator>
 <guid isPermaLink="false">5872 at http://mobiforge.com</guid>
</item>
<item>
 <title>An introduction to Firefox OS for mobile developers: Q&amp;A with Andreas Gal, Mozilla</title>
 <link>http://mobiforge.com/developing/story/an-introduction-firefox-os-mobile-developers-q-a-with-andreas-gal-mozilla</link>
 <description>&lt;p&gt;With the first device manufacturers expected to launch Firefox OS devices at Mobile World Congress this month and with major network operators inline to release them to consumers in early 2013, Mozilla’s new operating system (OS) is starting to make waves. Firefox OS is open-source, Linux-based and Web-friendly. mobiForge gets the low-down from Mozilla’s vice president of mobile engineering, Andreas Gal. &lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Q1. What is Firefox OS?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/an-introduction-firefox-os-mobile-developers-q-a-with-andreas-gal-mozilla&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/an-introduction-firefox-os-mobile-developers-q-a-with-andreas-gal-mozilla#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/html5-0">HTML5</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/5733</wfw:commentRss>
 <pubDate>Tue, 19 Feb 2013 17:04:25 +0000</pubDate>
 <dc:creator>AndreasGal_Mozilla</dc:creator>
 <guid isPermaLink="false">5733 at http://mobiforge.com</guid>
</item>
<item>
 <title>HTML5 for mobile developers</title>
 <link>http://mobiforge.com/developing/story/html5-mobile-developers</link>
 <description>&lt;h2&gt;Why HTML5 and why now?&lt;/h2&gt;
&lt;p&gt;When it comes to touch-screen mobile devices, native applications have led the way in terms of performance, speed and tighter integration to specific platforms. Unbound by the need to conform to standards, native apps could rapidly take advantage of the latest hardware and operating system innovations, while Web technologies always had to wait for the international community to agree and implement standards first. But with the HTML5 specification coming to fruition, browser-based mobile apps are rapidly catching up with the natives.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/html5-mobile-developers&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/html5-mobile-developers#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/browsers">Browsers</category>
 <category domain="http://mobiforge.com/client-side">Client-side</category>
 <category domain="http://mobiforge.com/standards">Standards</category>
 <category domain="http://mobiforge.com/html5-0">HTML5</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/5277</wfw:commentRss>
 <pubDate>Thu, 10 Jan 2013 16:13:58 +0000</pubDate>
 <dc:creator>SantthoshSelvadurai</dc:creator>
 <guid isPermaLink="false">5277 at http://mobiforge.com</guid>
</item>
<item>
 <title>Consuming JSON services in Android apps</title>
 <link>http://mobiforge.com/developing/story/consuming-json-services-android-apps</link>
 <description>&lt;p&gt;Unless you are writing a Hello World Android application, chances are your application would need to connect to the outside world to fetch some data, such as live currency exchange rates, weather information, records from databases, etc. One of the easiest ways for your application to connect to the outside world is to use web services. &lt;/p&gt;
&lt;p&gt;For the past few years, XML web services have dominated the arena for web services, as XML was touted as the ubiquitous medium for data exchange. However, using XML as the medium for your data payload suffers from the following problems:&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/consuming-json-services-android-apps&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/consuming-json-services-android-apps#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/android">Android</category>
 <category domain="http://mobiforge.com/apps">Apps</category>
 <category domain="http://mobiforge.com/javascript-0">Javascript</category>
 <category domain="http://mobiforge.com/java">Java</category>
 <category domain="http://mobiforge.com/xml">XML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/5187</wfw:commentRss>
 <pubDate>Wed, 19 Dec 2012 17:39:05 +0000</pubDate>
 <dc:creator>weimenglee</dc:creator>
 <guid isPermaLink="false">5187 at http://mobiforge.com</guid>
</item>
<item>
 <title>Lightweight accordions &amp; sliders with jQuery Mobile</title>
 <link>http://mobiforge.com/developing/story/lightweight-accordions-sliders-with-jquery-mobile</link>
 <description>&lt;p&gt;Mobile developers are commonly confronted with clients who want everything – all the content and features – on their PC site crammed into the mobile site, rather than going for a streamlined mobile site. That might sound like a recipe for bloated code and a poor user experience – neither of which is acceptable on a mobile device – but it needn’t be, as long as mobile developers emphasize ingenuity over excess functionality. That’s where jQuery accordion menus and sliders come in very useful and, if used cleverly, they can help keep the mobile experience lean and mean.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/lightweight-accordions-sliders-with-jquery-mobile&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/lightweight-accordions-sliders-with-jquery-mobile#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/design-patterns">Design Patterns</category>
 <category domain="http://mobiforge.com/frameworks">Frameworks</category>
 <category domain="http://mobiforge.com/javascript-0">Javascript</category>
 <enclosure url="http://mobiforge.com/sites/mobiforge.com/files/accordion.zip" length="2433" type="application/octet-stream" />
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/5213</wfw:commentRss>
 <pubDate>Thu, 06 Dec 2012 16:23:26 +0000</pubDate>
 <dc:creator>mdagruma</dc:creator>
 <guid isPermaLink="false">5213 at http://mobiforge.com</guid>
</item>
<item>
 <title>A Guide to Using Pictograms in Mobile Applications</title>
 <link>http://mobiforge.com/designing/story/a-guide-using-pictograms-mobile-applications</link>
 <description>&lt;h2 style=&quot;margin-top:0;padding-top:0&quot;&gt;A long-standing feature&lt;/h2&gt;
&lt;p&gt;Developers inspecting the user agent profile of a modern handset like the 
Motorola XT682 ATRIX TV may be surprised to discover the following &lt;span class=&quot;geshifilter&quot;&gt;&lt;code class=&quot;geshifilter-text&quot;&gt;ImageCapable&lt;/code&gt;&lt;/span&gt; declaration which indicates whether a device can display images or not: &lt;br class=&quot;clear&quot;/&gt;&lt;div class=&quot;geshifilter&quot;&gt;&lt;pre class=&quot;geshifilter-xml&quot;&gt;&lt;span style=&quot;color: #009900;&quot;&gt;&lt;span style=&quot;font-weight: bold; color: black;&quot;&gt;&amp;lt;prf:ImageCapable&lt;span style=&quot;font-weight: bold; color: black;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;Yes&lt;span style=&quot;color: #009900;&quot;&gt;&lt;span style=&quot;font-weight: bold; color: black;&quot;&gt;&amp;lt;/prf:ImageCapable&lt;span style=&quot;font-weight: bold; color: black;&quot;&gt;&amp;gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/story/a-guide-using-pictograms-mobile-applications&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/story/a-guide-using-pictograms-mobile-applications#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/browsers">Browsers</category>
 <category domain="http://mobiforge.com/usability">Usability</category>
 <category domain="http://mobiforge.com/pictograms">Pictograms</category>
 <category domain="http://mobiforge.com/standards">Standards</category>
 <category domain="http://mobiforge.com/html">HTML</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/4963</wfw:commentRss>
 <pubDate>Tue, 06 Nov 2012 16:37:15 +0000</pubDate>
 <dc:creator>casaise</dc:creator>
 <guid isPermaLink="false">4963 at http://mobiforge.com</guid>
</item>
<item>
 <title>Introducing Prism, a tool for testing device adaptation</title>
 <link>http://mobiforge.com/designing/blog/introducing-prism-a-tool-testing-device-adaptation</link>
 <description>&lt;p&gt;Due to the multifarious nature of the mobile web, developers tend to spend a lot of time testing their work. If your site is designed to adapt to multiple different devices this effort is multiplied because you need to ensure that your detection is working correctly across multiple devices and that your response is appropriate in each case.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/introducing-prism-a-tool-testing-device-adaptation&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/introducing-prism-a-tool-testing-device-adaptation#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/Testing">Testing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/testers">Testers</category>
 <category domain="http://mobiforge.com/analysts">Analysts</category>
 <category domain="http://mobiforge.com/insights">Insights</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <category domain="http://mobiforge.com/publishing">Publishing</category>
 <category domain="http://mobiforge.com/server-side">Server-side</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/4989</wfw:commentRss>
 <pubDate>Thu, 01 Nov 2012 16:20:43 +0000</pubDate>
 <dc:creator>ronan</dc:creator>
 <guid isPermaLink="false">4989 at http://mobiforge.com</guid>
</item>
<item>
 <title>Using HTML5 application cache in mobile Web apps</title>
 <link>http://mobiforge.com/developing/story/using-html5-application-cache-mobile-web-apps</link>
 <description>&lt;p&gt;One of the most interesting features of HTML5 is support for &lt;a href=&quot;http://www.html5rocks.com/en/tutorials/appcache/beginner&quot; target=&quot;_blank&quot;&gt;application cache&lt;/a&gt;. Every Web browser has a built-in &lt;a href=&quot;http://www.refreshyourcache.com/en/cache&quot; target=&quot;_blank&quot;&gt;cache&lt;/a&gt; that stores recently visited Web pages. This means the same pages and assets will load faster the next time the browser returns. At every subsequent call, the browser checks the timestamp to determine whether to reload the assets from the server or serve the cached versions.&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/using-html5-application-cache-mobile-web-apps&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/using-html5-application-cache-mobile-web-apps#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/html5-0">HTML5</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/4797</wfw:commentRss>
 <pubDate>Thu, 11 Oct 2012 14:46:58 +0000</pubDate>
 <dc:creator>AndreaMoretti</dc:creator>
 <guid isPermaLink="false">4797 at http://mobiforge.com</guid>
</item>
<item>
 <title>Sense and sensor-bility: access mobile device sensors with JavaScript</title>
 <link>http://mobiforge.com/developing/story/sense-and-sensor-bility-access-mobile-device-sensors-with-javascript</link>
 <description>&lt;p&gt;Just as we humans call upon our senses to provide us with data about our environment, so smartphones and tablet devices use their own digital senses – touchscreen, geolocation, orientation, direction and motion – to provide interaction and to tailor applications and games to the user and their real-world surroundings.&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/sense-and-sensor-bility-access-mobile-device-sensors-with-javascript&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/sense-and-sensor-bility-access-mobile-device-sensors-with-javascript#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/javascript-0">Javascript</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/4733</wfw:commentRss>
 <pubDate>Wed, 26 Sep 2012 13:43:22 +0000</pubDate>
 <dc:creator>DenOdell</dc:creator>
 <guid isPermaLink="false">4733 at http://mobiforge.com</guid>
</item>
<item>
 <title>Why mobile Web accessibility matters - best practices to make your mobile site accessible</title>
 <link>http://mobiforge.com/developing/story/why-mobile-web-accessibility-matters-best-practices-make-your-mobile-site-accessibl</link>
 <description>&lt;p&gt;&lt;strong&gt;“The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.”&lt;/strong&gt; &lt;a href=&quot;http://www.w3.org/standards/Webdesign/accessibility&quot; target=&quot;_blank&quot;&gt;Tim Berners-Lee&lt;/a&gt;, W3C Director and inventor of the World Wide Web.&lt;/p&gt;  
&lt;p&gt;This mantra is as true for the mobile Web as it is for the desktop Web. Over a billion people worldwide live with some kind of disability, and 285 million have visual impairments (39 million are blind and 246 have low vision), according to &lt;a href=&quot;http://www.who.int/mediacentre/factsheets/fs282/en/index.html&quot; target=&quot;_blank&quot;&gt;World Health Organization (WHO)&lt;/a&gt;. Given these numbers, what excuses are there for bad design practices that shut users out who are visually impaired and/or rely on assistive technologies?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/why-mobile-web-accessibility-matters-best-practices-make-your-mobile-site-accessibl&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/why-mobile-web-accessibility-matters-best-practices-make-your-mobile-site-accessibl#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/accessibility">Accessibility</category>
 <category domain="http://mobiforge.com/html5-0">HTML5</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/4648</wfw:commentRss>
 <pubDate>Thu, 13 Sep 2012 15:16:27 +0000</pubDate>
 <dc:creator>soederquist</dc:creator>
 <guid isPermaLink="false">4648 at http://mobiforge.com</guid>
</item>
<item>
 <title>What does JavaScript bring to the mobile HTML5 and CSS3 party?</title>
 <link>http://mobiforge.com/developing/story/what-does-javascript-bring-mobile-html5-and-css3-party</link>
 <description>&lt;p&gt;JavaScript brings the mobile Web to life. It brings interactivity to HTML5 and CSS3 mobile Web apps.&lt;br /&gt;
This Q&amp;A with Oren Farhi, front-end architect and JavaScript expert, explores what JavaScript does for mobile sites/apps and when, where, how and why it should be used … and when it shouldn’t.&lt;br /&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/what-does-javascript-bring-mobile-html5-and-css3-party&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/what-does-javascript-bring-mobile-html5-and-css3-party#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/html5-0">HTML5</category>
 <category domain="http://mobiforge.com/javascript-0">Javascript</category>
 <category domain="http://mobiforge.com/css">CSS</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/4606</wfw:commentRss>
 <pubDate>Fri, 07 Sep 2012 11:02:49 +0000</pubDate>
 <dc:creator>OrenFarhi</dc:creator>
 <guid isPermaLink="false">4606 at http://mobiforge.com</guid>
</item>
<item>
 <title>Anatomy of a mobile web experience: facebook.com</title>
 <link>http://mobiforge.com/designing/blog/anatomy-a-mobile-web-experience-facebook-com</link>
 <description>&lt;p&gt;
This is the second article in a series about how the major internet
brands deliver their mobile web experience. The previous article is
available here: &lt;a
href=&quot;http://mobiforge.com/designing/story/anatomy-a-mobile-web-experience-google-com&quot;&gt;Anatomy
of a mobile web experience: google.com&lt;/a&gt;
&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/anatomy-a-mobile-web-experience-facebook-com&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/anatomy-a-mobile-web-experience-facebook-com#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/design-patterns">Design Patterns</category>
 <category domain="http://mobiforge.com/mobile-design">Mobile Design</category>
 <category domain="http://mobiforge.com/authoring">Authoring</category>
 <category domain="http://mobiforge.com/client-side">Client-side</category>
 <category domain="http://mobiforge.com/server-side">Server-side</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/4136</wfw:commentRss>
 <pubDate>Wed, 11 Apr 2012 17:08:25 +0000</pubDate>
 <dc:creator>ronan</dc:creator>
 <guid isPermaLink="false">4136 at http://mobiforge.com</guid>
</item>
<item>
 <title>Anatomy of a mobile web experience: google.com</title>
 <link>http://mobiforge.com/designing/story/anatomy-a-mobile-web-experience-google-com</link>
 <description>&lt;p&gt;In a recent blog post that I did here on mobiForge (&lt;a
href=&quot;http://mobiforge.com/designing/blog/server-side-device-detection-used-82-alexa-top-100-sites&quot;&gt;Server-side
device detection used by 82% of Alexa top 100 sites&lt;/a&gt;) some people
expressed surprise that a 47 byte difference in the HTML payload
delivered by Google to different devices constituted a significant
level of
server-side adaptation. On checking my results, it turned out that this
minor 47
byte file size difference actually masks an entirely different HTML
document served to
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/story/anatomy-a-mobile-web-experience-google-com&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/story/anatomy-a-mobile-web-experience-google-com#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/design-patterns">Design Patterns</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/4126</wfw:commentRss>
 <pubDate>Wed, 28 Mar 2012 15:44:40 +0000</pubDate>
 <dc:creator>ronan</dc:creator>
 <guid isPermaLink="false">4126 at http://mobiforge.com</guid>
</item>
<item>
 <title>Future of the Mobile Web Whitepaper</title>
 <link>http://mobiforge.com/designing/blog/future-mobile-web-whitepaper</link>
 <description>&lt;p&gt;
	We&amp;#39;re very happy to publish this paper arising from the &lt;a href=&quot;http://deviceatlas.com/futureofthemobileweb&quot;&gt;&lt;strong&gt;The Future of the Mobile Web&lt;/strong&gt;&lt;/a&gt; event held at the Dublin Convention Centre in January 2012. We covered a lot of ground and the paper is a serious attempt to capture all the topics covered from HTML5 to responsive design to device detection and many others. We found it to be a very worthwhile process to listen, validate our ideas and learn from others in the process of writing it. We hope it is useful to a wider readership also.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/future-mobile-web-whitepaper&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/future-mobile-web-whitepaper#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/analysts">Analysts</category>
 <category domain="http://mobiforge.com/mobile-design">Mobile Design</category>
 <category domain="http://mobiforge.com/usability">Usability</category>
 <category domain="http://mobiforge.com/apps">Apps</category>
 <category domain="http://mobiforge.com/community">Community</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <category domain="http://mobiforge.com/gomobi">goMobi</category>
 <category domain="http://mobiforge.com/mobithinking">mobiThinking</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <category domain="http://mobiforge.com/dotmobi">dotMobi</category>
 <category domain="http://mobiforge.com/mobiforge">mobiForge</category>
 <category domain="http://mobiforge.com/publishing">Publishing</category>
 <category domain="http://mobiforge.com/tools">Tools</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/4024</wfw:commentRss>
 <pubDate>Thu, 23 Feb 2012 09:46:11 +0000</pubDate>
 <dc:creator>mclancy</dc:creator>
 <guid isPermaLink="false">4024 at http://mobiforge.com</guid>
</item>
<item>
 <title>Future of the Mobile Web</title>
 <link>http://mobiforge.com/designing/blog/future-mobile-web</link>
 <description>&lt;p&gt;
	Last week we hosted an event loftily entitled &amp;quot;The Future of the Mobile Web&amp;quot; at the Dublin Convention Centre.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/future-mobile-web&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/future-mobile-web#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/mobile-design">Mobile Design</category>
 <category domain="http://mobiforge.com/usability">Usability</category>
 <category domain="http://mobiforge.com/apps">Apps</category>
 <category domain="http://mobiforge.com/community">Community</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <category domain="http://mobiforge.com/standards">Standards</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3989</wfw:commentRss>
 <pubDate>Fri, 03 Feb 2012 12:13:12 +0000</pubDate>
 <dc:creator>mclancy</dc:creator>
 <guid isPermaLink="false">3989 at http://mobiforge.com</guid>
</item>
<item>
 <title>Server-side device detection used by 82% of Alexa top 100 sites</title>
 <link>http://mobiforge.com/designing/blog/server-side-device-detection-used-82-alexa-top-100-sites</link>
 <description>&lt;p&gt;About 82% of the Alexa 100 top sites use some form of server-side device detection to serve content on their main website entry point. As you descend from the top 10 to the top 25 and top 100 sites the percentage of sites using server-side detection falls from 100% to 96% to 82%. This is an interesting fact given the all of the recent discussion in the blogosphere of responsive design using client-side techniques such as media queries.&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/server-side-device-detection-used-82-alexa-top-100-sites&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/server-side-device-detection-used-82-alexa-top-100-sites#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/analysts">Analysts</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <enclosure url="http://mobiforge.com/sites/mobiforge.com/files/ServerSideDeviceDetection.xlsx.zip" length="47209" type="application/x-zip" />
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3912</wfw:commentRss>
 <pubDate>Wed, 11 Jan 2012 14:53:12 +0000</pubDate>
 <dc:creator>ronan</dc:creator>
 <guid isPermaLink="false">3912 at http://mobiforge.com</guid>
</item>
<item>
 <title>Future of the Mobile Web: Request for submissions</title>
 <link>http://mobiforge.com/mobile-design/blog/future-mobile-web-request-submissions</link>
 <description>&lt;p&gt;Dear mobiForge community,&lt;/p&gt;
&lt;p&gt;We have invited a number of colleagues and opinion formers from across several different verticals to &lt;span style=&quot;font-weight:bold&quot;&gt;a forum event in Dublin on January 26th next &lt;/span&gt;to discuss some of the most pressing &lt;span style=&quot;font-weight:bold&quot;&gt;issues, trends, opportunities and challenges in today’s mobile web environment&lt;/span&gt;. People from companies like Adobe, Cloud Four, Nokia, Yiibu and others will be coming along.&lt;/p&gt;
&lt;p&gt;The idea is to build towards &lt;span style=&quot;font-weight:bold&quot;&gt;a consensus on current technology, facts, fictions and opportunities of the mobile web&lt;/span&gt; in an environment that is increasingly noisy and hype filled.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/mobile-design/blog/future-mobile-web-request-submissions&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/mobile-design/blog/future-mobile-web-request-submissions#comments</comments>
 <category domain="http://mobiforge.com/mobile-design">Mobile Design</category>
 <category domain="http://mobiforge.com/usability">Usability</category>
 <category domain="http://mobiforge.com/community">Community</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <category domain="http://mobiforge.com/device-database">Device Database</category>
 <category domain="http://mobiforge.com/gomobi">goMobi</category>
 <category domain="http://mobiforge.com/tada">TADA</category>
 <category domain="http://mobiforge.com/mobithinking">mobiThinking</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <category domain="http://mobiforge.com/dotmobi">dotMobi</category>
 <category domain="http://mobiforge.com/mobiforge">mobiForge</category>
 <category domain="http://mobiforge.com/public">Public</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3878</wfw:commentRss>
 <pubDate>Fri, 06 Jan 2012 14:35:53 +0000</pubDate>
 <dc:creator>mclancy</dc:creator>
 <guid isPermaLink="false">3878 at http://mobiforge.com</guid>
</item>
<item>
 <title>Mobile web content adaptation techniques</title>
 <link>http://mobiforge.com/starting/story/mobile-web-content-adaptation-techniques</link>
 <description>    &lt;h2&gt;Introduction&lt;/h2&gt;
    &lt;p&gt;This article will help you pick from amongst the many techniques for building a mobile website. It doesn&#039;t describe how to do it, rather it instead tries to help you to pick the right approach. Before we begin it&#039;s worth clarifying exactly what the goal of the exercise is. Generally speaking, people who are looking to build a mobile site fall into two categories. They&#039;re either:&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/starting/story/mobile-web-content-adaptation-techniques&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/starting/story/mobile-web-content-adaptation-techniques#comments</comments>
 <category domain="http://mobiforge.com/Starting">Starting</category>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3628</wfw:commentRss>
 <pubDate>Tue, 01 Nov 2011 17:20:17 +0000</pubDate>
 <dc:creator>ronan</dc:creator>
 <guid isPermaLink="false">3628 at http://mobiforge.com</guid>
</item>
<item>
 <title>Displaying Status Bar Notifications in Android</title>
 <link>http://mobiforge.com/developing/story/displaying-status-bar-notifications-android</link>
 <description>&lt;p&gt;Developers of Android are no doubt familiar with the Toast class, which displays a little pop-up containing whatever message you want to display to the user. However, the Toast pop-up will automatically dismiss itself after a while, making it useful as a tool to provide timely feedback to the user (such as informing the user that a file has been saved successfully), but not a really good tool to use for some asynchronous action (such as telling the user that an incoming SMS message has arrived).&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/displaying-status-bar-notifications-android&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/displaying-status-bar-notifications-android#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/android">Android</category>
 <category domain="http://mobiforge.com/java">Java</category>
 <category domain="http://mobiforge.com/xml">XML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3547</wfw:commentRss>
 <pubDate>Tue, 20 Sep 2011 13:59:05 +0000</pubDate>
 <dc:creator>weimenglee</dc:creator>
 <guid isPermaLink="false">3547 at http://mobiforge.com</guid>
</item>
<item>
 <title>The best of breakingdevelopment conference</title>
 <link>http://mobiforge.com/developing/blog/the-best-breakingdevelopment-conference</link>
 <description>&lt;p&gt;As many of you know, the &lt;a href=&quot;http://www.bdconf.com/&quot;&gt;breakingdevelopment&lt;/a&gt; conference took place in Nashville, Tennessee over the last few days. It appears to have been a really seminal conference with 13 leading mobile web developers speaking.&lt;/p&gt;
&lt;p&gt;Others have already put together summaries of the conference but I thought I&#039;d link to what I thought were the most interest presentations.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/the-best-breakingdevelopment-conference&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/the-best-breakingdevelopment-conference#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <category domain="http://mobiforge.com/device-database">Device Database</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3538</wfw:commentRss>
 <pubDate>Thu, 15 Sep 2011 09:45:40 +0000</pubDate>
 <dc:creator>ronan</dc:creator>
 <guid isPermaLink="false">3538 at http://mobiforge.com</guid>
</item>
<item>
 <title>Importing &amp; Exporting Documents in iOS</title>
 <link>http://mobiforge.com/developing/story/importing-exporting-documents-ios</link>
 <description>&lt;p&gt;One of the common tasks that an iOS developer has to do is to import or export documents from his iOS application. For example, suppose you are developing a document reader and  you  want to allow the user to import documents into your application so that it can be read offline. Also, your reader might also support the exporting of documents so that other applications can make use of the document. &lt;/p&gt;
&lt;p&gt;In this article, I will walk you through the different techniques you can employ to allow documents to be imported or exported from your iOS application. &lt;/p&gt;
&lt;h2&gt;Creating the Project&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/importing-exporting-documents-ios&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/importing-exporting-documents-ios#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/iphone">iPhone</category>
 <category domain="http://mobiforge.com/objective-c">Objective C</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3491</wfw:commentRss>
 <pubDate>Tue, 09 Aug 2011 12:13:57 +0000</pubDate>
 <dc:creator>weimenglee</dc:creator>
 <guid isPermaLink="false">3491 at http://mobiforge.com</guid>
</item>
<item>
 <title>Preserving User Preferences in Android Applications</title>
 <link>http://mobiforge.com/developing/story/preserving-user-preferences-android-applications</link>
 <description>&lt;p&gt;Often you need to store personalized information for each user of your application. For example, your application may require users to logon to a secure server for authentication. In this case, the user needs to supply his credentials, such as a login name and a password. The first time the user uses your application this information will be entered by the user, but subsequently it would be useful for your application to “remember” this information somewhere so that it can save the user the trouble of entering the same information every time he uses your application.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/preserving-user-preferences-android-applications&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/preserving-user-preferences-android-applications#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/android">Android</category>
 <category domain="http://mobiforge.com/java">Java</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3467</wfw:commentRss>
 <pubDate>Mon, 25 Jul 2011 16:32:04 +0000</pubDate>
 <dc:creator>weimenglee</dc:creator>
 <guid isPermaLink="false">3467 at http://mobiforge.com</guid>
</item>
<item>
 <title>Device Diversity</title>
 <link>http://mobiforge.com/developing/story/device-diversity</link>
 <description>&lt;p&gt;As dotMobi brings &lt;a href=&quot;http://www.DeviceAtlas.com&quot;&gt;DeviceAtlas&lt;/a&gt; to the cloud Ronan Cremin, Director of Engineering at dotMobi, charts the increasing complexity of the device landscape for developers in the first of two pieces looking at device fragmentation.&lt;/p&gt;
&lt;p&gt;In the beginning the web was a much simpler place. By the time the web was becoming a mainstream media in the late 1990’s there was only one device through which you accessed it: the humble desktop PC, running one of just a handful of browsers.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/device-diversity&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/device-diversity#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/analysts">Analysts</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3465</wfw:commentRss>
 <pubDate>Thu, 07 Jul 2011 11:08:36 +0000</pubDate>
 <dc:creator>ronan</dc:creator>
 <guid isPermaLink="false">3465 at http://mobiforge.com</guid>
</item>
<item>
 <title>Responding To Inbound SMS Messages</title>
 <link>http://mobiforge.com/developing/story/responding-to-inbound-sms-messages</link>
 <description>&lt;p&gt;In our &lt;a href=&quot;http://mobiforge.com/developing/story/receiving-sms-messages-shortcodes-keywords&quot;&gt;last article&lt;/a&gt;, we created the basis of a messaging system, allowing us to receive inbound messages using keywords and shortcodes. We’ve also previously seen &lt;a href=&quot;http://mobiforge.com/developing/story/sending-sms-apps-and-webapps&quot;&gt;how we can send SMS messages&lt;/a&gt;. It’s time to bring everything together and create a simple messaging system that can process inbound SMS messages and send back responses to those messages.&lt;/p&gt;
&lt;h2&gt;The Current System&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/responding-to-inbound-sms-messages&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/responding-to-inbound-sms-messages#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/asp-net">ASP.NET</category>
 <category domain="http://mobiforge.com/c">C#</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3329</wfw:commentRss>
 <pubDate>Fri, 25 Feb 2011 09:50:52 +0000</pubDate>
 <dc:creator>mokil</dc:creator>
 <guid isPermaLink="false">3329 at http://mobiforge.com</guid>
</item>
<item>
 <title>Web Access in Windows Phone 7 Apps</title>
 <link>http://mobiforge.com/developing/story/web-access-windows-phone-7-apps</link>
 <description>&lt;p&gt;In previous articles, I have shown how easy it is to get started in Windows Phone 7 programming using Visual Studio 2010 and the Windows Phone Developer Tools. In this third installment of the series, I will continue the exploration of Windows Phone development. This time I will focus on one key development topic: Web access. Unless you are writing a Hello World application, chances are that your application will need to connect to the outside world.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/web-access-windows-phone-7-apps&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/web-access-windows-phone-7-apps#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/windows-phone-7">Windows Phone 7</category>
 <category domain="http://mobiforge.com/c">C#</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3266</wfw:commentRss>
 <pubDate>Fri, 07 Jan 2011 18:02:25 +0000</pubDate>
 <dc:creator>weimenglee</dc:creator>
 <guid isPermaLink="false">3266 at http://mobiforge.com</guid>
</item>
<item>
 <title>Building Location Service Apps in Windows Phone 7</title>
 <link>http://mobiforge.com/designing/story/building-location-service-apps-windows-phone-7</link>
 <description>&lt;p&gt;In my previous article on Windows Phone 7 development, I showed how you can quickly get started using Visual Studio 2010 together with the Windows Phone Developer Tools. In this second article in the series, I will discuss a topic that is garnering a lot of interest in recent years -location services. Location services usually involve two key components - getting your location data and displaying your location on a map. Hence in this article, I will first show you how to display a map in your Windows Phone 7 application and then use the Location Service APIs to obtain your current position.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/story/building-location-service-apps-windows-phone-7&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/story/building-location-service-apps-windows-phone-7#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/windows-phone-7">Windows Phone 7</category>
 <category domain="http://mobiforge.com/location-based-services">Location Based Services</category>
 <category domain="http://mobiforge.com/c">C#</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3241</wfw:commentRss>
 <pubDate>Wed, 15 Dec 2010 09:39:33 +0000</pubDate>
 <dc:creator>weimenglee</dc:creator>
 <guid isPermaLink="false">3241 at http://mobiforge.com</guid>
</item>
<item>
 <title>Receiving SMS Messages via Shortcodes &amp; Keywords</title>
 <link>http://mobiforge.com/developing/story/receiving-sms-messages-shortcodes-keywords</link>
 <description>&lt;p&gt;Back around 1998, more and more billboards started to display some odd messages, along the lines of &quot;Visit us on the web at &lt;a href=&quot;http://www.companyname.com&quot;&gt;www.companyname.com&lt;/a&gt;&quot;. This was a major shift in advertising and gave marketers another avenue to explore. It was, of course, the beginning of the Internet&#039;s move from academia to the mainstream, and the proliferation of Web sites seemed to happen almost overnight.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/receiving-sms-messages-shortcodes-keywords&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/receiving-sms-messages-shortcodes-keywords#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/messaging">Messaging</category>
 <category domain="http://mobiforge.com/c">C#</category>
 <category domain="http://mobiforge.com/sms">SMS</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3040</wfw:commentRss>
 <pubDate>Mon, 01 Nov 2010 14:31:14 +0000</pubDate>
 <dc:creator>mokil</dc:creator>
 <guid isPermaLink="false">3040 at http://mobiforge.com</guid>
</item>
<item>
 <title>Introduction to Windows Phone 7 Development</title>
 <link>http://mobiforge.com/developing/story/introduction-windows-phone-7-development</link>
 <description>&lt;p&gt;By now, you should already have heard of Microsoft&#039;s new Windows Phone 7 mobile OS. And while many developers are busy developing for Android and iPhone, Microsoft is hard at work, developing its killer mobile OS that could give the competitors a run for the money. Before you dismiss Microsoft as a serious contender in the mobile space, think again. The new OS is now a total rewrite of the older Windows Mobile platform, and sports many features that you have come to expect of a modern mobile operating system.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/introduction-windows-phone-7-development&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/introduction-windows-phone-7-development#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/android">Android</category>
 <category domain="http://mobiforge.com/iphone">iPhone</category>
 <category domain="http://mobiforge.com/windows-phone-7">Windows Phone 7</category>
 <category domain="http://mobiforge.com/c">C#</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3021</wfw:commentRss>
 <pubDate>Mon, 18 Oct 2010 08:49:50 +0000</pubDate>
 <dc:creator>weimenglee</dc:creator>
 <guid isPermaLink="false">3021 at http://mobiforge.com</guid>
</item>
<item>
 <title>DeviceAtlas &amp; jQueryMobile</title>
 <link>http://mobiforge.com/developing/blog/deviceatlas-jquerymobile</link>
 <description>&lt;p&gt;The first Alpha release of &lt;a href=&quot;http://jquerymobile.com&quot;&gt;jQueryMobile&lt;/a&gt; was &lt;a href=&quot;http://jquerymobile.com/2010/10/jquery-mobile-alpha-1-released/&quot;&gt;announced&lt;/a&gt; today, to great fanfare, and the mobile web world is already on fire with the thoughts of what this will mean to them.&lt;/p&gt;
&lt;h3&gt;A little bit of background...&lt;/h3&gt;
&lt;p&gt;Originally developed by &lt;a href=&quot;http://en.wikipedia.org/wiki/John_Resig&quot;&gt;John Resig&lt;/a&gt;, jQueryMobile&#039;s big brother &quot;&lt;a href=&quot;http://jquery.com/&quot;&gt;jQuery&lt;/a&gt;&quot; is now in use by pretty much anyone who implements advanced JavaScript capabilities on their site.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/deviceatlas-jquerymobile&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/deviceatlas-jquerymobile#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <category domain="http://mobiforge.com/device-database">Device Database</category>
 <category domain="http://mobiforge.com/deviceatlas">DeviceAtlas</category>
 <enclosure url="http://mobiforge.com/sites/mobiforge.com/files/jqm_alpha.png" length="68671" type="image/png" />
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/3020</wfw:commentRss>
 <pubDate>Sat, 16 Oct 2010 06:00:00 +0000</pubDate>
 <dc:creator>daniel.hunt</dc:creator>
 <guid isPermaLink="false">3020 at http://mobiforge.com</guid>
</item>
</channel>
</rss>
