The reason I used bluetooth is because of the original target platform, which was Nokia Series 60. The idea was to use whatever networking technologies were available, and for a lot of those phones it's bluetooth. If WiFi is available, then great, as long as you can have enough access to the stack in order to do ad-hoc style connections. With bluetooth, that's fairly easy to do. But yeah, I definitely want to support WiFi in the next version; it's just that this android SDK didn't even have an outline of a WiFi API, when it at least had the rudiments of a bluetooth one.
nick On Apr 17, 7:20 pm, GodsMoon <[EMAIL PROTECTED]> wrote: > Any reason you are using bluetooth instead of wifi? If I remember > correctly wifiArmy is using wifi for this kind of interaction. Can > anyone speculate on how many googlePhones will have wifi vs bluetooth? > > On Apr 17, 4:18 pm, nick <[EMAIL PROTECTED]> wrote: > > > Looks interesting, especially the combination of all of the varied > > services. Are you going to provide the API/library? I assume you > > simulated things for the video, since I don't think those services are > > available in the current SDK? > > > nick > > > On Apr 17, 1:32 pm, whitemice <[EMAIL PROTECTED]> wrote: > > > > As promised I have got my project website and videos online. > > > > Snowball is a revolutionary platform for getting location sensitive > > > content (and advertisements) onto your mobile. Its based around a > > > peer-to-peer network and provides a local area search API to your > > > Android Applications:http://www.zedray.com/snowball/ > > > > Let me know what you think. > > > Marl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Challenge" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-challenge?hl=en -~----------~----~----~----~------~----~------~--~---
