<?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>Designing</title>
 <link>http://mobiforge.com/designing</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<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>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>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>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>Future of the Mobile Web Whitepaper</title>
 <link>http://mobiforge.com/starting/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/starting/blog/future-mobile-web-whitepaper&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/starting/blog/future-mobile-web-whitepaper#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/Testing">Testing</category>
 <category domain="http://mobiforge.com/Running">Running</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/developers-guide">Developers Guide</category>
 <category domain="http://mobiforge.com/site-building-tutorial">Site Building Tutorial</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/authoring">Authoring</category>
 <category domain="http://mobiforge.com/android">Android</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/device-database">Device Database</category>
 <category domain="http://mobiforge.com/gomobi">goMobi</category>
 <category domain="http://mobiforge.com/ipad-0">iPad</category>
 <category domain="http://mobiforge.com/iphone">iPhone</category>
 <category domain="http://mobiforge.com/content-management">Content Management</category>
 <category domain="http://mobiforge.com/frameworks">Frameworks</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/standards">Standards</category>
 <category domain="http://mobiforge.com/publishing">Publishing</category>
 <category domain="http://mobiforge.com/server-side">Server-side</category>
 <category domain="http://mobiforge.com/content-transformation">Content Transformation</category>
 <category domain="http://mobiforge.com/tools">Tools</category>
 <category domain="http://mobiforge.com/analytics">Analytics</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/client-side">Client-side</category>
 <category domain="http://mobiforge.com/android">Android</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/device-database">Device Database</category>
 <category domain="http://mobiforge.com/ipad-0">iPad</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/content-management">Content Management</category>
 <category domain="http://mobiforge.com/frameworks">Frameworks</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>The goMobi Challenge is on!</title>
 <link>http://mobiforge.com/designing/blog/the-gomobi-challenge</link>
 <description>&lt;p&gt;UPDATE:*** Given that it’s been a very hot summer this year, we decided everyone needed a few days to regroup for the &lt;a href=&quot;http://cp.gomobi.info/gomobi_challenge&quot;&gt;goMobi Challenge&lt;/a&gt;. Since we want to see just how personalized you can make a goMobi site, we’re giving you a little extra time to show us your stuff. We’ve extended the contest through October 17, 2010.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/the-gomobi-challenge&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/the-gomobi-challenge#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/business">Business</category>
 <category domain="http://mobiforge.com/gomobi">goMobi</category>
 <category domain="http://mobiforge.com/frameworks">Frameworks</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/2874</wfw:commentRss>
 <pubDate>Mon, 20 Sep 2010 09:27:48 +0000</pubDate>
 <dc:creator>VanceMan</dc:creator>
 <guid isPermaLink="false">2874 at http://mobiforge.com</guid>
</item>
<item>
 <title>Using the PopoverView in iPad App Development</title>
 <link>http://mobiforge.com/designing/story/using-popoverview-ipad-app-development</link>
 <description>&lt;p&gt;In the previous article, we saw how to develop a new type of application known as the Split View-based application on the iPad. And one of the new views introduced for the iPad is the PopoverView, which you had a quick glimpse of it in action in the previous article. In this article, I will show you how you can use the PopoverView in your iPad application, not just in a Split View-based application. &lt;/p&gt;
&lt;h2&gt;Getting Started with the PopoverView&lt;/h2&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/story/using-popoverview-ipad-app-development&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/story/using-popoverview-ipad-app-development#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <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/ipad-0">iPad</category>
 <category domain="http://mobiforge.com/objective-c">Objective C</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/2729</wfw:commentRss>
 <pubDate>Thu, 13 May 2010 08:51:12 +0000</pubDate>
 <dc:creator>weimenglee</dc:creator>
 <guid isPermaLink="false">2729 at http://mobiforge.com</guid>
</item>
<item>
 <title>Nexus One: Where is Android at?</title>
 <link>http://mobiforge.com/designing/blog/nexus-one-where-android</link>
 <description>&lt;p&gt;With the announcement of the new &lt;em&gt;GooglePhone&lt;/em&gt;, which promises to be the best Android device yet and by all early reports at least comparable with the iPhone 3GS, it seems appropriate to stop to take a look around to see where Android is at.&lt;/p&gt;
&lt;p&gt;We start with the breakdown of Android Platform distribution, based on access to the Android Market.&lt;/p&gt;
&lt;p class=&quot;image-caption&quot;&gt;&lt;img src=&quot;/files/platform_versions-600.jpg&quot; alt=&quot;Android versions&quot; /&gt;&lt;br /&gt;Android versions (Source: &lt;a href=&quot;http://developer.android.com&quot;&gt;http://developer.android.com&lt;/a&gt;)&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/nexus-one-where-android&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/nexus-one-where-android#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/android">Android</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/2487</wfw:commentRss>
 <pubDate>Tue, 05 Jan 2010 17:02:30 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">2487 at http://mobiforge.com</guid>
</item>
</channel>
</rss>

