Peer to peer exchange of content: we see the ‘sharing’ of files
The specifications also note that it’s possible to “share business cards, bookmarks, calendar notes, images, profiles, and more” so there is clearly a deeper integration between the Series 40 system and the NFC functions here than with earlier devices (we called for this in 2005 when we had the first look at the 3220). What is not shown is the before/after interactions that are required to set up these sharing actions. How do I set up the transfer? What happens if we simply touch phones together? What are the default events? Where and how are these actions phrased within the menu system? Without seeing these we cannot yet assess the quality of these new NFC interactions.
Touch-based interactions are super-simple, orders of magnitude less button clicks and less security hassles than a technology like Bluetooth. This simplicity stems from the physical proximity required when interacting with tiny RFID fields. The demo shows NFC pairing between two devices working in various physical ways: two phones are tapped side to side, face to face and face to back. Previously these interactions were imagined to work back to back but since RFID works through electromagnetic induction, which creates a field that encompasses both sides of the antenna, other physical gestures are possible.
When the NFC chip is given enough power and when the interaction involves two readers rather than a reader powering a passive tag, phone-to-phone interactions will work in many configurations around the device. Although this seems to be a technical reality, I wonder if it makes sense to visualise and explain NFC in this way? Should there be an active point of connection on the phone that is more like a button rather than an active aura surrounding the entire phone? There is an interesting study to be created here about the user’s mental models formed by these subtly different interaction types. More on touch-interaction affordances later.
This launch is not just about the NFC phone, but points towards a range of NFC appliances: “pairing with a Bluetooth NFC-enabled device, like the new NFC variant of the Nokia BH-210 headset, happens with just one touch”.
At first glance this suggests that new Nokia accessories may have embedded NFC tags, but it seems that “the Bluetooth Headset BH-210 sales package includes a pairing tag that has BH-210 address information in it. Pair the device and headset conveniently by tapping the tag with the device.” When suitable Mifare tags are available down to about 10mm in diameter, why not embed the pairing tag inside the device itself? Perhaps the fear is that pranksters could sneak up to unsuspecting bluetooth-headset-wearing businesspeople and pair with their devices through a sneaky swipe…
Nonetheless, this points in some interesting directions, towards interfaces and control for all sorts of consumer devices. It highlights the possibility of the mobile phone as a ubiquitous controller where it interacts with a multitude of inputs and outputs from games controllers and sensors to printers and screens, and then perhaps a whole host of other devices that require a rich interface but don’t have the physical form or price range to justify one. For more on this see our thoughts on the universal controller and this research paper by Christof Roduner.
The phone is packaged with three tags, one of which is a ‘tutorial’ tag that teaches the use of NFC with on-screen tutorials. This learning mode seems to include lots of animations where phones and tags are brought into contact with each other, perhaps the least complicated part of NFC interactions. Without seeing it for ourselves its difficult to say, but the tutorials could perhaps be more useful for explaining the possibilities inherent in putting URLs, phone numbers, etc. onto tags.
Physical design notes
If we are expected to regularly touch our phones against grubby payment terminals, subway gates and public advertising, the surfaces and materials both on the phone and in the world must encourage this touching action. A robust and rugged shell is essential.
From the very first mobile phones that could be operated with one hand, Nokia has traditionally been good at creating robust, over-engineered devices that play well in the messy, physical world. The challenge with NFC is to create natural, basic touch interactions through material, ergonomic or other affordances. What are the physical affordances that would encourage—- as Dourish puts it—‘interacting in the world, participating in it and acting through it, in the absorbed and unreflective manner of normal experience.’? So beyond ruggedness and a degree of scratch-proofing, what is necessary for these touch-interaction affordances?
The first consideration is the placement of the reader. The above image is a quick excercise imagining where readers might be placed on various phone models. The 5140 RFID kit and the 3220 NFC shell had a ‘classic’ or ‘candybar’ form that meant that the NFC reader was placed on the lower back of the device. Apparently this was to separate the various radio antennae (GSM, Bluetooth, etc.) from the RFID antenna, but all of our experiments showed that this was confusing to users. The 6131 solved this by placing the NFC reader at the top of the flip-up screen, away from the other antennae at the hinge.
Somehow the NFC reader in the 6212 is at the top of the device. This is a very good place to have an ‘active area’, it’s outside of the natural hand-grip, and its the part of the phone that most often faces the world, encouraging intuitive pointing and selecting gestures. With this placement the phone becomes a kind of ‘wand’, that perhaps draws on the metaphor of magic in ubiquitous computing. Whatever our thoughts on magic in interaction design, there is no doubt that this gesture is culturally significant and is likely to be a useful model.
More practically, the 6212 features a camera lens in roughly the same position as the reader. This combined with the perforated loudspeaker work against the idea of a robust active area. This is clearly a tradeoff, will scratches and grit getting into these delicate areas hinder touch-based interactions, and will keeping the phone pristine in general be a problem? Would a shiny iPhone ever be suitable for touch-based interactions?
The second consideration is signs and symbols. There was a time when Nokia thought it necessary to indicate the active area of NFC phones with a visual icon, starting with two concentric rings and moving on to the ‘wireless fingerprint’:
But the 6131 and 6212 have no visible indication whatsoever that they offer any sort of NFC functionality. The clear plastic film that protects the 6131 screen had a diagram of a phone-tag interaction but that of course gets quickly removed.
My feeling is that there should be clearer markings for the NFC active areas on these phones, even if it is a change in texture, colour or material, it seems like a functional necessity until NFC is properly accepted and understood in the mass market. It’s also a particularly easy thing to do. When music phones have very clearly marked dedicated buttons devoted to specific media functions, why shouldn’t a significant functional and interactional surface be clearly marked on the device?
A few quick sketches using some of the icons from the graphic language for touch. Whether the possibilities inherent in NFC are indicated through clear affordances or explicit symbology, this is extremely important to get right.
Other technicalities
The 6212 has a slightly better higher resolution camera than the 6131. It also offers a second video camera on the display side (why do they still include these, does anyone actually do video calling? Is there a secondary usage that I’m missing, YouTube?)
The press-release and demos emphasise the new level of integration between NFC and Bluetooth but the specifications don’t list Bluetooth 2.1. Of course it supports the standard contactless communication API (JSR 257) so that 3rd parties like us can develop applications for NFC. We hope that it gives us more leeway than the implementation on the 6131. Includes MIDP 2.1 and a few other Java APIs.
The phone also supports the Nokia Software Market for application discovery and this might be very useful for distributing consumer-focused NFC applications.
