<?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>Usability</title>
 <link>http://mobiforge.com/usability</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<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>Future of the Mobile Web: Request for submissions</title>
 <link>http://mobiforge.com/browsers/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/browsers/blog/future-mobile-web-request-submissions&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/browsers/blog/future-mobile-web-request-submissions#comments</comments>
 <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/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>DIY Touchscreen Analysis</title>
 <link>http://mobiforge.com/antenna/diy-touchscreen-analysis</link>
 <description>&lt;p&gt;The success of the iPhone has triggered the adoption of touchscreen systems in a wide range of mobile devices, and a bevy of new gadgets equipped with capacitive sensing technology have now hit the market.  MOTO has years of experience developing products that use capacitive touch, and we’ve tested many of the latest devices. Our conclusion: All touchscreens are not created equal.&lt;/p&gt;
</description>
 <comments>http://mobiforge.com/antenna/diy-touchscreen-analysis#comments</comments>
 <category domain="http://mobiforge.com/usability">Usability</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/2510</wfw:commentRss>
 <pubDate>Fri, 15 Jan 2010 19:34:44 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">2510 at http://mobiforge.com</guid>
</item>
<item>
 <title>The dotMobi WordPress Mobile Pack</title>
 <link>http://mobiforge.com/running/story/the-dotmobi-wordpress-mobile-pack</link>
 <description>      &lt;p&gt;The dotMobi WordPress Mobile Pack is a complete toolkit from dotMobi to help mobilize your WordPress site and blog.&lt;/p&gt;
      &lt;p&gt;It includes a mobile switcher to select themes based on the type of user that is visiting the site, a selection of mobile themes, extra widgets, device adaptation and a mobile administration panel to allow users to edit the site or write new posts when out and about.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/running/story/the-dotmobi-wordpress-mobile-pack&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/running/story/the-dotmobi-wordpress-mobile-pack#comments</comments>
 <category domain="http://mobiforge.com/Running">Running</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/business">Business</category>
 <category domain="http://mobiforge.com/usability">Usability</category>
 <category domain="http://mobiforge.com/content-management">Content Management</category>
 <category domain="http://mobiforge.com/publishing">Publishing</category>
 <category domain="http://mobiforge.com/server-side">Server-side</category>
 <category domain="http://mobiforge.com/tools">Tools</category>
 <category domain="http://mobiforge.com/cms">CMS</category>
 <category domain="http://mobiforge.com/php">PHP</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/2011</wfw:commentRss>
 <pubDate>Thu, 30 Apr 2009 14:41:01 +0000</pubDate>
 <dc:creator>James Pearce</dc:creator>
 <guid isPermaLink="false">2011 at http://mobiforge.com</guid>
</item>
<item>
 <title>Accesskeys: Thinking about them in a QWERTY world</title>
 <link>http://mobiforge.com/developing/blog/accesskeys-thinking-about-them-a-qwerty-world</link>
 <description>&lt;p&gt;Interestingly enough, in this time of excitement and interest in building apps for mobile phones, Google did a refresh on their &lt;span style=&quot;font-style:italic&quot;&gt;web&lt;/span&gt; apps for iPhone and Android. Go figure, seems like the mobile web isn&#039;t dead even on high end, high power devices. Even more, it would appear to make sense to build mobile specific web interfaces even for fully functional WebKit browser based devices. Imagine that!&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/accesskeys-thinking-about-them-a-qwerty-world&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/accesskeys-thinking-about-them-a-qwerty-world#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/mobile-design">Mobile Design</category>
 <category domain="http://mobiforge.com/usability">Usability</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/2014</wfw:commentRss>
 <pubDate>Wed, 29 Apr 2009 14:58:31 +0000</pubDate>
 <dc:creator>Ronan_Mandel</dc:creator>
 <guid isPermaLink="false">2014 at http://mobiforge.com</guid>
</item>
<item>
 <title>Handset Market Share Data (why it matters)</title>
 <link>http://mobiforge.com/developing/blog/handset-market-share-data-why-it-matters</link>
 <description>&lt;p&gt;With Mobile World Congress and CTIA now behind us, it&#039;s difficult to not get hot bothered and drooly about what new handsets are going to be on the market. Don&#039;t get me wrong, hot, new, fully functional and super sexy are all good things to have in a handset, especially in these otherwise gloomy times. However, as a developer it&#039;s important to remember to not get too carried away in the excitement, and here&#039;s why. The handset sales figures for November and December in the US &lt;a href=&quot;http://www.rcrwireless.com/article/20090108/WIRELESS/901079989/1081/by-the-numbers-top-10-most-popular-us-handsets-in-november&quot;&gt;were recently released&lt;/a&gt;, and a look at them reveals something telling for how one might (or might not) target content development.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/handset-market-share-data-why-it-matters&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/handset-market-share-data-why-it-matters#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/best-practices">Best Practices</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>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/2008</wfw:commentRss>
 <pubDate>Mon, 20 Apr 2009 09:07:03 +0000</pubDate>
 <dc:creator>Ronan_Mandel</dc:creator>
 <guid isPermaLink="false">2008 at http://mobiforge.com</guid>
