The good people at Inside Secure have ported over their Open NFC stack to Ice Cream Sandwich, giving OEM's one less hurdle to jump when getting devices ready for upgrading.  The new 4.3.3 release allows almost any NFC hardware to become Android compliant by using a Hardware Abstraction Layer and special kernel module to communicate via a set of consistent APIs.  What this means to you and I is that hardware developers can now use the free and robust Open NFC 4.3.3 stack to get their hardware working, and software developers can use the Android SDK add-on to communicate with it.  This means shorter engineering and development time dedicated to NFC from start to finish -- something that all impatient Android enthusiasts will be happy about.

Inside Secure says to expect new devices using the Open NFC 4.3.3 stack to ship later this year.  We don't know if this will be the push needed to make NFC relevant, but it sure can't hurt.  For more info, and more technical specifications than you can shake a stick at, see the links below.

Source: Inside Secure; via: PhoneScoop
More: Open NFC developer site

There are 11 comments

rem_kujawa says:

I didn't understand a single thing of that.

jms67 says:


cerob says:


Mayze says:


Melophat says:

In (very) simple terms, it means that the people who develop the open nfc software updated their code so that other developers can easily write software that uses the nfc hardware. The API they created is basically a pre-programmed set of tools that take all the messy parts of accessing the nfc hardware and clean it up, creating less confusing way of writing nfc enabled software.

Let me try it this way:

Imagine you make Android phones.  There's two boxes in your office filled with NFC chips.  One is small, and only has one or two choices -- this is the one directly supported by the Android source code.  If you use these NFC chips, you can use Google's code.

Now Imagine the other HUGE box has hundreds of different makes and models of NFC chip in it.  If you use any of these, you can't just use Google's code the way it was written.  But now, you can use Open NFC for Ice Cream Sandwich, because it supports a ton of hardware and communictaes directly with the system -- all you need to do it talk to this code.  Open NFC even provides a plug in for the Android SDK to help you make your software talk to their code.  

This helps OEM get current phones with NFC updated to ICS faster, and helps out when designing new devices by offering more hardware choice.

It also does other things, like offer up cross platform (Win, Mac, Linux, iOS, Android) solutions and helps handle difficult low level tasks by giving a set way to read, write, and use data with NFC.

It does all this and it's open source.

This is an all-around good thing :)

IceDree says:

Thank you

It's definitely a good step! Does this also mean the NFC code is available to third-party ROMs?



jmc2543 says:

Make it simple for everyone. It will make things easier for developers to start using nfc, beyond that if you aren't a Dev its not that big of a deal for u besides faster development.

DerekMorr says:

How is the OpenNFC stack different from the NFC APIs that already exist in the Android SDK?