Explaining it is difficult because it depends on the perspective you
view it from. Moseycode includes:

  * A barcode symbology: which is a way of encoding binary data in a
pattern
  * A markup language: that instructs an application how to act for a
given barcode
  * A set of webserves: that barcode readers/publishers can use to
process the barcodes
  * A website: that you can use to register your own barcode ids
  * An android application: that you can use to scan and publish
barcodes

The barcode symbology is distinctive because it has been designed to
be extremely fast to scan. It is also free for anyone to implement
(just like all the specifications associated with Moseycode).

The markup language is novel because (I think) this is the first time
that an open language for barcode storage has been attempted in this
way. It stores primarily semantic information and other applications
could use the information in a different ways depending on the device
and context etc.

The android application is exciting (depending on your point of view)
because it uses AR to present the barcode information and is easily
used (via Intents and ContentProviders) with other Android
applications. It focuses on physical interaction.

The system as a whole is also location aware so it can track where any
barcode is scanned and log it. I'm not using android's mock location
providers because it's actually a semi live system now. So in the
absence of valid GPS data, the server fills in using geo lookups based
on IP address.

Finally, in addition to plugging Moseycode into android applications,
developers can forward data requests away from the Moseycode server
(which might only hold a 'stub' record for a set of barcodes) to their
own servers, so they can wrap the system at both ends: their
application can scan moseycode barcodes allocated by their servers.
Moseycode 'just' does the plumbing in between.

Not a short response, but hopefully clears it up.

The flippant answer to "why can't the emulator use the camera on my
laptop?" is to ask Google. It's because the emulator is a black box
that only connects to the outside world via keyboard, mouse and
network; there's no way to get any other data into it.


On Apr 12, 3:28 pm, jtaylor <[EMAIL PROTECTED]> wrote:
> I have to sit down and take a real look at this. You need to explain
> it very well, and very quickly. Also what differentiates it from the
> normal barcode system. Right now I'll have to spend at least half a
> day figuring it out. Which would actually be worth it because it peaks
> one's interest. Augmented Reality is cool.
>
> And why can't the emulator use the camera on my laptop?
>
> - Juan
>
> On Apr 11, 2:13 pm, tomgibara <[EMAIL PROTECTED]> wrote:
>
> > ...and another entry plops silently onto the virtual doormat of the
> > Googleplex.
>
> > Moseycode is an experimental new barcode system for handheld devices.
> > It provides an interactive bridge between the physical and digital
> > worlds.
>
> > This is version 0.2.0, here are some handy links for the latest
> > release:
>
> > Downloads, installation instructions and basic developer 
> > information:http://www.tomgibara.com/android/moseycode/releases/0.2.0/
>
> > A video of the barcode scanning in-action, produced to support its
> > entry into the ADC*:http://www.youtube.com/watch?v=D364ReDaZ3o
>
> > A short user guide 
> > (pdf):http://www.tomgibara.com/android/moseycode/releases/0.2.0/moseycode-i...
>
> > The latest online 
> > help:http://www.tomgibara.com/android/moseycode/releases/help
>
> > The website you need to register at to obtain publication 
> > accounts:http://www.moseycode.com
>
> > As ever, all comments and feedback welcome, but now I'm going off for
> > a whiskey.
>
> > * that's several months spent developing part of the application that
> > the judges can't even use because there's no camera support. *sigh*
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to