Last year the Apple iPhone 6 joined the majority of smartphones by containing an NFC controller. However, at the moment, this new iPhone is locked down only to the Apple Pay mobile payment system. This means that iPhone 6 users are unable to take advantage of the massive potential of NFC through apps, tags and communication.
Despite this, in the 72 hours following it's launch, a million credit cards had been registered with Apple Pay - an indication of the popularity from Apple's user base. Since launch, we've been asked many times if an when Apple will open up access to the NFC controller and what difference it would make to the market. In answer to the first part - we simply don't know. Most commentators, including RapidNFC, believe that they will (and that it will be able to scan tags) but when is a different point.
As for what difference it would make, let's consider what will happen if the iPhone's NFC controller is opened up and allowed to function with NFC tags and applications.
Marketing is arguably one of the most anticipated uses for the iPhone's NFC function. Clearly, advertisers are currently holding back because without the iPhone, a percentage of all NFC marketing spend is going to be lost. A complete round-up of all phones changes that.
Additionally, while there are of course more Android users than iPhone users, iPhone owners are seen as spending more money than their Android counterparts, making them a valuable demographic.
As such, NFC marketing, such as smart posters or other promotional material, will become more attractive to retailers and advertising agencies once the iPhone can interact with NFC tags. This will affect Android and Windows Phone users as well as iPhone users due to Apple's influence. An example of this knock-on effect can be seen in America, where the release of Apple Pay helped grow the general mobile payments market. This launch saw boosts in the use of Android mobile wallet apps such as Google Wallet and Softcard which grew as more retailers struck deals with the companies.
Applications would benefit from NFC as current apps could be updated and new Apps could be developed and released to use this new functionality. NFC could be used in a number of ways in new applications. Apps could be released that write or read the tags or encode the tags with weblinks or trigger system setting changes. Another potential application could allow communication between devices, like Android Beam, that can send information easily from one device to another. Developing this theme of communication, applications could be used to connect and pass information from phones to other smart devices around the home – developing the Internet of Things.
NFC functionality could be incorporated into existing apps from retailers and other companies. This is one of the most interesting uses as it will allow stores to easily and intuitively interact with their customers. For example, NFC tags could be linked to further information on products or retailer's apps could allow extra functionality such as saving items for later. This concept is already being pioneered by Topshop using barcodes to save items for review, however using NFC tags would allow for a better experience, increasing ease of use for the users and so greater rewards for the retailer. Based on the range of apps that can tap into this NFC functionality, it is likely that, when the iPhone's NFC is unlocked, the next 'killer app' will use this feature.
The rapidly increasing use of NFC within Asset Management and similar user and object tracking and management systems has been once of the success stories of NFC. In fact, the significant majority of RapidNFC's business is working with companies rolling out asset management projects.
While we expect to see some 'glow' from iPhone NFC, it's unlikely to change the current momentum in this area as the hardware (the phones) are usually supplied or can be recommended. The cost and relative software and ecosystem restrictions of the Apple iPhone aren't as appealing to many developers in this area and we would expect to see Android continue to dominate in this area. (With possibly Windows Phone creeping in as many corporate clients start to move towards a Windows tech ecosystem).
When Apple does allow the iPhone to work with NFC, we expect there to be a large shift in both companies and consumers perception of NFC, as more marketing and applications become available that use this technology. Due to the popularity and the influence Apple has, we anticipate that NFC awareness will rapidly grow among both everyday consumers, across the platforms, and professionals in marketing and advertising.
Whatever happens, there are certain areas of the NFC market that will change very quickly.
RapidNFC have been fortunate to have been involved with many of Europe's largest NFC marketing campaigns over the last year. Projects have including outdoor advertising such as shop windows and bus stops, promotional marketing such as drinks mats, badges or giveaways, in-store marketing, magazine advertising, mailouts, flyers and much more.
One thing that connects all of these - as with any marketing campaign - is the desire to maximise response rates. Clearly, an NFC marketing campaign is always going to be about getting the maximum number of people to scan the tags.
So what have we learned ? Let's summarise in three main points.
Use the best performing tag you can. RapidNFC rate all our tags with our unique ScanStrength rating. The higher the rating the greater, in general, the scanning distance. And it makes a difference. We were involved in two campaigns during 2014 where the users interaction with the tags were very carefully recorded. On average, a typical mobile phone user will spend less than five seconds trying to scan a tag and then give up. Five seconds.
Additionally, in many cases, users didn't try to locate the hotspot on the phone by moving it around - they simply placed the phone and waited. Then gave up. The message here is clear - if you want to maximise response, make sure you use tags with the best possible ScanStrength and then get them as close as possible to the users phone.
This is a very common discussion with our team. Our recommendation is simple : Link to a mobile optimised website landing page and from there engage the user.
We've seen attempts to link to Facebook, download Apps and all sorts. All of these can have varying results across different mobiles. We have seen links through to webpages designed for desktops which don't render and take an age to load. Users will not wait for a download and they turn off very quickly if redirected to an App download (unless the campaign is specifically stating 'download our App here'!).
The best results were always that a fast response from the tag (see above) and a fast presentation of the campaign. Once the user has that initial response they will be substantially more willing to get involved from there.
We have saved the most important to last. This is the one where we have had the most discussion and the effect on perfecting that call to action on campaign performance is astonishing.
Let's be clear - not enough people know what NFC is. Many phone users have little idea that it's even on their phone or how to use it. Many iPhone users think they can scan NFC tags. So we need to help and this is crucial in the success of a campaign.
Two basic changes can make all the difference. This is what you need to do.
First, make sure you use the letters NFC. We've seen numerous marketing campaigns where advertisers have used an NFC logo (ours or the NFC Forum) without the letters 'NFC', perhaps with 'tap here' or something similarly vague. It's useless. There's a tiny amount of recognition for these logos.
Second, guide the user. A short phrase such as 'place your NFC enabled phone here' will work wonders. Better still, tell them why - 'place your NFC enabled phone here to get your voucher'. Using a picture of a mobile phone has shown to help but from our involvement either a picture of a phone or the word phone is just as good.
RapidNFC saw a gradual pickup in NFC marketing during 2014 but we feel that 2015 is the year where we will really start to see some high profile campaigns. This isn't just about getting users to interact with a campaign but getting users to really connect with products, brands and ideas. NFC can provide a very quick and easy link between a physical object like a poster, magazine or store shelf and online information, social networks and so much more.
But to get the maximum performance, it needs to be considered with more care than putting a simple website address on the bottom of a poster.
As most readers will know, the majority of the NFC tags we currently stock have a data capacity of around 37 - 144 bytes of data. There are larger capacity tags on the market, some of which we stock such as the 888 byte NTAG216. There's also more specialist tags with larger 4,000 or 8,000 byte capacities but these are extremely expensive and highly specialised.
However, there are 'standard' NFC tags currently being developed by a few companies which we have tested which hold large amounts of data. This raises the question: what, if any, are the benefits of having a tag with a 8,000 byte (8K) data capacity ?
Here at RapidNFC we can think of a three potential uses for such tags :
vCards - It would be possible to add a small image to vCard data with large capacity tags.
Instruction documents - It would be possible, for a tag with this capacity, to hold small text based instruction manuals and documents.
Encrypted data - Rather than purchasing an encryption tag, it would be possible for the tag itself to hold encrypted data directly.
There are a few issues with first two uses.
A general issue with vCards is that, regardless of the available standards, they are not universally compatible with all devices as each device has different contact settings and various devices interpret the vCard data differently (or not very well at all!). The image would still be of low quality and, ultimately, there is no guarantee that this will transfer to the device as intended or at all.
To access instruction documents in any meaningful way, the user would need a particular App pre-installed on the phone. Otherwise the device simply would not recognise the data - in some cases even if it was plain text. This begs the question, why not store the instruction manual online where access would be far more straightforward ? There is certainly an upside to not relying on the internet for the transfer of data, but holding the data on a server would be, by far, the easier and more reliable of the two options.
In addition to this, storing instruction manuals directly on large capacity tags is not very dynamic. Instructions may need be altered or updated regularly. The problem is that tags carrying instruction manuals would need to locked to be secure, however once locked they cannot be updated over time. This makes the idea of using large capacity tags to hold information documents and manuals impractical as you would need a new tag every time the information or instruction changes.
In addition to all of this, the price of one of these larger capacity tags would be higher than any of the NTAG, Topaz or Ultralight chips we currently stock; extra money for what appears to be a very limited set of benefits opinion.Pricing aside, our main issue with large capacity tags is that they seem to miss the point of how we see NFC in general. We have always considered that NFC should be thought of as a means to an end, rather than an end in itself. The best use of NFC is to create a link to data, rather than directly storing data. NFC works best as a connection between devices and data.
Therefore, while RapidNFC always consider any development with NFC as exciting - we can't see larger memory capacity tags as anything more than a very niche specialist item.
As most of our regular blog readers will know, the new iPhone 6 was launched with NFC for use with Apple Pay - Apple's new mobile payment service. However, Apple has decided for the moment not to open access to the NFC controller for developers. At the moment, there's no NFC API in the iOS SDK which means that, for the moment, there's nothing planned either.
Apple have remained tight on if and when NFC will be available for developers although the chances of it being within the next year seem to be slim. But now there's something else.
iFixit recently did a 'teardown' of the new iPhone 6 which showed the NXP NFC chip (65V10) and an AMS AS3923 chip which is likely to be used as an 'NFC booster' to increase the performance of the NFC antenna.
What's interesting here is that, at the moment, nobody seems to be quite sure where the NFC antenna actually is. And importantly, in a point raised by NFC World+ whether this might indicate that the antenna wouldn't be powerful enough for reading/writing NFC tags.
Let's look at a couple of points here.First is why the NFC antenna needs to be more powerful for reading/writing NFC tags than for payments. As many readers will know, NFC tags are not powered. The 'antenna' in an NFC tag isn't really an antenna at all, but is an inductor designed to convert a magnetic field into energy. When a mobile phone reads an NFC tag, this magnetic field and thus energy is provided by the mobile phone itself. How much energy is required to activate the tag depends on the NFC chip (NTAG203, Ultralight C, etc), antenna effeciency and so on. The mobile phone's ability to energise the tag is therefore vital.
The important point is that when a mobile phone is communicating to a powered reader - such as a payment terminal - the amount of energy provided by the phone is substantially less significant. For reading and writing tags, you would typically need a larger antenna - perhaps 10mm in diameter or more.
So where is this antenna in the new iPhone 6 ? So, couple of things from the September 2014 keynote speech. First is that in the demo of using the iPhone, the video clearly shows the phone's top edge being placed towards the payment reader - as opposed to the flat face on the back. Second is Apple's Eddie Cue commenting that the iPhone 6 and 6 Plus have '..a groundbreaking NFC radio antenna built across the top.'
Well that's kind of clear, but not exactly. As of today, as far as we know, nobody is actually still quite sure where the NFC antenna actually is. There's two likely positions. Either built into the PCB board which runs across the top edge of the phone or it may actually use part of the casing on the top edge of the phone. Bearing in mind the 'groundbreaking' comments regarding the antenna and the ability of the AS3923 chip to adapt tuning - it would certainly be fascinating if Apple are indeed using the case. Worth mentioning that in a 'Wireless Power Utilization In A Local Computing Environment' Patent Applicaton made by Apple at the end of November 2012, the idea of using the case had been considered : '..housing or a portion of a housing used to enclose the NFMR (near field magnetic resonance) power source can act to extend a useful range of the NFMR power supply.'
In any event, the point of all this is that while it's clear that a reasonable sized antenna would be required if the iPhone 6 / 6 Plus is to be used with NFC tags rather than just payments, there's nothing to indicate that such an antenna doesn't exist within the phone. Even if nobody seems to have actually found it yet.
Our popular Cumulative Discount scheme is available to all our registered users. The scheme is designed to help and reward our customers that regularly buy the same products from us.
Essentially, it is designed so that you pay the volume discount price based on all the purchases you have made for that product, not just what you are about to buy. So, for example, if you have purchased in the past a total of 1,000 units of a particular product (over any number of orders), then you would never pay more than the 1,000+ volume discount rate. It means you can get the higher level discounts simply because you have purchased enough in the past.
Simply register an account which is free and place an order. The system is all automatic and you get the discount without doing anything. Accounts are, obviously, completely free and we don't spam with unwanted email or anything silly like that.
NFC is a new technology and we are now moving into a phase where many of our original products are being replaced with updated or 'next generation' products. RapidNFC only stock the 'best of type' products so as soon as there's a better option, it is our policy to make sure we offer it. For example, many of our old NTAG203 products are being replaced now with the next generation NTAG213 chips and so on where the new products are better.
However, as we upgraded our products we found that many customers who had built up cumulative discounts on discontinued products lost their discount benefit.
Clearly, this isn't how we intended the Cumulative Discount system to work so we've now put in a place a new policy. From now on, we will duplicate all Cumulative Discount benefits from discontinued products to their equivalent replacement products. At the moment, we plan to do this at the point that the new product is introduced to the website so that as soon as the upgraded product is available, you can get the discount. You can also continue to get the discount on the product to be discontinued while we have stocks but after the discount 'duplication', further purchases will apply to one product or the other.
We have applied this duplication to a number of products already. As always, we are here to help so if any questions - just ask !
As most of our readers will be aware, Apple have now launched the iPhone 6 and Apple Watch. The iPhone 6 will ship with NFC support and the Watch will 'work with Apple Pay', indicating that it will also have NFC.
Clearly, this is a very significant step and one which will cement NFC's inclusion in mobile devices moving forward. NFC will become an essential feature in mobile devices rather than an additional feature.
However, it appears that access to the NFC controller is currently restricted to just Apple Pay. This essentially means that the features you get as standard on Android, Windows and BlackBerry for NFC such as pairing, scanning and encoding NFC tags and so on, are not yet available on the iPhone.
The inclusion of NFC hardware from NXP is likely to indicate that the device is capable of these additional features and the inability to use them is either because the software is just not yet ready or it's a strategic (economic) decision to lock these features down.
There has been some discussion that allowing access to additional NFC features has been restricted because Apple wants to find out a way to make money from them. For example, the idea that you can open your hotel room from your NFC enabled phone is brilliant but NFC is an open standard and therefore there's no direct benefit to Apple. If there's a way you can only open your hotel room with an Apple phone then the situation changes - even if the mechanism is still NFC.
Here at RapidNFC, we find that argument a little far fetched. It would surely be in Apple's interest to make the iPhone as powerful as possible and by opening NFC to the developer masses, the range of new Apps and possibilities from ticketing to asset management, trade shows to marketing could easily put the iPhone at the heart of an open NFC eco-system. We think it more likely that Apple simply didn't want to hint at NFC inclusion in the iPhone 6 by including any NFC APIs in the iOS 8 SDK.
So, as far as NFC in general is concerned, we consider Apple's iPhone 6 and Watch move a big step in the right direction but we haven't arrived yet .
Earlier this summer Microsoft started to release the next version of their mobile phone operating system, Windows Phone 8.1. Unlike Apple's iPhone, Microsoft has included extensive NFC support in their mobile operating system for some time. However, Windows Phone 8.1 builds on that support and adds a number of important updates.
One of the key differences in the way that Windows Phone handles an NFC Tag scan compared to Android is that the operating system will notify you of the scan, prompting you to ‘accept’ the scan contents. For example, a quick scan of a tag encoded with a web address will pop-up a window on the phone stating ‘Receive content? Someone is sharing a website .. with you’. To which you have to tap ‘accept’ before being redirected to the site.
This is annoying for two potential NFC markets. For marketing, it provides a barrier to interaction which can result in significant user drop-off. On Android, you wave your phone and it ‘magically’ opens a web page. On Windows, it feels like something bad is about to happen – like you are about to download a virus. For simple Applications such as launching settings or more complex Applications such as for Asset or Personnel Management it is simply a nuisance. You have installed the Application, you’ve probably even encoded the tag yourself or tapped the tag before. You don’t need the warning.
To be clear, the reason (as we understand it) is that it’s simply a security feature. Is it really safe that Android allows you to wave your phone over a tag and open a potentially virus infested website ? Maybe not. So Microsoft decided that the pop-up would show how security conscious Windows Mobile is and not let that happen. Fair enough perhaps.
However, in Windows Phone 8.1, you can stop this pop-up. Sort of. Essentially, if you have a tag that launches an App on your phone then the second time you scan that tag, it will ask if you if you don’t want the pop-up again in future. It will still ask you the first time. And importantly, it only appears to work with Apps rather than launching web pages for which you will always get the pop-up window.
For our customers considering developing advanced Apps for Windows Phone, this is certainly a plus. For marketing, nothing has really changed.
As most of our readers will know, every NFC tag has a Unique ID (UID) built into it during manufacture. It’s typically 7 bytes long (14 characters) and, because it cannot be changed and is very difficult to replicate to another NFC tag, is a quick and easy way to use NFC Tags to uniquely identify people and objects. Simple. So, you scan your phone over the NFC tag, read the UID and with a quick check against an external database can identify people and objects. Well, you can if you are using Android. Unfortunately, Windows Phone didn’t support reading the UID from the tags.
Well that’s changed. Sort of. Windows Phone 8.1 now supports the ability to read the UID from the chip. Except that it requires the right sort of NFC chip inside the phone to do it. And none of the current phones on the market have that chip. No. Really. Not even the new Nokia 930.
It’s very likely that upcoming phones will support this but as the penetration of the new phones will take a long time, it’s really only a feature that developers of ‘known hardware’ Apps are going to be able to use for the near future.
In short, locking an NFC Tag means that the data stored inside the tag (web address for example) is ‘locked’ and nobody can change it. Ever. You can do this with any Android phone but, hey ho, not with a Windows Phone.
The good news is that with Windows Phone 8.1, you can ! Except you can’t because, as above, there’s currently no phones with the internal chip to allow the software to do this. See above for more info.
Oh how we love this one. Quickly.. data is stored on an NFC Tag in a very specific way set out by the global body for this sort of thing called the NFC Forum. For example, if you want to store a web address, you don’t randomly put bits of data on the tag, you do it in a very defined NDEF data structure. Then any other NFC Forum compliant device can read it. Works great.
Now, many NFC Tags have what’s known as a ‘blank’ NDEF message on them at manufacture. This provides a very basic ‘NDEF Format’ so that the device reading it can immediately know that the tag is able to store NDEF data. There’s often other bits of information as well such as memory capacity. However, some NFC Tags, like the Ultralight chip, do not have this default NDEF data – they are effectively just blank.
So, in some cases, you can ‘NDEF Format’ the tags which essentially means putting this blank NDEF data onto the chip. It can be overwritten with other data so it’s there simply to provide a basic starter format.
Old Windows Phones couldn’t handle tags that didn’t have this NDEF Format. They couldn’t encode them at all. Which means that if you had a set of tags that were not formatted then they were useless to you if you had a Windows Phone.
All change on Windows 8.1. Problem solved, except…. By now you’ll get the general idea and if you haven’t, then read the sections above.
So there we are. Microsoft’s Windows Phone 8.1 has wrapped up a number of the major issues with NFC Tag support.
Except nobody can use them yet.
(With thanks to Windows Phone guru Andreas Jakl at Mopius.com for help in writing this article)
NXP's Mifare Ultralight chip is one of the most popular NFC chips. We use this chip in a large number of NFC products including wristbands, keyfobs, PVC cards and so on. It's a very reliable and universally compatible chip which works with all mobile phones.
The Ultralight EV1 is a 'next generation' version of the Ultralight and has a small number of additional features. These include counters, simple password protection and an originality signature.
RapidNFC aim to provide the latest and best performing products to our clients where it makes financial and logistical sense and we have started providing the new EV1 chip in some products.
Yes. And no. For all normal use cases the Ultralight EV1 can be used instead of the Ultralight so that the performance and other benefits can be realised. The standard memory configuration and UID structure is the same on both - although the EV1 has additional memory blocks for the password protection, counter and so on. In every case where we have seen, these additional memory locations do not interfere with function and therefore direct drop-in replacement is possible. However...
There is a bug. While the default memory structure on the EV1 is the same as the Ultralight, the default memory data is not. This is interesting because the default memory on the Ultralight does not contain 'proper' NDEF data but does contain some 'filler' data. The new EV1 contains simply blank data in the same locations.
And this is where the problem lies. When attempting to encode the new Ultralight EV1 tags with some Android phones, the phone is not recognising the tag type and failing to encode. All phones are able to read the tags, but are getting stuck encoding.
From the tests that RapidNFC have conducted, it seems that the problem only affects mobile phones with internal Broadcom NFC controllers not internal NXP NFC controllers. If you are using a phone with an NXP internal NFC chip, then you will not have this problem.
Well, as far as our research and the research of some helpful customers have found, it is all Broadcom chipped NFC phone but only Broadcom chipped NFC phones. Therefore, for example, the Samsung Galaxy S3 is good (use NXP), the S4 is not good (uses Broadcom), but the S5 is good (uses NXP).
If you have Ultralight EV1 cards and are unable to encode, then a quick unlocked encode with another Android NXP chipped phone will solve the problem. The process of encoding puts the correct data format on the tags to enable the Broadcom phones to encode EV1 chips.
Until we find a resolution to this issue, RapidNFC will stop stocking EV1 products and any customers purchasing any products we currently have with EV1 chips will be contacted to discuss options.
It's important to point out that this issue only affects the encoding of the Ultralight EV1 tags using these limited number of phones. We have no evidence or reason to believe that any device cannot read the tags or read the UID from the tags.
It's also important to note that this is a different type of bug - although similar- to the inability of Windows phones to read tags that haven't been NDEF formatted.
Like Bluetooth or WiFi, NFC is a wireless communication technology that offers value as part of a wider product. For example Bluetooth is a technology that allows photos to be shared between two mobile phones but without the wider product (the two phones and the software that makes the process happen) Bluetooth has little customer value. Similarly when you scan your contactless credit card at a payment terminal although NFC facilitates the transaction the value also comes from the software that handles the transaction and debits your account.
In the year to September 2013 Visa contactless card payments totalled £461.6 million, rising from £96.7 million the year before. The reason for this fourfold growth is that NFC provides a simple one touch interaction that can improve existing customer experiences, in this case contactless payments.
When NFC is analysed it is typically hailed as a magic bullet or derided as an old technology about to be surpassed by Apple's iBeacon or whatever the latest marketing buzzword is; both sides miss the point. NFC is already highly integrated and useful in a wide range of global industries, many of which will be mentioned in more detail below, and because of that NFC is here to stay and a technology worth learning about.
The exact number of NFC smartphones or the percentage in circulation is not known however as Apple is currently the only smartphone manufacturer that doesn't support NFC a strong picture can be drawn. The Q1 2014 smartphones sales in Europe show 19% of devices sold supported iOS (the iPhone operating system) and the US (the iPhone's most significant market) had 38.9% iOS sales, down from 46.6% the previous year.
Across the 12 key global markets 21.1% of smartphone sales are iOS devices. Taking into account that the vast majority of new Android and Windows Phone devices support NFC the number of NFC smartphones is significant and rising fast. For a more in depth analysis click here.
The application of NFC in mobile and contactless payments such as Google Wallet and Visa payWave is the primary reason for NFC's continued growth. Mobile payments is the reason Google first introduced NFC to smartphones with the Nexus S in 2011 and NFC is now supported by nearly all Android and Windows Phone devices.
NFC is used in a vast range of products, the most prominent being out-of-home advertising, healthcare monitoring, asset tracking, events and marketing. There are three main reason these companies chose NFC.
i. NFC smartphones are cheap, widely available and reliable. They also include a wide range of other useful technologies such as WiFi, network connections, a touch screen interface and Bluetooth. See a complete list of NFC enabled phones and tablets.
ii. Software development is affordable in the form of mobile apps or using an NFC tag to link to a webpage.
iii. NFC tags or smartcards are inexpensive and available in a wide range of formats. Click to find out more about NFC tags.
NFC, BLE and QR codes are all different technologies which in turn have different properties, advantages and disadvantages based on the situation. For example if a project is price sensitive QR codes (which are printed and therefore essentially free) are a much better option than iBeacons at $25 each. Find out more about NFC and how it compares with iBeacon and QR codes by clicking the links below.
i. What Is The Difference Between iBeacon and NFC? - Click Here
ii. NFC Tags vs QR Codes - How to Make the Right Choice - Click Here
NFC creates a one touch, frictionless interaction whether that is tapping a travel card (such as the London Oyster card) to a train station entrance gate or scanning a loyalty card at a payment terminal. Calling that interaction NFC rather than simply 'tap your card here' can cause unnecessary confusion.
If your product does require the user to know what NFC is, such as someone tapping their smartphone again a poster to launch a YouTube clip, it is beneficial to offer clear instructions so the user knows what to do.
The internet is filled with a large amount of debate on when/if the iPhone will support NFC however even information from 'reliable' sources or multinational corporations should be treated with caution. It is expected NFC will be included in the iPhone eventually however until Apple makes the announcement no-one truly knows.
Contactless and mobile payments using NFC require the continued global upgrade of POS (point of sale) infrastructure in retailers. This change is already making significant progress (in the UK most major retailers support contactless NFC payments already) however like any change on this scale it takes time and will not happen overnight.
At RapidNFC we are always on the lookout for simple and effect hardware solutions that can work in tandem with NFC tags; the MicroNFCBoard is just that offering an integrated development platform that can be used with Arduino, Raspberry Pi, mdeb or PC/Mac
The MicroNFCBoard is a highly diverse NFC development platform that allows for NFC tag emulation, NFC tag reading, NFC tag writing, AppNearMe mode and Android Beam. The applications of this are extremely far reaching with the potential for use in mobile payment platforms, out-of-home advertising, events and asset tracking.
The MicroNFCBoard is for NFC platform developers with an understanding of electronics hardware and software programming. If you have no previous experience with such development we instead recommend you read and write NFC tags with a non-programmer friendly mobile application such as NFC TagWriter available on Android.
Although many NFC enabled boards/readers are available online the accompanying software is very limited. The MicroNFCBoard uses an onboard microcontroller that takes care of NFC related processing and can be controlled using the API.
MircoNFCBoard also offers the unique AppNearMe mode which makes it simple to add an external UI to your project by creating inputs and outputs that can be coded into an NFC-enabled Android app.
See the Kickstarter project page for more information and how you can back this project.
New NFC products, comments, general views and other opinions about NFC tags, NFC phones and all things NFC !Tweets by @RapidNFC