<?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>Authoring</title>
 <link>http://mobiforge.com/authoring</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>A Beginner&#039;s Guide to Mobile Web Development</title>
 <link>http://mobiforge.com/starting/story/a-beginners-guide-mobile-web-development</link>
 <description>&lt;p&gt;While accessing the web on a mobile device is nothing new, a renewed interest in developing mobile web content has been ignited by the increased availability of WAP 2.0 devices, an abundance of skilled XHTML developers, and notable efforts by groups such as dotmobi and the W3C’s Mobile Web Initiative. &lt;p&gt;&lt;a href=&quot;http://mobiforge.com/starting/story/a-beginners-guide-mobile-web-development&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/starting/story/a-beginners-guide-mobile-web-development#comments</comments>
 <category domain="http://mobiforge.com/Starting">Starting</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/best-practices">Best Practices</category>
 <category domain="http://mobiforge.com/authoring">Authoring</category>
 <category domain="http://mobiforge.com/tools">Tools</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/151</wfw:commentRss>
 <pubDate>Fri, 09 Mar 2007 15:13:03 +0000</pubDate>
 <dc:creator>cameronmoll</dc:creator>
 <guid isPermaLink="false">151 at http://mobiforge.com</guid>
</item>
<item>
 <title>Mobile Web App Development with ASP.NET and HAWHAW</title>
 <link>http://mobiforge.com/developing/story/mobile-web-app-development-with-asp-net-and-hawhaw</link>
 <description>&lt;p&gt;Development of mobile applications is often highly dependent on the target platform.
        If plain old XHTML markup is written from scratch then it is rather easy to switch
        between platform and technologies. But if the development process has been accelerated and made comfortable by the use of tools and middleware, it soon becomes difficult or impossible to switch environments e.g. from a LAMP environment to ASP.NET or vice versa.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/story/mobile-web-app-development-with-asp-net-and-hawhaw&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/story/mobile-web-app-development-with-asp-net-and-hawhaw#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/authoring">Authoring</category>
 <category domain="http://mobiforge.com/content-adaptation">Content Adaptation</category>
 <category domain="http://mobiforge.com/frameworks">Frameworks</category>
 <category domain="http://mobiforge.com/asp-net">ASP.NET</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/2059</wfw:commentRss>
 <pubDate>Tue, 23 Jun 2009 15:24:01 +0000</pubDate>
 <dc:creator>H2f</dc:creator>
 <guid isPermaLink="false">2059 at http://mobiforge.com</guid>
