<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: URLs are special; Where the Web beats Native</title>
	<atom:link href="http://almaer.com/blog/urls-are-special-where-the-web-beats-native/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog/urls-are-special-where-the-web-beats-native</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Sat, 08 Sep 2012 07:06:53 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Arpit</title>
		<link>http://almaer.com/blog/urls-are-special-where-the-web-beats-native/comment-page-1#comment-47585</link>
		<dc:creator>Arpit</dc:creator>
		<pubDate>Mon, 15 Nov 2010 01:59:04 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/?p=2868#comment-47585</guid>
		<description>I feel the biggest thing missing from the web is higher level controls. I wish I HTML would evolve to look more like XUL, Flex or XAML. For example designing a list should only require defining it&#039;s item renderers, and it&#039;s API should include events like selected, dragged, dropped, etc. We can do these now but we end up building them from ground up and different implementations are inconsistent. This also requires less markup to define the app, which is important in today&#039;s mobile app world with spotty connectivity.

I guess I would really want browsers to evolve into something like Appcelerator Titanium, that uses runtime reflection to instantiate native controls.

Some more thoughts here, it&#039;s an old post of mine, but the thoughts remain valid (I hope)
http://www.arpitonline.com/blog/2009/11/23/web-applications-vs-real-applications-and-a-thoughts-on-moving-off-the-webpage-browser-for-apps-idea/</description>
		<content:encoded><![CDATA[<p>I feel the biggest thing missing from the web is higher level controls. I wish I HTML would evolve to look more like XUL, Flex or XAML. For example designing a list should only require defining it&#8217;s item renderers, and it&#8217;s API should include events like selected, dragged, dropped, etc. We can do these now but we end up building them from ground up and different implementations are inconsistent. This also requires less markup to define the app, which is important in today&#8217;s mobile app world with spotty connectivity.</p>
<p>I guess I would really want browsers to evolve into something like Appcelerator Titanium, that uses runtime reflection to instantiate native controls.</p>
<p>Some more thoughts here, it&#8217;s an old post of mine, but the thoughts remain valid (I hope)<br />
<a href="http://www.arpitonline.com/blog/2009/11/23/web-applications-vs-real-applications-and-a-thoughts-on-moving-off-the-webpage-browser-for-apps-idea/" rel="nofollow">http://www.arpitonline.com/blog/2009/11/23/web-applications-vs-real-applications-and-a-thoughts-on-moving-off-the-webpage-browser-for-apps-idea/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron</title>
		<link>http://almaer.com/blog/urls-are-special-where-the-web-beats-native/comment-page-1#comment-47582</link>
		<dc:creator>Ron</dc:creator>
		<pubDate>Sat, 13 Nov 2010 20:28:44 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/?p=2868#comment-47582</guid>
		<description>&gt;&gt;&gt; It would be nice if the native system would allow me to register a URL handler &gt;&gt;&gt; so the New York Times app could say “hey, if you see a nytimes URL, 
&gt;&gt;&gt; hand it to me and I can take care of it” 

Actually, it is possible - at least on iOS.  An app can register a URL scheme and be launched by the OS when such a URL is clicked by the user.  

See &quot;Communicating with Other Applications&quot; in http://developer.apple.com/library/ios/#documentation/iphone/conceptual/iphoneosprogrammingguide/StandardBehaviors/StandardBehaviors.html

I suspect this could also be done on Android using the SchemeRegistry (http://developer.android.com/reference/org/apache/http/conn/scheme/SchemeRegistry.html)</description>
		<content:encoded><![CDATA[<p>&gt;&gt;&gt; It would be nice if the native system would allow me to register a URL handler &gt;&gt;&gt; so the New York Times app could say “hey, if you see a nytimes URL,<br />
&gt;&gt;&gt; hand it to me and I can take care of it” </p>
<p>Actually, it is possible &#8211; at least on iOS.  An app can register a URL scheme and be launched by the OS when such a URL is clicked by the user.  </p>
<p>See &#8220;Communicating with Other Applications&#8221; in <a href="http://developer.apple.com/library/ios/#documentation/iphone/conceptual/iphoneosprogrammingguide/StandardBehaviors/StandardBehaviors.html" rel="nofollow">http://developer.apple.com/library/ios/#documentation/iphone/conceptual/iphoneosprogrammingguide/StandardBehaviors/StandardBehaviors.html</a></p>
<p>I suspect this could also be done on Android using the SchemeRegistry (<a href="http://developer.android.com/reference/org/apache/http/conn/scheme/SchemeRegistry.html)" rel="nofollow">http://developer.android.com/reference/org/apache/http/conn/scheme/SchemeRegistry.html)</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Zyp</title>
		<link>http://almaer.com/blog/urls-are-special-where-the-web-beats-native/comment-page-1#comment-47581</link>
		<dc:creator>Kris Zyp</dc:creator>
		<pubDate>Sat, 13 Nov 2010 18:34:32 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/?p=2868#comment-47581</guid>
		<description>I can&#039;t help but think that native apps could integrate with the web much better, it seems that the web actually was designed with many of these types of native applications in mind with MIME system. If native applications were registered as media handlers with the browser, they could launch in response to content negotiated media types (perhaps application/twitter and application/nytimes from your example). Click on a link to a twitter account and your native twitter app would popup, just like you want, and just like the web was designed to do. As long as native apps also present links that delegate back to the browser (which may in turn delegate back to another native app), it is participating in the web, at least at the REST level anyway (albiet not at the HTML level).</description>
		<content:encoded><![CDATA[<p>I can&#8217;t help but think that native apps could integrate with the web much better, it seems that the web actually was designed with many of these types of native applications in mind with MIME system. If native applications were registered as media handlers with the browser, they could launch in response to content negotiated media types (perhaps application/twitter and application/nytimes from your example). Click on a link to a twitter account and your native twitter app would popup, just like you want, and just like the web was designed to do. As long as native apps also present links that delegate back to the browser (which may in turn delegate back to another native app), it is participating in the web, at least at the REST level anyway (albiet not at the HTML level).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
