Seriously, how do we, as developers,  not that I am one… but, anyway, read these data?  Tah Tah…The key word is….NDEF = NFC Data Exchange Format.  That’s what make everything so readable…there is actually a standard format for this device!

Now, just from the name, it gives me very little information, I must dig further down what was in NDEF:   An NDEF message contained old histories of the record on different devices tell the type of data were stored, the maker’s, then the way how the information being dispatch, what type of id was needed in order to dispatch…etc. All that was captured as  records in NDEF.

How should developers use NDEF?  We know now that NFC does one activity at a time on one device, so you smart  developer better know, it’s important to design a  straight forward activity of  what user really want and don’t screw up.  That’s not what Google said, I did  and  that’s how I interpreted it.  By all means, dispatching information directly to application is important.

First of all, how do you get activity when data was read over NDEF?  From Message a developer will find out it’s type of device, then developer build an intent to and from that type of device. Easy as that..if you developer know what Google is talking about, I am fine with it.

Secondly, the standard NDEF can be read in 2 types of dispatching record: “Well known”, “Text” such as payload.   My understanding of the “Well known” part is the coding that were set already for the NFC tags as per NFC Forum manifest.   As for the “text”, it could be something used for reading records like your addresses…

Summing from the above, we start to write intents filter – code of “MINE” type to “TEXT”  plain- for what ever type you just received from the NDEF record.. with intent filter you start to write your next message on how you would deal with the intent..  Ok, picture this, let’s say I have a selection of meat that I want to cook for my kids.  Thing is, I want to make only beef stew tonight because it’s easy and no need for cutting.  Chopped/sliced beef would be filtered to meet my need. After I selected the  beef , I would tell  the store that I want to make beef stew and received a pack of rue in result, this will be the 2nd message on how I want to deal with the  beef I bought.. Simple as that.

Google suggest developers to make practice on the intents filter in order to capture the activity precisely as you want.   Make sense, if I write “Stew” but they give me chicken meat, fish, and all sorts of things,that would be wasting my time to return the unwanted meat.   So, I need to write “for  Beef Stew Only” in order to get “beef” precisely.  Let’s not forget, NFC is a very small devise so the things we want to write is in a small “scale”.   In my case, “Beef Stew for only 3 People” .   No, my husband is not included because he always eat out.

 

Leave a Reply

(required)

(required)

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

当社サイトのご利用について  |  Image: scottchan / FreeDigitalPhotos.net
© 2013 アジャイル開発 | Enterprise Java | 株式会社アットウェア Suffusion theme by Sayontan Sinha