Open Source Java NFC Software

Open NFC is an open source stack implementing the NFC functionnalities for many OSes. The Open NFC stack offers a comprehensive set of NFC API for Android, Linux and Windows Mobile.

A small and simple Java API to read and write NFC cards. It supports mifare cards and PN 532 chips. This library works with RS232. More details: http://blog.sibvisions.com/2012/12/23/new-project-embedded-nfc/

NFC API for Android.

NFC is a scalable, distributed chat server and client implemented in Java. Notable features include built in load balancing and HTTP-tunneling support. Using the load balancing, a distributed network of servers can be formed, similar to an IRC network.

This is a kit of applications that runs in NFC mobile phones, user can read information on tags that contains a path to play a multimedia object previously store in external memory. Useful for treasure hunt or outdoor activities.

This Project gives instructions on how to setup a working environment with Eclipse to develop MIDlets for NOKIA 6131 NFC. The entire setup requires the installation of JDK, JRE, Eclipse ME, and NFC SDK.

The primary Source of communication With an Android-powered Device when dealing With NFC tags, is through NDEF Messages. However, when desiring to use the extended features of the individual tags, the user is required to implement the tags binary protocol stack. This Project is an attempt to ease the workload of Developers desiring this type of Access, by providing a simple API for communicating With the tags.

This is a set of NFC applications that uses a common framework that interacts with the JSR 257. There are two application examples: NFCMuseum and Picking.

YubiChallenge is an Android app that provides a simple, low-level interface for performing challenge-response authentication using the NFC interface of a Yubikey Neo. This app should be triggered using an implicit intent by any external application wishing to perform challenge-response. The intent name should be "com.yubichallenge.NFCActivity.CHALLENGE" and the challenge should be stored in an extra called "challenge". The response will be returned by the intent in an extra called "response".