Preparation for NRF: Porting to the New Surface 2 SDK went Better than Expected

While working through the task, I realized it was not a conversion of a Surface application built on version 1 to version 2. It was a task in converting the application to conform to the newly integrated Windows 7 touch technology newly integrated with the Surface technologies.

Surface “contacts” are now called “touches” blending the language of surface into the Windows 7 environment. Additionally, another significant change is that manipulations are no longer processes that work on objects, but have been migrated to be functions within the UI elements. The application compiled successfully after addressing these two factors along with some additional minor tweaking.

The next step was to adjust the layout of the application.  The resolution of a Surface 1 application is not only smaller, but also a different aspect ratio than the new Surface 2. This impacted what I will call the stage of the application or background. The interactive objects used in the original application went unchanged as a result of the update.

Generally speaking, the conversion went fairly well with the biggest effort being the adjustment to the manipulations to the UI element level. In addition, developers should be aware that there are some changes to the application icon dimensions and the XML configuration file when running on a physical Surface unit.

I would say that when developing or converting applications for Surface 2, try not to reference version 1 too much, but rather, embrace the new Windows 7 touch environment. It’s not just Microsoft Surface, it’s also Windows 7.

CES & NRF 2012: More Insights Beyond the Technology

Like some other exhibitors and attendees, I made the quick leap from the Consumer Electronics Show (CES) in Las Vegas to the National Retail Federation (NRF) in New York City in a matter of a few short days. With so many exhibitors (and a lack of sleep) it’s not so easy to say one thing really stood out among the rest.

However, having been at both CES and NRF, one of the observations I’m most excited about is that the economy is definitely picking up. Based on the significant increase in numbers of exhibitors and attendees from 2009 to 2012, it is clear that companies are again exploring technology and have the desire to invest in digital merchandising solutions.

With that being said, I’d be remiss if I didn’t share some of the things I’ve been keeping my eye on.  This year the transparent LCD products are moving from concept to production and RFID is being implemented in more creative ways.  Both of these technologies have the ability to impact the consumer experience in retail.

Transparent LCDs

Transparent LCD technology is becoming more and more prevalent as a viable option for customer-facing digital merchandising initiatives. Samsung seems to have the lead in this space with one of the clearest and advanced solutions on the market.  One of the concepts I’ve seen in the past involved attaching the transparent LCD to the inside of a beverage refrigerator glass door.  Perching an implementation like this at the front of the checkout aisle, is a prime spot to display eye-catching content and to get the consumers attention on a product.  If implemented properly, it’s sure to be able to drive up brand awareness and increase sales.

RFID

There are many opportunities within the digital merchandising realm to leverage the power of RFID tagging. Perhaps, in ways that have not been previously thought of.  Reality Interactive has implemented RFID reading for projects before (Wave and Win contest) but since then the technology has advanced in its capabilities and reduced in cost.  Not only can RFID tagging be used for active scanning and inventory purposes, but also consumer interaction with merchandise or displays.

At NRF, while exhibiting our Microsoft Surface 2.0 application on the new SUR40. We started to conceptualize different options for integrating RFID location-based interactivity. During lunch, we sat next an individual who happened to be deep into the development of RFID technology and directed us to UPM‘s booth showcasing the work of their partner inMotion.  They were demonstrating a similar concept based on the movement of the RFID tag on a product  the display would change to more relevant content.  This definitely got the creative juices flowing. Enjoy the video below while I’m off to get some sleep!

Courtesy of Washington Post : see photo gallery of CES 2012

Essential Elements of Kiosk Solution Implementation: What Should You Know about the Deployment Process? Part I

A successful deployment starts with proper planning during the initial stages of a project. There are some very practical questions and areas of focus that need to be taken into account when pulling together a kiosk or digital merchandising project.

The overall development process, from concept to pilot, may only take 10-14 weeks, but the decisions that are made at the beginning of the process can be the most crucial. These decisions will determine how you’ll cut costs, save time, and reduce the amount of headaches you’ll have when you get to deployment.

Your deployment process should be thoroughly planned “upstream,” meaning during the manufacturing process, or by developing an easy to use installation “Wizard.”  Field installation should be swift, simple and obvious. Make sure to provide step-by-step, detailed, and specific guidelines and procedures.  The installer should not have to improvise or make decisions on your behalf.

The Kiosk is a “Toaster”

For many kiosk deployments, it is highly likely that there is no commonality among kiosks in the field. The installation process may vary. There may be different drivers, BIOS settings, and even hardware. All the units in a kiosk roll out should be identical, to the fullest extent possible. Think of them as toasters rather than remote PCs, each having the same hardware, the same wiring, the same software, etc.  Multiple field configurations can increase costs and support efforts. Additionally, it can make it more likely that you will have problems over the life of the program.

Don’t Think of Units as PC’s

Plain and simple: kiosks are not desktop environments. You don’t want people to make changes on individual units. If all the units are identical it makes troubleshooting and remote management substantially more efficient.  No one should be allowed “into” the PC to be making one-off changes. This applies to both the initial installation and ongoing management. It takes discipline, but with this philosophy there is either a problem on all the field units, or it’s a hardware problem on one specific unit. There is no in-between. If you abide by this practical advice, you will save time and money and increase your field uptime.

What to Install in the Field

Our “best practice” for deployment includes the testing of all parts and functionality of units before they are shipped. The manufacturing process should include QC, test, and setup of units before they are sent out for installation. We have witnessed many projects where final set up and testing was left to the field installer. Just think about it, if you have created a process that requires installers to assemble the units in the field, you will have increased costs and increased variability. Each installer will put things together differently, which will lead to more problems down the line.

You should have an idea in mind of what your unit is going to look like in the field and see to it that the manufacturing and installation processes makes that happen. Make sure you test the entire system prior to deployment. Test the speakers. Test the parts. Test everything!