</item>
<item>
 <title>Going Native (or you had me at &#039;hello&#039;) Part I</title>
 <link>http://mobiforge.com/developing/blog/going-native-or-you-had-me-hello-part-i</link>
 <description>&lt;p&gt;So I’ve got a confession to make here, I’ve been working on this bit for the better part of a month now in fits and starts, and having a hard time getting my head around it all. I started out with the notion of a quick primer comparing what it would take to knock out a quick ‘hello world’ on the various native platforms out there if you were to decide to do something other than a web app.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/going-native-or-you-had-me-hello-part-i&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/going-native-or-you-had-me-hello-part-i#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/developers-guide">Developers Guide</category>
 <category domain="http://mobiforge.com/authoring">Authoring</category>
 <category domain="http://mobiforge.com/client-side">Client-side</category>
 <category domain="http://mobiforge.com/tutorial">Tutorial</category>
 <category domain="http://mobiforge.com/brew">BREW</category>
 <category domain="http://mobiforge.com/java">Java</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1843</wfw:commentRss>
 <pubDate>Wed, 14 Jan 2009 11:47:16 +0000</pubDate>
 <dc:creator>Ronan_Mandel</dc:creator>
 <guid isPermaLink="false">1843 at http://mobiforge.com</guid>
</item>
<item>
 <title>The Google Phone Cometh (so what)?</title>
 <link>http://mobiforge.com/developing/blog/the-google-phone-cometh-so-what</link>
 <description>&lt;p&gt;Last week saw the announcement of the first Android based device, the HTC Dream better known now as the T-Mobile G1. Despite the fact that this phone is based on on Open Source platform, the details as they have been released, make it feel very much like any other smartphone that Joe Consumer can go purchase from his operator. It&#039;s locked to T-Mobile USA at launch and will find its way into the UK in November before it conquers the world in 2009. Now the real question: So what?&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/the-google-phone-cometh-so-what&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/the-google-phone-cometh-so-what#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/authoring">Authoring</category>
 <category domain="http://mobiforge.com/client-side">Client-side</category>
 <category domain="http://mobiforge.com/android">Android</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/1693</wfw:commentRss>
 <pubDate>Mon, 13 Oct 2008 14:00:00 +0000</pubDate>
 <dc:creator>Ronan_Mandel</dc:creator>
 <guid isPermaLink="false">1693 at http://mobiforge.com</guid>
</item>
<item>
 <title>An Operator Decides to be Polite… </title>
 <link>http://mobiforge.com/developing/blog/an-operator-decides-be-polite%E2%80%A6</link>
 <description>&lt;p&gt;Say what you will about the network operators with whom we have to play in the mobile space, but every now and again they do think of the developer community before implementing changes that may impact us all. Case in point, our friends over at &lt;a href=&quot;http://developer.att.com&quot;&gt;AT&amp;amp;T devCentral&lt;/a&gt; recently sent out an announcement to the developer community about changes that &lt;i&gt;will be coming&lt;/i&gt; as a result of some modifications to their gateway.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/an-operator-decides-be-polite%E2%80%A6&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/an-operator-decides-be-polite%E2%80%A6#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/authoring">Authoring</category>
 <category domain="http://mobiforge.com/http">HTTP</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1233</wfw:commentRss>
 <pubDate>Thu, 28 Aug 2008 21:00:01 +0000</pubDate>
 <dc:creator>Ronan_Mandel</dc:creator>
 <guid isPermaLink="false">1233 at http://mobiforge.com</guid>
</item>
<item>
 <title>FlashLite Version Detection update</title>
 <link>http://mobiforge.com/developing/blog/flashlite-version-detection-update</link>
 <description>		&lt;p&gt;So if you’re an active FlashLite or Flash developer who keeps an eye on the mobile space, you may have noticed something that happened last month with one of the web’s largest Flash delivery site: YouTube. The change was around the mechanism they used for version detection, and draws attention back to a topic close to the heart of every mobile developer (flash or otherwise): user-agent detection.&lt;/p&gt; 
		&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/flashlite-version-detection-update&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/flashlite-version-detection-update#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/authoring">Authoring</category>
 <category domain="http://mobiforge.com/flash-lite">Flash Lite</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1189</wfw:commentRss>
 <pubDate>Fri, 08 Aug 2008 10:43:29 +0000</pubDate>
 <dc:creator>Ronan_Mandel</dc:creator>
 <guid isPermaLink="false">1189 at http://mobiforge.com</guid>
</item>
<item>
 <title>The underestimated object element</title>
 <link>http://mobiforge.com/developing/blog/the-underestimated-object-element</link>
 <description>&lt;p&gt;One of the more powerful elements in XHTML MP (actually a part of XHTML, but extremely powerful and flexible in our mobile world) is the &lt;span class=&quot;geshifilter&quot;&gt;&lt;code class=&quot;geshifilter-text&quot;&gt;&amp;lt;object&amp;gt;&lt;/code&gt;&lt;/span&gt; element. Still, it is not used very often. So, I thought I would do some promotion!&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/the-underestimated-object-element&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/the-underestimated-object-element#comments</comments>
 <category domain="http://mobiforge.com/developing">Developing</category>
 <category domain="http://mobiforge.com/developers">Developers</category>
 <category domain="http://mobiforge.com/authoring">Authoring</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1146</wfw:commentRss>
 <pubDate>Thu, 17 Jul 2008 17:34:55 +0000</pubDate>
 <dc:creator>jonarne</dc:creator>
 <guid isPermaLink="false">1146 at http://mobiforge.com</guid>
</item>
<item>
 <title>The worst practices of the mobile web, part II</title>
 <link>http://mobiforge.com/developing/blog/the-worst-practices-mobile-web-part-ii</link>
 <description>&lt;p&gt;A few months ago, I blogged about the &lt;a href=&quot;http://mobiforge.com/blog/the-worst-practices-mobile-web&quot;&gt;worst mistakes&lt;/a&gt; I saw on mobile sites. Since this time I have visited and analysed plenty more mobile sites (so that my &lt;a href=&quot;http://find.mobi&quot;&gt;search crawler&lt;/a&gt; can process them better), and I have a few more offenders whose  practices can make mobile browsing a nightmare...&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/the-worst-practices-mobile-web-part-ii&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/the-worst-practices-mobile-web-part-ii#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/usability">Usability</category>
 <category domain="http://mobiforge.com/authoring">Authoring</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1011</wfw:commentRss>
 <pubDate>Fri, 23 May 2008 10:05:35 +0000</pubDate>
 <dc:creator>Cyril</dc:creator>
 <guid isPermaLink="false">1011 at http://mobiforge.com</guid>
</item>
<item>
 <title>WebKit by any other name… or How I found a use for JavaScript</title>
 <link>http://mobiforge.com/designing/blog/webkit-any-other-name%E2%80%A6-or-how-i-found-a-use-javascript</link>
 <description>&lt;p&gt;I’ve  been doing a great deal of thinking lately about JavaScript/ECMAScript and the mobile web. What I’ve been struggling with is the need or value for it when it comes to sites which are organically created for mobile. Sure there’s a need to support JavaScript as fully as possible for providing a ‘full web’ experience and managing existing content, but when it comes to designing for the mobile context, is there really value for it?&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/designing/blog/webkit-any-other-name%E2%80%A6-or-how-i-found-a-use-javascript&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/designing/blog/webkit-any-other-name%E2%80%A6-or-how-i-found-a-use-javascript#comments</comments>
 <category domain="http://mobiforge.com/designing">Designing</category>
 <category domain="http://mobiforge.com/designers">Designers</category>
 <category domain="http://mobiforge.com/usability">Usability</category>
 <category domain="http://mobiforge.com/authoring">Authoring</category>
 <category domain="http://mobiforge.com/ajax">AJAX</category>
 <category domain="http://mobiforge.com/xhtml">XHTML</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/1032</wfw:commentRss>
 <pubDate>Wed, 21 May 2008 10:39:26 +0000</pubDate>
 <dc:creator>Ronan_Mandel</dc:creator>
 <guid isPermaLink="false">1032 at http://mobiforge.com</guid>
</item>
<item>
 <title>Open Sesame</title>
 <link>http://mobiforge.com/developing/blog/open-sesame</link>
 <description>&lt;p&gt;There’s lots of chatter about ‘openness’ in the mobile space recently. If you’re listening to the media, you’re hearing it both on the handset and the network side. We’ve got the 700MHz spectrum auction that’s just wrapped up in which Google so cleverly forced the ‘openness’ provision to kick in. Verizon, the largest operator in the US (and the big winner in the C block that’s now required to be ‘open’), making statements that they’re going to allow ‘any device’ on their network.&lt;p&gt;&lt;a href=&quot;http://mobiforge.com/developing/blog/open-sesame&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://mobiforge.com/developing/blog/open-sesame#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/authoring">Authoring</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://mobiforge.com/crss/node/959</wfw:commentRss>
 <pubDate>Thu, 24 Apr 2008 03:30:17 +0000</pubDate>
 <dc:creator>Ronan_Mandel</dc:creator>
 <guid isPermaLink="false">959 at http://mobiforge.com</guid>
</item>
</channel>
</rss>

