On Sat, Mar 12, 2011 at 3:37 PM, Marcin Orlowski <webnet.andr...@gmail.com>wrote:
> On 12 March 2011 16:57, Kristopher Micinski <krismicin...@gmail.com> > wrote: > > > Note that I *never* mentioned using ad hoc mode, where did you get that? > > Read my previous post. There's no much choice if you go for Wifi - > either you use infrastructure mode which require, well, infrastructure > with router available, or you got with ad-hoc mode which, on android, > requires root and modified drivers. > > Agreed. > > Otherwise then, yes, but have you tried using Bluetooth for these types > of > > applications? The instability of it between different types of phones, > plus > > the requirement that it seems to be only supported well on more recent > > That's probably true. But we're not talking about implementation > quirks yet - just general approach. > > Okay, sounds good. > > phones just seems a bit shady. And I think that having to pair phones > seems > > like a fairly high barrier to using an app, can you imagine that that > would > > be at least a little annoying? > > You see a need of entering 4 digits (usually once per pair of devices) > a "high barrier", and at the same time it's no problem that you need > hardware router present? Good luck with your app in the woods :) > > With my app in a similar situation (an app for university students to exchange class notes), users did *not* want to pair their phone with another person's phone they did not know very well. Doing the pairing, in my experience, is not as easy as just typing four numbers: you also have to wait a few minutes to make the device discoverable and that takes a while (unless they already have the device as such). It's not just a quick thirty second, open the app, transfer the data, done, that most of the people wanted. Honestly it shouldn't be an issue, you'd think one or two minutes is no problem, but it just hasn't been the case for a mix of a little lost time and people not understanding what's involved in Bluetooth pairing (paranoid students not wanting to pair with twenty classmates, most of whom they don't know...) In the end we went with using the wifi connection and exchanging data over TCP/IP just using the routers, which worked much better: each student checks in, then they can exchange notes when next to each other when next to each other. N*ote that the popular ``bump'' system also works this way*: over internet rather than Bluetooth (like I thought it had, it's worth checking out). And yes, our app was like bump, you might ask why we didn't use it, but there was a little of content tracking involved for statistics reporting too. -- > Regards, > Marcin Orlowski > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
