请检查此链接 - 以非常详细的方式描述了两种解决方案之间的区别。 Sebastien 在此写下的答案是官方 Open NFC 堆栈声明。 Nikolay Elenkov 的说法也是正确的，除非您使用自己的设备或者以某种方式重新刷新它，否则您将仅使用 Google API。
BR 斯坦恩
please check this link - there is in a quite detailed way described the difference between both solutions. The answer written here by Sebastien is the official Open NFC stack statement. Also Nikolay Elenkov is right about the fact, that unless you are doing your own device or you are re-flashing it somehow you will use the Google API only.
综上所述 ： 在一些手机制造商将堆栈集成到设备中之前，对开放式 NFC 堆栈感兴趣并没有太大意义。应用程序开发人员无法使用 Open NFC，除非它位于硬件上。
At the moment (Android 2.3.4), the Android platform does not integrate the Open NFC stack. This stack has several advantages: not limited to one particular NFC hardware, portable to many different environments (not only Android), many additional features compared to the current stack. On the other hand, because Open NFC is not part of the standard Android environment, it requires some work (but it is actually quite easy) to use this stack in an Android platform. The Open NFC documentation describes this process.
The Open NFC stack is parallel activity and is optional replacement to the current stack. Due to its description it overcomes some limits of the Google NFC stack implementation and makes new HW adaptions (i.e. support for new tag types) easier…
This stack is intended to by used by device manufacturers, not mobile developers, because the standard Android kernel does not support modules loading, the Open NFC stack cannot be simply installed as another application, it requires a kernel change. But once the kernel is replaced, it is quite easy to deploy and use the Open NFC stack. An application developer should probably stick to the OS features, even if more limited, since they assure the portability of the code over any NFC-enabled phone. But if you are trying to use "more" features than what comes with Android, Open NFC is a good candidate.
In Conclusion : Until some phone manufacturer will integrate the stack into device, it does not make too much sense to be interested in Open NFC stack. An app developer cannot make use of Open NFC unless it is on hardware.
除非您要刷新自己的固件，否则您必须坚持使用 Android SDK 中提供的 API。如果您正在构建/定制自己的设备，您可以刷新支持 Open NFC 的映像和内核。我还没有实际使用过它，但看起来 Open NFC 提供了较低级别的 API，从而为您提供了更多控制权。
You already have the links, how about reading them?
Unless you are flashing your own firmware, you have to stick to the APIs available in the Android SDK. If you are building/customizing your own device you can flash an image and kernel that supports Open NFC. I haven't actually used it, but it looks like Open NFC offers lower level APIs, thus giving you more control.
发布评论
评论（3）
请检查此链接 - 以非常详细的方式描述了两种解决方案之间的区别。 Sebastien 在此写下的答案是官方 Open NFC 堆栈声明。 Nikolay Elenkov 的说法也是正确的，除非您使用自己的设备或者以某种方式重新刷新它，否则您将仅使用 Google API。
BR
斯坦恩
please check this link - there is in a quite detailed way described the difference between both solutions. The answer written here by Sebastien is the official Open NFC stack statement. Also Nikolay Elenkov is right about the fact, that unless you are doing your own device or you are re-flashing it somehow you will use the Google API only.
BR
STeN
目前（Android 2.3.4），Android 平台未集成 Open NFC 堆栈。该堆栈有几个优点：不限于一种特定的 NFC 硬件、可移植到许多不同的环境（不仅是 Android）、与当前堆栈相比有许多附加功能。另一方面，由于 Open NFC 不是标准 Android 环境的一部分，因此在 Android 平台中使用此堆栈需要一些工作（但实际上非常简单）。 Open NFC 文档描述了此过程。
开放式 NFC 堆栈是并行活动，并且是当前堆栈的可选替代品。由于其描述，它克服了 Google NFC 堆栈实现的一些限制，并使新的硬件适应（即支持新标签类型）变得更容易……
该堆栈旨在由设备制造商而不是移动开发人员使用，因为标准 Android 内核不不支持模块加载，Open NFC 堆栈不能简单地安装为另一个应用程序，它需要更改内核。但一旦更换内核，部署和使用 Open NFC 堆栈就变得相当容易。
应用程序开发人员可能应该坚持使用操作系统功能，即使更加有限，因为它们确保了代码在任何支持 NFC 的手机上的可移植性。但如果您想使用比 Android 附带的“更多”功能，Open NFC 是一个不错的选择。
综上所述 ：
在一些手机制造商将堆栈集成到设备中之前，对开放式 NFC 堆栈感兴趣并没有太大意义。应用程序开发人员无法使用 Open NFC，除非它位于硬件上。
At the moment (Android 2.3.4), the Android platform does not integrate the Open NFC stack. This stack has several advantages: not limited to one particular NFC hardware, portable to many different environments (not only Android), many additional features compared to the current stack. On the other hand, because Open NFC is not part of the standard Android environment, it requires some work (but it is actually quite easy) to use this stack in an Android platform. The Open NFC documentation describes this process.
The Open NFC stack is parallel activity and is optional replacement to the current stack. Due to its description it overcomes some limits of the Google NFC stack implementation and makes new HW adaptions (i.e. support for new tag types) easier…
This stack is intended to by used by device manufacturers, not mobile developers, because the standard Android kernel does not support modules loading, the Open NFC stack cannot be simply installed as another application, it requires a kernel change. But once the kernel is replaced, it is quite easy to deploy and use the Open NFC stack.
An application developer should probably stick to the OS features, even if more limited, since they assure the portability of the code over any NFC-enabled phone. But if you are trying to use "more" features than what comes with Android, Open NFC is a good candidate.
In Conclusion :
Until some phone manufacturer will integrate the stack into device, it does not make too much sense to be interested in Open NFC stack. An app developer cannot make use of Open NFC unless it is on hardware.
您已经有了链接，如何阅读它们？
除非您要刷新自己的固件，否则您必须坚持使用 Android SDK 中提供的 API。如果您正在构建/定制自己的设备，您可以刷新支持 Open NFC 的映像和内核。我还没有实际使用过它，但看起来 Open NFC 提供了较低级别的 API，从而为您提供了更多控制权。
You already have the links, how about reading them?
Unless you are flashing your own firmware, you have to stick to the APIs available in the Android SDK. If you are building/customizing your own device you can flash an image and kernel that supports Open NFC. I haven't actually used it, but it looks like Open NFC offers lower level APIs, thus giving you more control.