http://socialtimes.disqus.com/enWed, 06 Feb 2008 12:58:24 -0000http://www.adweek.com/socialtimes/the-challenges-of-cross-platform-development/1159#comment-1574116<p>Edit: I meant the "gadgets" Javascript namespace in step 2 above....</p>DannyWed, 06 Feb 2008 12:58:24 -0000http://www.adweek.com/socialtimes/the-challenges-of-cross-platform-development/1159#comment-1574115<p>Given the reality of proprietary OpenSocial extensions like the one offerred by MySpace, IMHO the ideal development path for OpenSocial is the following:</p><p>1) Design your OpenSocial app to adhere strictly to the Google spec (currently at 0.7). This should suffice for most functions (profile/friend queries, rendering, sharing and activity stream pushing).</p><p>2) Write alternative paths for code that uses Google's "widgets" Javascript namespace, since not all containers (e.g. MySpace) implement them.</p><p>Ta da, you have an OpenSocial app that can run on any container, including Orkut and MySpace. Finally,</p><p>3) If your apps want to take advantage of extra metadata available via platform-specific, then go for it, making sure to test for existence of those calls in your code.</p><p>If you follow this path then you don't have to worry about "coding to the platform."</p>DannyWed, 06 Feb 2008 12:02:43 -0000http://www.adweek.com/socialtimes/the-challenges-of-cross-platform-development/1159#comment-1574114<p>I still think it's okay that people have to check out sites like <a href="http://www.allfacebook.com" rel="nofollow noopener" target="_blank" title="www.allfacebook.com">www.allfacebook.com</a> to find good apps ;)</p>Jonathan KleimanWed, 06 Feb 2008 11:08:52 -0000