Thanks for the comment. Perhaps you should repost it over on the blogs<div> so everyone can benefit.</div><div> See below.<br><br><div class="gmail_quote">On Mon, Jul 20, 2009 at 11:44 AM, Laszlo KREKACS <span dir="ltr"><<a href="mailto:laszlo.krekacs.list@gmail.com">laszlo.krekacs.list@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Mon, Jul 20, 2009 at 5:47 PM, steven mosher<<a href="mailto:moshersteven@gmail.com">moshersteven@gmail.com</a>> wrote:<br>
> <a href="http://www.qi-hardware.com/" target="_blank">http://www.qi-hardware.com/</a><br>
<br>
</div>Sorry for being ignorant, but who are the target group?</blockquote><div><br></div><div> For the initial device the target audience is developers. Period. Going forward</div><div> the roadmap will be shaped by the community. In the Open. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<br>
I, for myself would not buy a device like this. It resembles like<br>
the old "manager calculator"... (my mom had one like 15 years ago or so)</blockquote><div><br></div><div> That's fine. The difference is you probably couldn't turn that old calculator</div><div> into a picture viewer, or offline wikipedia device, or notepad, or music player,</div>
<div> or plug in a Wifi adapter or have a say in the roadmap. But physically, yes,</div><div> it looks like one of those. Don't judge a book they say. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
It looks to me you are completely ignoring the world trend:<br>
More functions concentrate into less devices.<br>
People dont like to carry many things with them...</blockquote><div><br></div><div> A couple points: All all times during the evolution of devices you see</div><div> two trends: one trend toward the "all in wonder" and another trend toward</div>
<div> appliances. MP3 is my favorite example. being there at the start we faced</div><div> the same argument with one set of people ( in design) arguing that the PC</div><div> was going to be the center of convergence. Another set saying the phone</div>
<div> was going to be the center. A third set saying the game console would be the</div><div> center. Another set arguing the palm pilot would be the center. In the midst</div><div> of this was another group. We thought that a device dedicated to music</div>
<div> would get traction. And a device dedicated to video etc etc. At one point</div><div> ( long before the flip camera) we argued for a dedicated simple device for</div><div> video recording. The point is there are always two movements: one movement</div>
<div> toward integration ( swiss army knives) and another movement toward specialized</div><div> devices.</div><div><br></div><div> All that said, our road aims at enabling the type device you are talking about. Over</div>
<div> time we will add more capability to the device. But we will start with something</div><div> that WORKS and improve on that. Adding capability in a well disciplined manner</div><div> so that developers don't have to struggle with hardware that is dodgy. </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<br>
So what would be used for this device? A dictionary? An ebook? (too<br>
small display)<br>
A calendar?</blockquote><div><br></div><div> The device we adopted ( and opened) had the following proprietary software</div><div> on it.</div><div> 1. games</div><div> 2. MP3 player</div><div> 3. Audio recording</div>
<div> 4. Video (Mp4) player</div><div> 5. Dictionaries</div><div> 6. Photo viewer.</div><div> 7. Notepad.</div><div> 8. calculator.</div><div><br></div><div> We have no intention of creating our own software to go on this device. The Community</div>
<div> has plenty of applications it can put on the device. Or you could target putting open content</div><div> ( like wikitravel or wikidictionary etc ) on the device. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<br>
If it is used for something specific, who will develop the (specific)<br>
software for it?</blockquote><div><br></div><div> See above. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
<br>
I dont want to ruin the party, but looks to me you are ignoring the basics.</blockquote><div><br></div><div> I like to think we are embracing the basics. If we want to get to a device that has all</div><div> the features you want, what is the best way to get there? If I told you that the first</div>
<div> device we would build was going to have wifi and gps and touchscreen, and bluetooth, and</div><div> 3G and 3D graphics and replace your iphone, you'd rightly throw the bullshit flag.</div><div> Instead, we start with the basics. A device that works. From that foundation we can</div>
<div> move forward and build more complex things. You can be a part of that, contribute thoughts,</div><div> make critical comments, shape the future. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
<font color="#888888"><br>
Laszlo<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
</div></div></blockquote></div><br></div>