Just back from a well deserved weekend off. :-)
>>This was very appealing when you had the emergency use case example. Not sure why you changed it to a trivial ice cream example. Now the wow factor has definitely come down in my mind. Any reasons, why the emergency use case is not highlighted?<<
99.9% of the people using the Snowball platform would do so for
location based search and advertising (search for Pizza, social
networking, dating, etc). However if someone wrote a messaging
application using this platform, they could highlight the emergency
use case as part of their design. The ice cream example is just an
easy way to get the concept across to people.
Everybody likes ice cream. ;-)
>>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?<<
Currently (i.e. on existing hardware) having Wi-Fi switched on uses
significantly more power than Bluetooth, hence it is a bit of a
problem for always-on-ad-hoc-networking, although I look forward to
tackling these problems when the hardware and APIs become available
Using cellular (via a server and cell id tags) is like putting an ad
hoc network on steroids, i.e. it does a lot of useful things like
improving the user experience on first use and reduces propagation
Also, I have put a lot of work into protecting user privacy, so unlike
other LBS technologies this does in no way compromise the user and
their location to the “government”.
>>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?<<
If you look at the architecture, you’ll see that I was able to
implement a lot of the technology already:
Snowball is just missing Bluetooth, Wi-Fi and actual handsets.
Hence the Snowball applications will work as soon as Google installs
them on an actual Android device - although they say they won’t be
When run in the emulator, some of my ADC submissions rely on the
server being injected with canned data (e.g. Pizzeria #1, User #2),
although Snowball Date users can publish their own profiles and watch
them appear on other devices. As the current Android emulator lacks
proper cell id simulation, there is no location sensitivity to this
Right now I am looking to partner with people who can make marketable
end user applications, so I can get feedback on the API and
concentrate my energies on getting the networking right.
In time I will publish the Snowball for Android client and make its
API available for general use.