It's hard to imagine that they'd close the device down to 3rd party development given that it runs OSX...there might be some limited benefits from the patent perspective that Joshua mentions, but seeing as the device is covered by 200 or so patents already, competitors aren't going to be able to come remotely close to this thing for years (unless Apple chooses to license the technology).
<br><br>I can imagine them developing certain quality standards and certification schemes to ensure that the average user has a high quality experience with any third party apps meeting the requirements (and buyer beware for any that don't)...but a total lock out would be a mistake I think.
<br><br>It was the availability of a wide variety of apps on DOS that held the Mac back from wider adoption. We could be in a similar situation today...people might be willing to accept a more awkward device if it's running a Palm or MS OS that has a large ecosystem of third party apps. Especially when you consider that people will inevitably develop killer niche apps that appeal to small segments of the population, but for those segments, such an app would be an absolute must and any device that doesn't run it would be worthless. I think the iPhone is incredible and I've wanted a miniaturized device capable of running OSX for a long time, but a locked down device is a serious handicap that would give me second thoughts (after all, half the reason I'd want one is to tinker around with it and write my own software for it).
<br><br>- Stephen<br><br><div><span class="gmail_quote">On 1/10/07, <b class="gmail_sendername">Howard Stearns</b> <<a href="mailto:hstearns@wisc.edu">hstearns@wisc.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Good point. This highlights the question of "what's a platform?"<br><br>Consider, as just one example, <a href="http://openlaszlo.org">openlaszlo.org</a> (which I mention because I<br>have friends there). Their fat-client Web-delivered apps "compile" to
<br>Flash or AJAX. Will iPhone Safari support Flash? Will it support DHTML<br>as much as the standard Safari does? If so, then it's hard for me to<br>technically or legally understand why a Laszlo kind of third-party app
<br>would be supported, but not a "native" third-party app? Flash and AJAX<br>have an API for applications to receive gestures and to display output,<br>and so does the operating system. What's the difference?
<br><br>I tend to think of Squeak as just another one of these kinds of<br>platforms, on which apps can run.<br><br>I wonder when they'll support the Parallels VM...<br><br>If the reasons for the distinction are just arbitrary, we could make a
<br>Flash or Java VM for Squeak, in which the .image/.changes/.sources files<br>all come over the Internet (hopefully with caching!)... I have no idea<br>how to estimate the performance.<br><br>-Howard<br><br>Darius Clarke wrote:
<br>> I suspect they'll make 3rd party development go the Web 2.0 route.<br>><br>> You develop with their tools on their hosted server (for a fee) and<br>> then they control what can go to which phones (for a fee that scales
<br>> with the number of targeted units).<br>><br>> Just a guess. Such a scenario lets them keep user experience uniform,<br>> predictable, and fewer disabling side effects. The scenario also keeps<br>> the bulk of processing on the servers where one has more room and
<br>> flexibility for creativity & interactivity with other processing<br>> services and other data stores. DabbleDB might be more the development<br>> tool we'd use for such a phone.<br>><br>> We'd probably prefer developing for the open source phone.
<br>><br>> Cheers,<br>> Darius<br>><br><br>--<br>Howard Stearns<br>University of Wisconsin - Madison<br>Division of Information Technology<br>mailto:<a href="mailto:hstearns@wisc.edu">hstearns@wisc.edu</a><br>
<a href="mailto:jabber:hstearns@wiscchat.wisc.edu">jabber:hstearns@wiscchat.wisc.edu</a><br>voice:+1-608-262-3724<br><br></blockquote></div><br>