</item>
<item>
 <title>Getting started with the ready.mobi API</title>
 <link>http://mobiforge.com/testing/story/getting-started-with-ready-mobi-api</link>
 <description>&lt;p&gt;&lt;a href=&quot;http://ready.mobi&quot;&gt;Ready.mobi&lt;/a&gt; is a well known page testing tool offered by dotMobi. When you supply a page URL to ready.mobi, it evaluates how well the page is likely to display on mobile devices by testing against the Mobile Web Best Practices, and dotMobi compliance rules. &lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/testing/story/getting-started-with-ready-mobi-api&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/testing/story/getting-started-with-ready-mobi-api#comments</comments>
 <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/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/dotmobi-compliance-0">dotMobi Compliance</category>
 <category domain="http://mobiforge.com/readymobi">ready.mobi</category>
 <category domain="http://mobiforge.com/tools">Tools</category>
 <category domain="http://mobiforge.com/http">HTTP</category>
 <enclosure url="http://mobiforge.com/sites/mobiforge.com/files/sample_java.zip" length="1483" type="" />
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1956</wfw:commentRss>
 <pubDate>Thu, 19 Mar 2009 12:50:56 +0000</pubDate>
 <dc:creator>ruadhan</dc:creator>
 <guid isPermaLink="false">1956 at http://mobiforge.com</guid>
</item>
<item>
 <title>Effective Design for Multiple Screen Sizes</title>
 <link>http://mobiforge.com/designing/story/effective-design-multiple-screen-sizes</link>
 <description>&lt;p&gt;So you&#039;re a designer and have been tasked with the design of a mobile web site. Chances are, unless you&#039;re designing for only one device you&#039;re quickly going to be faced with a common problem experienced by designers who work with mobile devices; figuring out what screen size to actually design for.&lt;/p&gt;
&lt;p&gt;For instance:&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/story/effective-design-multiple-screen-sizes&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/story/effective-design-multiple-screen-sizes#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/stylesheets">Stylesheets</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/usability">Usability</category>
 <category domain="http://mobiforge.com/client-side">Client-side</category>
 <category domain="http://mobiforge.com/css">CSS</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/1847</wfw:commentRss>
 <pubDate>Thu, 15 Jan 2009 17:32:43 +0000</pubDate>
 <dc:creator>bryanrieger</dc:creator>
 <guid isPermaLink="false">1847 at http://mobiforge.com</guid>
</item>
<item>
 <title>A Very Modern Mobile Switching Algorithm - Part II</title>
 <link>http://mobiforge.com/designing/story/a-very-modern-mobile-switching-algorithm-part-ii</link>
 <description>&lt;p&gt;This article follows on from last month&#039;s &lt;a href=&#039;/designing/story/a-very-modern-mobile-switching-algorithm-part-i&#039;&gt;Part I&lt;/a&gt;, where we discussed some of the principles of handling mobile users and switching their experiences. If you haven&#039;t read it yet please do so before we dive into some of the technical ideas and implementation details.&lt;/p&gt; &lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/story/a-very-modern-mobile-switching-algorithm-part-ii&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/story/a-very-modern-mobile-switching-algorithm-part-ii#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/hosting">Hosting</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/browsers">Browsers</category>
 <category domain="http://mobiforge.com/design-patterns">Design Patterns</category>
 <category domain="http://mobiforge.com/usability">Usability</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <category domain="http://mobiforge.com/publishing">Publishing</category>
 <category domain="http://mobiforge.com/cms">CMS</category>
 <category domain="http://mobiforge.com/http">HTTP</category>
 <category domain="http://mobiforge.com/php">PHP</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <enclosure url="http://mobiforge.com/sites/mobiforge.com/files/switcher_sample_implementation.zip" length="3326" type="application/zip" />
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1784</wfw:commentRss>
 <pubDate>Mon, 08 Dec 2008 11:20:03 +0000</pubDate>
 <dc:creator>James Pearce</dc:creator>
 <guid isPermaLink="false">1784 at http://mobiforge.com</guid>
</item>
<item>
 <title>Character Encoding Issues and the Mobile Web</title>
 <link>http://mobiforge.com/developing/story/character-encoding-issues-and-mobile-web</link>
 <description>&lt;p&gt;Character encoding, the binary representation underlying every symbol in documents delivered to mobile devices, is often treated as an afterthought in mobile Web development. Many developers simply rely upon ISO-8859-1; not a bad choice, as this encoding efficiently supports all important Western European languages, has long been available in the mobile and fixed Internet, is widespread among low-end phones, and is the default encoding in the HTTP standard.&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/character-encoding-issues-and-mobile-web&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/character-encoding-issues-and-mobile-web#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/usability">Usability</category>
 <category domain="http://mobiforge.com/standards">Standards</category>
 <category domain="http://mobiforge.com/http">HTTP</category>
 <category domain="http://mobiforge.com/html">HTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1796</wfw:commentRss>
 <pubDate>Fri, 05 Dec 2008 13:20:38 +0000</pubDate>
 <dc:creator>casaise</dc:creator>
 <guid isPermaLink="false">1796 at http://mobiforge.com</guid>
</item>
</channel>
</rss>

