For me the close tie in with the hardware is what interests me in the project. It is not just software. You have access to the accelerometers data, gps data, wifi, and all the open hardware. I feel that will lead to the best possible solution for the phone. It is the software working together with the hardware that truly makes the neo 1973 and openmoko such a powerful tool. I have worked with the Openmoko's API and I have looked at the android api and they both seem to offer advantages. The Android API seems to be easier to use but less powerful. If you really need control then openmoko seems to be the answer. I don't have enough experiance with the others to really say what draws me to openmoko but if I had to say something it is the sense of being able to do anything with the support you need to make it actually happen.
<br><br><div class="gmail_quote">On Jan 16, 2008 6:00 PM, Michael Shiloh <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Lorn reminds me that there is another option in the "open source Linux<br>frameworks for mobile devices" space. (I think SVHMPC wanted to include<br>Trolltech as well. Not sure what happened.) (And of course there are
<br>other options besides these three.)<br><br>So the questions remain: What features make you choose one over the other?<br><br>And in particular, regarding Lorn's point below, how do you feel about<br>the different APIs?
<br><br>By the way, this is not meant to start an "us vs. them" battle. I'm not<br>out to prove that one is better than the other.<br><br>Android, Qtopia, and OpenMoko are all different, and each is aimed at a
<br>different type of developer. I'm interested in understanding what those<br>differences are, and how they influence a developer's choice.<br><br>Michael<br><br><br>-------- Original Message --------<br>Subject: Re: New to OpenMoko
<br>Date: Thu, 17 Jan 2008 10:45:27 +1000<br>From: Lorn Potter <<a href="mailto:email@example.com">firstname.lastname@example.org</a>><br>Reply-To: List for OpenMoko community discussion<br><<a href="mailto:email@example.com">
firstname.lastname@example.org</a>><br>To: <a href="mailto:email@example.com">firstname.lastname@example.org</a>, List for OpenMoko community discussion<br><<a href="mailto:email@example.com">firstname.lastname@example.org
</a>><br>References: <<a href="mailto:478E8AB6.email@example.com">478E8AB6.firstname.lastname@example.org</a>><br><<a href="mailto:478E8B79.email@example.com">478E8B79.firstname.lastname@example.org</a>><br><<a href="mailto:20080116234613.GA8662@stlux503.dsto.defence.gov.au">
20080116234613.GA8662@stlux503.dsto.defence.gov.au</a>><br><<a href="mailto:email@example.com">firstname.lastname@example.org</a>><br><br>andy selby wrote:
<br><br>> * ..Err help me out here Lorn<br>ummmm, better programming API? ;)<br><br><br>_______________________________________________<br>OpenMoko community mailing list<br><a href="mailto:email@example.com">
firstname.lastname@example.org</a><br><a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br></blockquote></div><br>