Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

May 10 2012

Commerce Weekly: The competitive push toward mobile payment

Here are a few of this week's stories from the commerce space that caught my eye.

Mobile payments are coming, one way or another

Square_AngleyHands.pngThe New York Times (NYT) took a look this week at the push toward mobile payments and the various paths toward that end. The push isn't only coming from a consumer desire for a mobile wallet, but also from the payment companies. The NYT's post reports:

"Merchants are facing heavy pressure to upgrade their payment terminals to accept smart cards. Over the last several months, Visa, Discover and MasterCard have said that merchants that cannot accept these cards will be liable for any losses owing to fraud."

This could be the push needed for mobile payment, at least in the U.S., to get over the technology hump that has thus far been hindering it from catching on. Jennifer Miles, executive vice president at payment terminal provider VeriFone, told the NYT, "Everybody is going to be upgrading ... Before the credit card companies made their announcements, almost no merchants were buying terminals with smart card and NFC capabilities." She says VeriFone no longer installs payment terminals without NFC readers.

NFC technology, however, not only requires upgrades from merchants, but also consumers. The post reviews mobile payment solutions from PayPal and Square, noting the directive for these two companies may be more consumer centric:

"Both PayPal and Square say that asking customers to buy NFC-enabled phones and wait for merchants to install new hardware is folly. Neither company says it has plans to incorporate NFC into its wallet."

This consumer-centric approach might be part of what's behind VeriFone's announcement this week that it would jump into the payment processing fray. Bloomberg reports:

"VeriFone Systems Inc. (PAY), the largest maker of credit-card terminals, will offer an attachment that lets mobile devices accept credit and debit cards, making a deeper push into a market pioneered by Square Inc. and EBay Inc. (EBAY)'s PayPal ... VeriFone's version will allow partners such as banks to customize the service to transmit coupons and loyalty points to consumers, said Greg Cohen, a senior vice president at San Jose, California-based VeriFone."

VeriFone's system will work with Apple and Android mobile devices.

X.commerce harnesses the technologies of eBay, PayPal and Magento to create the first end-to-end multi-channel commerce technology platform. Our vision is to enable merchants of every size, service providers and developers to thrive in a marketplace where in-store, online, mobile and social selling are all mission critical to business success. Learn more at x.com.

MasterCard releases PayPass

MasterCard announced its new PayPass Wallet Services this week. The company describes the global service in a press release:

PayPass Wallet Services delivers three distinct components — PayPass Acceptance Network (PayPass Online and PayPass Contactless), PayPass Wallet and PayPass API. These services enable a consistent shopping experience no matter where and how consumers shop, as well as a suite of digital wallet services, and developer tools to make it easier to connect other wallets into the PayPass Online acceptance network.

In other words, it's designed to work with any sort of digital wallet used by its partners. According to the release, American Airlines and Barnes & Noble are in the initial group of merchant partners.

One of the big differences between MasterCard's system and those of its competitors is its open nature. PC World reports:

What sets MasterCard's offering apart from digital wallet systems announced by Visa, Google, PayPal and others is how much the company is opening up its platform to third parties, said Gartner wireless analyst Mark Hung. Banks and other partners will be able to adopt PayPass Wallet Services in two different ways: They can use MasterCard's own service under their own brand or just use the company's API (application programming interface) to build their own platform.

Mobile payment readiness, global edition

How ready is the world for mobile payments? MasterCard has that covered this week, too. In a guest post at Forbes, vice president of MasterCard Worldwide Theodore Iacobuzio wrote about the launch of the MasterCard Mobile Payments Readiness Index (MPRI), a data-driven survey of the mobile payments landscape. Iacobuzio says the index "assesses and ranks 34 global economies in terms of how ready (or not) they are for mobile payments of three types":

  • M-commerce, which is e-commerce conducted from a mobile phone or tablet.
  • Point-of-Sale (POS) mobile payments where a smart phone becomes the authentication device to complete a transaction at checkout.
  • Person-to-Person (P2P) mobile payments that involve the direct transfer of funds from one person to another using a mobile device.

Iacobuzio says that "one of the top-level findings is that unless all constituents — banks, merchants, telcos, device makers, governments — collaborate on developing new solutions and services, the mainstream adoption of mobile payments will be slower, more contentious and more expensive." He discusses the needs for mobile payments around the world, including in developed, developing and emerging countries.

But who's ready? The following image is a screenshot of the index summary. Note that no country has yet hit the "inflection point":

MPRIScreenshot.png
A screenshot of the MasterCard Mobile Payments Readiness Index (MPRI). Click here to access the full site.

Dan Rowinski at ReadWriteWeb has a nice analysis of the index. In part, he says much of the finance world, including MasterCard, may be viewing the mobile payment situation through "rose-colored glasses":

"For instance, why do mobile payments skew heavily toward young males in developed countries? The answer, more or less, is because it is cool. The actual need for mobile payments (NFC or otherwise) is not as clear in the U.S. as it is in other countries, like Kenya and Singapore."

Mobile shopping needs faster carts

Michael Darnaud, CEO of i-Cue Design, proposed a solution this week for one of the major problems with mobile shopping: speed, or lack thereof. In a post at Mobile Commerce Daily, he says the steps to a purchase simply take too long because of the number of data transfers involved:

"Just clicking a button to 'add,' 'delete' or 'change quantity' on the mobile Web requires sending transaction data from the shopper's mobile device to the vendor's server — average three to five seconds — via cell towers, not high-speed cables. These interim steps, long before checking out, are the challenge — it is all about time."

"Time is money" is no joke in mobile commerce. Darnaud notes: "A recent Wall Street Journal article declared that sales at Amazon increase by 1 percent for every 100 milliseconds it shaves off download times." To that end, he suggests an improvement to online cart technology that "reduces the time it takes to 'add,' 'delete' or 'change quantity' by virtually 100 percent because it eliminates the need for a server call for each of those commands." He describes his solution:

"This 'instant-add' cart solution requires nothing but familiar HTML and JavaScript. It is an incremental change that can be inserted into virtually any new or existing cart.

And what that means to a customer arriving at your site on the mobile Web is that he or she can see a product, click 'add to cart' and have no forced page change or reload or waiting time at all as a result."

Darnaud also notes the "elegance" of the solution: "... it forms a perfect bridge between desktop and mobile Web. The reason is simply that it works identically on both, via the browser."

Tip us off

News tips and suggestions are always welcome, so please send them along.

Related:

Understanding Mojito

Yahoo's Mojito is a different kind of framework: all JavaScript, but running on both the client and the server. Code can run on the server, or on the client, depending on how the framework is tuned. It shook my web architecture assumptions by moving well beyond the convenience of a single language, taking advantage of that approach to process code where it seems most efficient. Programming this way will make it much easier to bridge the gap between developing code and running it efficiently.

I talked with Yahoo architect fellow and VP Bruno Fernandez-Ruiz (@olympum) about the possibilities Node opened and Mojito exploits.

Highlights from the full video interview include:

  • "The browser loses the chrome." Web applications no longer always look like they've come from the Web. [Discussed at the 02:11 mark]
  • Basic "Hello World" in Mojito. How do you get started? [Discussed at the 05:05 mark]
  • Exposing web services through YQL. Yahoo Query Language lets you work with web services without sweating the details. [Discussed at the 07:56 mark]
  • Manhattan, a closed Platform as a Service. If you want a more complete hosting option for your Mojito applications, take a look. [Discussed at the 10:29 mark]
  • Code should flow among devices. All of these devices speak HTML and JavaScript. Can we help them talk with each other? [Discussed at the 11:50 mark]

You can view the entire conversation in the following video:

Fluent Conference: JavaScript & Beyond — Explore the changing worlds of JavaScript & HTML5 at the O'Reilly Fluent Conference (May 29 - 31 in San Francisco, Calif.).

Save 20% on registration with the code RADAR20


Related:


May 03 2012

Commerce Weekly: Mobile payments and the consumer experience

Here are a few stories from the commerce space that caught my eye this week.

Don't forget the mobile payment UX

PayPalSquareLogo.jpgCompetition in the mobile payment space is heating up, as Square's payment pace closes in on PayPal's, according to a report at Bloomberg. The report highlights a recent move by Square to lure in merchants: "The San Francisco company is making cash from sales before 5 p.m. on any day available in merchants' accounts on the next business day, compared with as many as five days out for other processors."

The real endgame, though, will be adoption by consumers, and Lauren Goode over at All Things Digital addressed the battle to control digital wallets from a UX perspective. Goode reports on her experience shopping around San Francisco and New York, paying either with Pay with Square or PayPal's mobile app. She says both apps are easy to use and that the biggest issue for both was the lack of merchants accepting payments of this type. Another issue she mentions caught my eye, however — the execution inconsistencies:

"Square has been touting the idea that this app actually allows for 'hands-free' payments ... One shop I bought coffee at didn't see my name right away, even though I had turned on the tab in the iPhone version of the app. I tried to buy another item using the app on a Samsung Galaxy Nexus Android phone, and my name didn't appear at all on the list of customers in the store.

But at another downtown coffee shop I was able to walk in, place my order and say, 'Charge it to Lauren Goode' — without taking my phone out of my pocket — and the transaction was completed in seconds."

And regarding a beef jerky purchase using PayPal's app:

"Since data service on my phone happened to be particularly bad in that area, I initially had trouble dropping the digital pin within the app that's supposed to let the merchant know I was there. The merchant also had to reboot his phone once to process the payment on his end. But once I switched over to Wi-Fi, I had four options for paying him ..."

Goode also reports on location-based features and the importance of merchant-provided content — her entire account is well worth the read.

X.commerce harnesses the technologies of eBay, PayPal and Magento to create the first end-to-end multi-channel commerce technology platform. Our vision is to enable merchants of every size, service providers and developers to thrive in a marketplace where in-store, online, mobile and social selling are all mission critical to business success. Learn more at x.com.


E-gifting and mobile commerce get social

Social gifting is gearing up to be one of the next big mobile commerce booms, according to a report at Reuters. The post focuses on the launch of Wrapp, a Swedish-based app startup, and highlights the blurring lines of online and brick-and-mortar commerce worlds. It describes the app:

"It allows Facebook friends to buy each other gift cards from participating retailers either individually or by teaming up, which they can store on their mobile devices and redeem either online or inside physical stores. Retailers like it because there is little marketing cost and because customers often end up buying more once they are inside the store."

Wrapp's CEO Hjalmar Winbladh told Reuters, "Brick-and-mortar retailers are all looking for new, more efficient ways to drive sales into stores without diluting their brands ... we wanted to really see how retailers can leverage the megatrends of smartphones and social networks."

TheFind also launched a social commerce app this week. It's called Glimpse, and it's a Facebook app that, according to the press release, "uses Facebook Like data from across the web to instantly personalize and curate a stream of fashion and design items that are trending, tailored to the tastes and preferences of an individual and their community of Facebook friends."

Ryan Kim at GigaOm calls the shopping discovery app a Pinterest rival and reports: "TheFind's CEO Siva Kumar told me TheFind has been working with Facebook for some time to bridge the two data sets, mapping a user's likes to products, their taxonomy and a user's profile. Now, when a Glimpse user likes a page, the service can determine what product the URL is referring to, can pull up the most recent availability and pricing data and also fit it into different styles and trends."


Move over smartphones, NFC to unlock experiences for Nook users

In an interview at CNN Fortune, Barnes & Noble CEO William Lynch talked about the future of the Nook and the recently announced partnership with Microsoft. In talking about opportunities in offline-online integration, Lynch offered an example of how B&N will improve customers' experiences:

"We're going to start embedding NFC [near-field communications] chips into our Nooks. We can work with the publishers so they would ship a copy of each hardcover with an NFC chip embedded with all the editorial reviews they can get on BN.com. And if you had your Nook, you can walk up to any of our pictures, any our aisles, any of our bestseller lists, and just touch the book, and get information on that physical book on your Nook and have some frictionless purchase experience. That's coming, and we could lead in that area."

Lynch told Fortune the NFC experience could appear as early as this year.

Related:

Jason Grigsby and Lyza Danger Gardner on mobile web design

This Velocity podcast with Cloud Four founding members Jason Grigsby (@grigs) and Lyza Danger Gardner (@lyzadanger) centers on mobile web performance. It's a fitting topic since these two wrote "Head First Mobile Web." Jason and Lyza have interesting insights into building high-performance websites that are ready for mobile.

Our conversation lasted nearly 20 minutes, so if you want to pinpoint any particular topic use the specific timing links noted below. The full interview is embedded at the end of this post.

  • The difference between a website and a mobile website 00:00:50
  • What tools are available for determining your performance benchmarks for a mobile web site? 00:03:18
  • What considerations need to be taken into effect to truly build a site that performs like greased lightning? 00:05:02
  • Has Google improved its Android browser to catch up with the Chrome browser? 00:07:04
  • What are some of the most common mistakes or patterns that developers make when building a mobile web site? 00:08:08
  • What do the two terms "mobile-first responsive web design" and "progressive enhancement" mean? 00:12:36
  • How do you make progressive enhancements when one Android phone may have five different browsers? Do you have five forks of a code base? 00:13:30
  • How do developers pick up best practices for mobile web development? 00:15:38
  • The mobile platform keeps growing and bringing lots of change. 00:17:13

If you would like to hear Jason Grigsby speak on "Performance Implications of Responsive Web Design," he is presenting at the 2012 Velocity Conference in Santa Clara, Calif. on Tuesday, June 26 at 1 pm. We hope to see you there.

Velocity 2012: Web Operations & Performance — The smartest minds in web operations and performance are coming together for the Velocity Conference, being held June 25-27 in Santa Clara, Calif.

Save 20% on registration with the code RADAR20

Related:

May 02 2012

Recombinant Research: Breaking open rewards and incentives

In the previous articles in this series I've looked at problems in current medical research, and at the legal and technical solutions proposed by Sage Bionetworks. Pilot projects have shown encouraging results but to move from a hothouse environment of experimentation to the mainstream of one of the world's most lucrative and tradition-bound industries, Sage Bionetworks must aim for its nucleus: rewards and incentives.

Previous article in the series: Sage Congress plans for patient engagement.

Think about the publication system, that wretchedly inadequate medium for transferring information about experiments. Getting the data on which a study was based is incredibly hard; getting the actual samples or access to patients is usually impossible. Just as boiling vegetables drains most of their nutrients into the water, publishing results of an experiment throws away what is most valuable.

But the publication system has been built into the foundation of employment and funding over the centuries. A massive industry provides distribution of published results to libraries and research institutions around the world, and maintains iron control over access to that network through peer review and editorial discretion. Even more important, funding grants require publication (but the data behind the study only very recently). And of course, advancement in one's field requires publication.

Lawrence Lessig, in his keynote, castigated for-profit journals for restricting access to knowledge in order to puff up profits. A chart in his talk showed skyrocketing prices for for-profit journals in comparison to non-profit journals. Lessig is not out on the radical fringe in this regard; Harvard Library is calling the current pricing situation "untenable" in a move toward open access echoed by many in academia.

Lawrence Lessig keynote at Sage Congress
Lawrence Lessig keynote at Sage Congress.

How do we open up this system that seemed to serve science so well for so long, but is now becoming a drag on it? One approach is to expand the notion of publication. This is what Sage Bionetworks is doing with Science Translational Medicine in publishing validated biological models, as mentioned in an earlier article. An even more extensive reset of the publication model is found in Open Network Biology (ONB), an online journal. The publishers require that an article be accompanied by the biological model, the data and code used to produce the model, a description of the algorithm, and a platform to aid in reproducing results.

But neither of these worthy projects changes the external conditions that prop up the current publication system.

When one tries to design a reward system that gives deserved credit to other things besides the final results of an experiment, as some participants did at Sage Congress, great unknowns loom up. Is normalizing and cleaning data an activity worth praise and recognition? How about combining data sets from many different projects, as a Synapse researcher did for the TCGA? How much credit do you assign researchers at each step of the necessary procedure for a successful experiment?

Let's turn to the case of free software to look at an example of success in open sharing. It's clear that free software has swept the computer world. Most web sites use free software ranging from the server on which they run to the language compilers that deliver their code. Everybody knows that the most popular mobile platform, Android, is based on Linux, although fewer realize that the next most popular mobile platforms, Apple's iPhones and iPads, run on a modified version of the open BSD operating system. We could go on and on citing ways in which free and open source software have changed the field.

The mechanism by which free and open source software staked out its dominance in so many areas has not been authoritatively established, but I think many programmers agree on a few key points:

  • Computer professionals encountered free software early in their careers, particularly as students or tinkerers, and brought their predilection for it into jobs they took at stodgier institutions such as banks and government agencies. Their managers deferred to them on choices for programming tools, and the rest is history.

  • Of course, computer professionals would not have chosen the free tools had they not been fit for the job (and often best for the job). Why is free software so good? Probably because the people creating it have complete jurisdiction over what to produce and how much time to spend producing it, unlike in commercial ventures with requirements established through marketing surveys and deadlines set unreasonably by management.

  • Different pieces of free software are easy to hook up, because one can alter their interfaces as necessary. Free software developers tend to look for other tools and platforms that could work with their own, and provide hooks into them (Apache, free database engines such as MySQL, and other such platforms are often accommodated.) Customers of proprietary software, in contrast, experience constant frustration when they try to introduce a new component or change components, because the software vendors are hostile to outside code (except when they are eager to fill a niche left by a competitor with market dominance). Formal standards cannot overcome vendor recalcitrance--a painful truth particularly obvious in health care with quasi-standards such as HL7.

  • Free software scales. Programmers work on it tirelessly until it's as efficient as it needs to be, and when one solution just can't scale any more, programmers can create new components such as Cassandra, CouchDB, or Redis that meet new needs.

Are there lessons we can take from this success story? Biological research doesn't fit the circumstances that made open source software a success. For instance, researchers start out low on the totem pole in very proprietary-minded institutions, and don't get to choose new ways of working. But the cleverer ones are beginning to break out and try more collaboration. Software and Internet connections help.

Researchers tend to choose formats and procedures on an ad hoc, project by project basis. They haven't paid enough attention to making their procedures and data sets work with those produced by other teams. This has got to change, and Sage Bionetworks is working hard on it.

Research is labor-intensive. It needs desperately to scale, as I have pointed out throughout this article, but to do so it needs entire new paradigms for thinking about biological models, workflow, and teamwork. This too is part of Sage Bionetworks' mission.

Certain problems are particularly resistant in research:

  • Conditions that affect small populations have trouble raising funds for research. The Sage Congress initiatives can lower research costs by pooling data from the affected population and helping researchers work more closely with patients.

  • Computation and statistical methods are very difficult fields, and biological research is competing with every other industry for the rare individuals who know these well. All we can do is bolster educational programs for both computer scientists and biologists to get more of these people.

  • There's a long lag time before one knows the effects of treatments. As Heywood's keynote suggested, this is partly solved by collecting longitudinal data on many patients and letting them talk among themselves.

Another process change has revolutionized the computer field: agile programming. That paradigm stresses close collaboration with the end-users whom the software is supposed to benefit, and a willingness to throw out old models and experiment. BRIDGE and other patient initiatives hold out the hope of a similar shift in medical research.

All these things are needed to rescue the study of genetics. It's a lot to do all at once. Progress on some fronts were more apparent than others at this year's Sage Congress. But as more people get drawn in, and sometimes fumbling experiments produce maps for changing direction, we may start to see real outcomes from the efforts in upcoming years.

All articles in this series, and others I've written about Sage Congress, are available through a bit.ly bundle.

OSCON 2012 — Join the world's open source pioneers, builders, and innovators July 16-20 in Portland, Oregon. Learn about open development, challenge your assumptions, and fire up your brain.

Save 20% on registration with the code RADAR20

April 30 2012

Mobile web development isn't slowing down

We're all well aware that mobile web development has gone through a complete metamorphosis over the last five years. We went from tiny screens with limited browsers to elegant multitouch displays with advanced web experiences. But even if you look at a shorter timeline — two years or so — you'll see that major improvements in mobile web development are still in progress. This space continues to produce exponential shifts.

In the following interview, "Programming the Mobile Web" author and Fluent Conference speaker Maximiliano Firtman (@firt) discusses some of mobile development's short-term leaps. He also looks at where mobile's envelope pushers will take us next.

At this point, what are the essential mobile development skills?

Maximiliano FirtmanMaximiliano Firtman: It depends on if we are targeting native or mobile web development, but usually an understanding of the mobile space is important. There are many differences between devices, so developers need up-to-date information on operating systems, versions, browsers, screen sizes, screen densities, multitouch, etc. That's why mobile usability and high-performance coding techniques are a must.

Related to that, what are the key mobile development tools?

Maximiliano Firtman: Emulators and simulators, while not perfect, are essential tools. Tools that debug and quickly deploy apps to real devices are also important. And the devices themselves are important for measuring performance and testing hardware-related features, such as touch, the accelerometer, GPS accuracy and even color palettes.

The first edition of your book, "Programming the Mobile Web," came out in July 2010. What are the major changes you've tracked in mobile web development since then?

Maximiliano Firtman: Since 2010, we've finally deprecated some old technologies such as WML and even XHTML MP. Today, HTML5 is king, while in 2010 we were talking about Apple or Webkit extensions.

In addition, the mobile web is no longer just for mobile websites. We can now also develop native web apps and even ebooks with EPUB 3. So, the platform is growing.

The tablet market was just starting two years ago, and now we have several vendors and operating systems. We also have new problems to deal with, such as screen density, performance optimization and even 3-D screens.

These days, we have a new vocabulary with responsive web design and responsive web design + server-side components (RESS). We also have lots of new APIs on the JavaScript side, new hardware APIs (motion sensors, battery, camera), and new mobile browsers (Google Chrome, Firefox, Amazon Silk).

Finally, we've seen the creation of a number of frameworks and debugging tools, including jQuery Mobile, Adobe Shadow and even iWebInspector — a free tool I've created for iOS web debugging.

What do you see happening at the edge of mobile web development?

Maximiliano Firtman: We are seeing browsers pushing boundaries, such as the live camera API inside WebRTC on Opera Mobile, Web Notifications and WebGL on BlackBerry PlayBook, and the Battery API on Firefox for Android.

Examples of envelope-pushing web apps include the Financial Times app, which has a great touch UI and offline access, and the Boston Globe website, which is a good example of responsive web design and RESS.

Fluent Conference: JavaScript & Beyond — Explore the changing worlds of JavaScript & HTML5 at the O'Reilly Fluent Conference (May 29 - 31 in San Francisco, Calif.).

Save 20% on registration with the code RADAR20

This interview was edited and condensed.

Related:

April 26 2012

Commerce Weekly: Mobile commerce is on the rise globally

Here are a few of the stories that caught my eye in the commerce space this week.

Survey shows global rise in consumer desire for mobile commerce

TNS Global's recent Mobile Life Survey, which surveyed the mobile habits of 48,000 people in 58 countries, shows that global interest in mobile commerce is on the rise. The screenshot of the survey's interactive results map below illustrates levels of interest for different commerce features — in this case mobile wallets:.

Mobile Life Survey screenshot
A screenshot of the TNS Global Mobile Life Survey results map. See the interactive version.

In a post for stuff.co.nz, William Mace took a deeper look at the survey results concerning the mobile commerce status in New Zealand. The results showed a bright future for mobile commerce, especially in the feature areas of mobile wallet and mobile banking. Mace reports:

"TNS New Zealand director David Thomas said New Zealanders surveyed liked the convenience of 'mobile wallets' — essentially using a smartphone to pay for goods and services — and placed the greatest trust in banks to provide such a service."

Thomas explained to Mace that technology and infrastructure are speed bumps to mobile wallets, much like here in the U.S. He said, "Mobile wallets generally require smartphones and generally a near-field communication chip in your phone which is still relatively unusual. The technology has driven mobile banking to come first but we can see with the developments of people like PayMark, Telecom and Vodafone are talking about we can see that the infrastructure for mobile wallets will come soon."

X.commerce harnesses the technologies of eBay, PayPal and Magento to create the first end-to-end multi-channel commerce technology platform. Our vision is to enable merchants of every size, service providers and developers to thrive in a marketplace where in-store, online, mobile and social selling are all mission critical to business success. Learn more at x.com.

EU investigates possible mobile wallet monopoly

Mobile wallet news wasn't all positive across the globe this week. In the U.K., where mobile retail is up 254% from last year and up 300% year over year for the first quarter of 2012, the European Union might become an additional speed bump to mobile wallets.

According to a report at Internet Retailer, the EU is looking into three U.K. telecommunications companies — Telefónica, Vodafone and Everything Everywhere — that announced a mobile wallet plan last June called Project Oscar. Plans were submitted in March. A press release from the EU explained that the problem lies in the potential monopoly:

"The Commission's initial investigation revealed that the joint venture and its three parent companies may have the technical and commercial ability and incentive to block future competitors from offering their own mobile wallet services to customers in the UK, or to degrade the quality of these competing mobile wallets so that they become less attractive."

According to the release, the commission has until the end of August to make a final decision.

Boston rail commuters get a paper ticket alternative

Consumers can buy a cup of coffee with an app (even in the drive-thru!) or a hammer with a phone number, and several companies offer local smartphone payment options for breakfast, lunch or dinner. By this fall, commuters in the Boston area can add "buying commuter rail tickets with an app" to that list. According to a post at Boston.com, the MBTA signed an agreement Friday that will allow "[c]ustomers with an iPhone, Android, or BlackBerry who download the free app [to] buy one-way, round trip, 10-ride, and monthly tickets and passes using debit or credit cards." The app will have a scannable QR code. The post describes how it will work:

"Riders will activate their pass when the conductor approaches, and it will generate a one-time image lasting long enough to be checked on the trip but not reused on another ride ... Though the mobile tickets will contain QR codes, the T will not initially equip all conductors with hand-held scanners, using them only for spot checks. Instead, digital watermarks, such as changing colors and animation, will help deter fraud while allowing passes to be verified at a glance."

The post pointed out that similar mobile payment options are common in England, "but the T would be the first major US commuter rail to offer passengers an alternative to paper." MBTA officials also told Boston.com they will use the new app to gather more accurate ridership data.

Related:

April 19 2012

Commerce Weekly: Facebook's shopping spree continues

You might have noticed I'm not David Sims, who has been writing this weekly payments column since its inception. David's talents now are required elsewhere, and I am delighted to have the honor of highlighting news from the payment space for you going forward. And now, onto the commerce stories that caught my eye this week.

Facebook buys into e-commerce

Tagtile.pngContinuing its startup shopping spree, Facebook late last week acquired Tagtile, a customer loyalty and direct marketing startup that blends social engagement for the consumer with custom direct marketing for the retailer. In a recent post for ZDNet, Eileen Brown noted that with its pending IPO, Facebook will need to look beyond ad revenues to satisfy shareholders:

"Ad revenue brings in over 83 per cent of the $3.71 billion total revenue reported. The potential for this revenue stream to fail is just too great ... After IPO, Facebook must diversify its revenue streams. And the only way it can currently do this is through online games and e-commerce."

This latest acquisition is a clear move in the e-commerce direction. Emil Protalinski at ZDNet described how Tagtile works:

"You walk into a store, tap your phone against the Tagtile Cube ... and you get discounts or rewards. Customers have to first download the Tagtile app ... which pushes targeted marketing material to their smartphone based on stores they visit. The Cube meanwhile provides data to help businesses pinpoint marketing efforts that work."

"Data" is the key word there — if Facebook has anything to sell, it's data, and if Tagtile has an organized system to manage and analyze consumer data, there's no need to reinvent the wheel. Brown pointed out in a later post that "[Facebook] needs to be able to mine its data stores to identify trends in customer spending to sell on to its business partners ... [It] needs to be able to bundle a solution to sell to brands who want to tap into Facebook's store of data for closer customer connections."

X.commerce harnesses the technologies of eBay, PayPal and Magento to create the first end-to-end multi-channel commerce technology platform. Our vision is to enable merchants of every size, service providers and developers to thrive in a marketplace where in-store, online, mobile and social selling are all mission critical to business success. Learn more at x.com.


Apple is ripe to disrupt the payment space

Jason Calacanis (@jason) argued over at Launch that "Apple will become a trillion-dollar company based not on iPads and Apple TV, but payments." His argument follows the line of why Apple (and Amazon, for that matter) are so successful: convenience and ease of use. Not to mention, Apple likely already has the data:

"Buying apps is easy and we do it all day long — on iOS at least — because our credit card number is already in the device ... Buying on Amazon is easy and we do it all month long — because our credit card number is already stored ... The person with hundreds of millions of stored credit cards wins big. There are only two people on the planet who have stored over a hundred million active credit card numbers that I can think of: Apple and Amazon.

One is in commerce and one isn't — yet."

There has been much speculation (going back a couple of years) about when and how Apple will enter the mobile payment space, but many agree the disruption that will occur in the payments space when it does happen will be profound. Likening Apple in the payments space to a "PayPal on steroids," an analyst told Computerworld in January that "[Apple has] 160 million users with digital wallets in iTunes accounts. They don't have to do anything other than to NFC-enable their phones."

Calacanis points out the flipside to that — Apple not only could corner the payments market, but also further secure its place in the smartphone market:

"Start doing the math and it gets scary: Apple would have massive margin, and vendors who didn't accept iPhone payments would be at a massive disadvantage the same way folks who didn't take credit cards were in the 70s and 80s."

His piece is well worth the read.

The future of money is mobile

Two surveys and a study this week shed some light on the current state of mobile money and what the future may look like. E-commerce company RichRelevance conducted a study of 4.4 billion mobile shopping sessions that took place between April 2011 and March 2012. As pointed out on Payments.com, the study found that "shoppers on their iPads account for 89 percent of all dollars spent through mobile shopping sessions." You can view the study infographic here.

RichRelevance screenshot
Click here to see the entire infographic.

And though, based on the graphic above, it seems people are becoming more comfortable purchasing TVs with their iPads, a survey (PDF) conducted by the Federal Reserve showed they're a bit more reluctant to conduct their banking via mobile devices. Ann Carrns at the New York Times took a look at the study and reported that "many consumers still don't see the need for mobile banking, and many also are skeptical of the level of security around banking with their phone." She also noted a statement made by Sandra F. Braunstein, director of the Fed's division of consumer and community affairs, to the Senate banking committee in March: "Specifically, consumers expressed concerns about hackers gaining access to their phones and exposing their personal financial information." You can view the full Federal Reserve survey report here (PDF).

A survey conducted by Elon University's Imagining the Internet Center and the Pew Research Center's Internet & American Life Project found that, regardless of any current fears or hesitations, the future of money is definitely mobile. In answering "What is the future of money?" the survey found that 65% of 1,021 "Internet experts and other Internet users" agreed with this statement:

"By 2020, most people will have embraced and fully adopted the use of smart-device swiping for purchases they make, nearly eliminating the need for cash or credit cards. People will come to trust and rely on personal hardware and software for handling monetary transactions over the Internet and in stores. Cash and credit cards will have mostly disappeared from many of the transactions that occur in advanced countries."

You can view the full survey report here.

Tip us off

News tips and suggestions are always welcome, so please send them along.

Related:

April 12 2012

Commerce Weekly: Bump taps mobile payments

Here are some of the commerce items that caught my eye this week.

Bump taps into payments

A Bump in progressBump relaunched its service this week as a PayPal-powered person-to-person payment service. Bump has been around for a few years, offering a clever way to share data that looks, to the casual user, as if it's transferring data locally from one device to another by bumping the two devices together. Is it using NFC? Infrared? Bluetooth? None of these, of course: Bump sends data through the cloud, locating the two sharing devices by their proximity and the reaction each device had to their bump. It seems pretty clever, as it enables virtual phone-to-phone transfers without having to wait on any assurance that the two phones share technology for syncing locally. As long as both phones can talk to the network — and would they be mobile phones if they couldn't? — Bump can process the transfer.

The capability for payments has always been part of the plan, but until now Bump has promoted itself primarily as a way to share contact and other information. Payments is a far more compelling use, though what Bump is actually doing is just sharing emails and looping PayPal into the process — just as you would if you were paying someone by going to PayPal's site from a laptop.

Still, how big can the market be for splitting the tab at dinner or sharing a tank of gas? The real upside for Bump must be in licensing its technology to other, more established payment processors, like PayPal. If you could Bump to pay at Home Depot or anywhere else where PayPal is accepted in the physical world, that would be simpler than having to key your mobile number into a keypad and faster than having to wait for a manufacturer to build NFC capabilities into your next phone.

X.commerce harnesses the technologies of eBay, PayPal and Magento to create the first end-to-end multi-channel commerce technology platform. Our vision is to enable merchants of every size, service providers and developers to thrive in a marketplace where in-store, online, mobile and social selling are all mission critical to business success. Learn more at x.com.

When will Apple enter the mobile payment race?

There's an interesting guest column by Ramzi Yakob, a strategist at digital agency TH_NK, on Wired's UK site about what mobile payments could do for Apple and (more importantly) what Apple could do for mobile payments. Yakob suggests that Apple is uniquely positioned to enter the increasingly crowded field of mobile payments — not exactly late, but not a first mover either — and reinvent it in its own image. What's interesting is that, even though Apple is now, on some days at least, the world's biggest company by market capitalization, Yakob notes that it isn't Apple's market might that gives it the power to enter and change industries:

"The position that Apple has now, not just financially but also within the hearts and minds of the modern consumer, gives it the perhaps unique ability to enter new sectors and make them 'Apple' in a way that feels completely natural to us — and by making them 'Apple', I mean, of course, beautiful, desirable, easy-to-use and hugely profitable."

The post is worth a quick read. (As an interesting aside, to point out how lax credit card security and scrutiny are, Yakob points to his brother's Tumblr where he shares pics of the ridiculous signatures he gets away with on restaurant tabs.)


Tip us off

News tips and suggestions are always welcome, so please send them along.


If you're interested in learning more about the commerce space, check out DevZone on x.com, a collaboration between O'Reilly and X.commerce.


Related:

April 10 2012

Carsharing saves U.S. city governments millions in operating costs

One of the most dynamic sectors of the sharing economy is the trend in large cities toward more collaborative consumption — and the entrepreneurs have followed, from Airbnb to Getable to Freecycle. Whether it's co-working, bike sharing, exchanging books and videos, or cohabiting hackerspaces and community garden spaces, there are green shoots throughout the economy that suggest the way we work, play and learn is changing due to the impact of connection technologies and the Great Recession.

This isn't just about the classic dilemma of "buy vs. rent." It's about whether people or organizations can pool limited resources to more efficiently access tools or services as needed and then pass them back into a commons, if appropriate.

Speaking to TechCrunch last year, Lauren Anderson floated the idea that a collaborative consumption revolution might be as "significant as the Industrial Revolution." We'll see about that. The new sharing economy is clearly a powerful force, as a recent report (PDF) by Latitude Research and Shareable Magazine highlighted, but it's not clear yet if it's going to transform society and production in the same way that industrialized mass production did in the 19th and 20th centuries.

Opportunity Infographic - The New Sharing Economy Study by latddotcom, on Flickr
Infographic from "The New Sharing Economy" study. Read the report (PDF) and see a larger version of this image.

Carsharing is saving

What is clear is that, after years of spreading through the private sector, collaborative consumption is coming to government, and it's making a difference. A specific example: Carsharing via Zipcar in city car fleets is saving money and enabling government to increase its efficacy and decrease its use of natural resources.

After finally making inroads into cities, Zipcar is saving taxpayers real money in the public sector. Technology developed by the car-sharing startup is being used in 10 cities and municipalities in 2012. If data from a pilot with the United States General Services Agency fleet pans out, the technology could be also adopted across the sprawling federal agency's vehicles, saving tens of millions of dollars of operating expenses though smarter use of new technology.

"Now the politics are past, the data are there," said Michael Serafino, general manager for Zipcar's university and FastFleet programs, in a phone interview. "Collaborative consumption isn't so difficult from other technology. We're all used to networked laser printers. The car is just a tool to do business. People are starting to come around to the idea that it can be shared."

As with many other city needs, vehicle fleet management in the public sector shares commonalities across all cities. In every case, municipal governments need to find a way to use the vehicles that the city owns more efficiently to save scarce funds.

The FastFleet product has been around for a little more than three years, said Serafino. Zipcar started it in beta and then took a "methodical approach" to rolling it out.

FastFleet uses the same mechanism that's used throughout thousands of cars in the Zipcar fleet: a magnetized smartcard paired with a card reader in the windshield that can communicate with a central web-based reservation system.

There's a one-time setup charge to get a car wired for the system and then a per-month charge for the FastFleet service. The cost of that installation varies, predicated upon the make of vehicles, type of vehicles and tech that goes into them. Zipcar earns its revenue in a model quite similar to cloud computing and software-as-a-service, where operational costs are billed based upon usage.

Currently, Washington, D.C., Chicago, Santa Cruz, Calif., Boston, New York and Wilmington, Del. are all using FastFleet to add carsharing capabilities to their fleets, with more cities on the way. (Zipcar's representative declined to identify which municipalities are next.)

Boston's pilot cut its fleet in half

"Lots of cities have departments where someone occasionally needs a car," said Matthew Mayrl, chief of staff in the Boston Public Works department, during a phone interview.

"They buy one and then use it semi-frequently, maybe one to two times per week. But they do need it, so they can't give up the car. That means it's not being used for highest utilization."

The utilization issue is the key pain point, in terms of both efficiency and cost. Depending on the make and model, it generally costs between $3,000 and $7,000 on average for a municipality to operate a vehicle, said Serafino. "Utilization is about 30% in most municipal fleets," he said.

That's where collaborative consumption became to relevant to Boston. Mayrl said Boston's Public Works Department talked to Zipcar representatives with two goals in mind: get out of a manual reservation system and reduce the number of cars the city uses, which would reduce costs in the process. "Our public works was, for a long time, administered by a city motor pool," Mayrl said. "It was pretty old school: stop by, get keys, borrow a car."

While Boston did decide to join up with Zipcar, public sector workers aren't using actual Zipcars. The city has licensed Zipcar's FastFleet technology and is adding it to the existing fleet.

One benefit to using just the tech is that it can be integrated with cars that are already branded with the "City of Boston," pointed out Mayrl. That's crucial when the assessing office is visiting a household, he said: In that context, it's important to be identified.

Boston started a pilot in February that was rolled out to existing users of public works vehicles, along with two pilots in assessing and the Department of Motor Vehicles. The program started by taking the oldest cars off the road and training the relevant potential drivers. Using carsharing, the city of Boston was able to reduce the number of vehicles in the pilot by over 50%.

"Previously, there were 28 cars between DPW [the Public Works department] and those elsewhere in the department," said Mayrl. "That's been cut in half. Now we have 12 to 14 cars without any missed reservations. This holds a lot of promise, only a month in. We don't have to worry about maintenance or whether someone is parked in the wrong place or cleaning snow off a car. We hope that if this is successful, we can roll it out to other departments."

The District's fleet gets leaner

While a 50% reduction in fleet size looks like significant cost savings, Serafino said that a 2:1 ratio is actually a conservative number.

"We strive for 3:1," Serafino said. "The one thing we have is data. We capture and gather data from every single use of every single vehicle by every single driver, at a very granular level, including whenever a driver gets in and out. That allows a city to measure real utilization and efficiency. Using those numbers, officials can drive policy and other things. You can take effective utilization and real utilization and say, 'we're taking away these four cars from this area.' You can use hard data gathered by the system to make financial and efficiency decisions."

Based upon the results to date, Serafino said he expects Washington, DC, to triple its investment in the system. "The original pilot was started by a mandated reduction by [former DC Mayor Adrian] Fenty, who said 'make this goal,' and 'get it done by this date.' Overall, DC went from 365 to 80 vehicles by consolidating and cooperating."

Serafino estimated the reduction represents about 50% of the opportunity for DC to save money. "The leader of the DC Department of Public Works wants to do more," he said. "The final plans are to get to a couple of hundred vehicles under management, resulting in another reduction by at least 200 cars." Serafino estimated potential net cost savings would be north of $1 million per year.

There is a floor, however, for how lean a city's car fleet can become — and a ceiling for optimal utilization as well.

"The more you reduce, the harder it gets," said Serafino. "DC may have gone too far, by going down to 80 [vehicles]. It has hurt mobility." If you cut into fat deep enough, in other words, eventually you hit muscle and bone.

"DC is passing 70% utilization on a per-day basis," said Serafino. "They have three to four people using each of the cars every day. The trip profile, in the government sense, is different from other customers. We don't expect to go over 80%. There is a point where you can get too lean. DC has kind of gotten there now."

In Boston, Mayrl said they did a financial analysis of how to reduce costs from their car fleet. "It was cheaper to better manage the cars we have than to buy new ones. Technology helps us do that. [Carsharing] had already been done in a couple of other cities. Chicago does it. The city of DC does it. We went to a competitive bid for an online vehicle fleet management software system. [Zipcar] was the only respondent."

Given that FastFleet has been around for more than three years and there's a strong business case for employing the technology, the rate of adoption by American cities might seem to be a little slow to outside observers. What would be missing from that analysis are the barriers to entry for startups that want to compete in the market for government services.

"What hit us was the sales cycle," said Zipcar's Serafino. "The average is about 18 months to two years on city deals. That's why they're all popping now, with more announcements to come soon."

The problem, Serafino mused, was not making the case for potential cost savings. "Cities will only act as sensitive as politics will allow," said Serafino.

"Boston, San Francisco, New York and Chicago are trying. The problem is the automotive and vehicle culture," Serafino said. "That, combined with the financial aspects of decentralized budgeting for fleets, is the bane of fleet managers. Most automotive fleet managers in cities don't control their own destinies. Chicago is one of the very few cities where they can control the entire fleet.

Cities do have other options to use technology to manage their car fleets, from telematics providers to GPS devices to web-based reservation systems, each of which may be comparatively less expensive to buy off the shelf.

One place that Zipcar will continue to face competition at the local level is from companies that provide key vending machines, which are essentially automated devices on garage walls.

"You go get a key and go to a car," said Serafino. "If you have 20 cars in one location, it's not as likely to make sense to choose our system. If you have 50 cars in three locations, that's a different context. You can't just pick up a keybox and move it."

Collaborative consumption goes federal?

Zipcar is continuing along the long on-ramp to working with government. The next step for the company may be to help Uncle Sam with the federal government's car fleet.

As noted previously, the U.S. General Services Agency (GSA) has already done a collaborative consumption pilot using part of its immense vehicle fleet. Serafino says the GSA is now using that data to prepare a broader procurement action for a request for proposals.

The scale for potential cost savings is significant: The GSA manages some 210,000 vehicles, including a small but growing number of electric vehicles.

Given congressional pressure to find cost savings in the federal budget, if the GSA can increase the utilization of its fleet in a way that's even vaguely comparable to the savings that cities are finding, collaborative consumption could become quite popular in Congress.

If carsharing at the federal level succeeded similarly well at scale, members of Congress and staff that became familiar with collaborative consumption through the wildly popular Capital bike sharing program may well see the sharing economy in a new light.

"There's a broader international trend to work to share resources more efficiently, from energy to physical infrastructure," said Mayrl. "Like every good city, we're copying the successful stuff elsewhere."

Related:

April 06 2012

Promoting and documenting a small software project: VoIP Drupal update

Isn't the integration of mobile phones and the Web one of the hot topics in modern technology? If so, VoIP Drupal should become a fixture of web development and administration. I have been meeting with leaders of the project to help with their documentation and publicity. I reported on my first meeting with them here on Radar, and this posting is one of a series of follow-ups I plan to write.

Immediate pressures

When Leo Burd, the lead developer of VoIP Drupal, first pulled together a small cohort of supporters to help with documentation and promotion, only three weeks were left before DrupalCon, the major Drupal annual conference. Leo was doing some presentations there, and the pressing question was what users would want in order to get interested in VoIP Drupal, learn more about it, and be able to get started.

Leo was indefatigable. He planned to get some new modules finished before the conference, but in addition to coding and preparing his own presentations, he wanted to address the lack of introductory materials because it might get in the way of enticing new users to try VoIP Drupal.

In the end, Leo led a webinar to drum up interest. The little group of half a dozen self-selected fans reviewed his slides, sat in on a preview, and helped whip it into a really well-focused, hard-hitting survey. This webinar had 94 participants from 19 countries and more than 40 companies.

Michele Metts, a non-profit activist and Drupal consultant, also stepped up to create slides and lead webinars with slides explaining VoIP Drupal basics.

Slide from a VoIP Drupal webinar
Slide from a VoIP Drupal webinar

Although we agreed that many parts of the system needed more documentation, it was a more effective use of time at this point to do webinars. VoiP Drupal has many interactive aspects that are best shown off through demonstrations. As I'll explain, documentation would require more resources.

Perceptions and challenges

Responses to the webinar and to Leo's DrupalCon presentation helped us understand better what it would take to win more adherents to this useful tool. Leo reported that few people knew of the existence of VoIP Drupal, but that when they heard of it, they assumed it would be expensive. His impression was that they knew traditional PBX systems and didn't realize how much more low-cost and light-weight VoIP is.

In my opinion, Web administrators (and many content providers) still see the Web and the telephone as separate worlds, never to meet. This despite the increasing popularity of running queries and Internet apps on mobile devices. We have to address server-side apathy. There should come a day when the things VoIP Drupal does are taken for granted: people leaving phone numbers on Web sites to receive SMS or voice updates, pressing Web buttons on their cell phones to get an interactive voice menu, etc.

The versatility of VoIP Drupal gives it fantastic potential but makes it harder to explain in an elevator speech. The ways in which voice can be integrated with the Web are nearly infinite. In addition, two distinctly different settings can benefit from VoIP. One consists of highly structured corporate sites, which can use VoIP Drupal for such typical bureaucratic tasks as offering interactive voice menus and routing customers to extensions. The other consists of sites serving underdeveloped areas, where people are more adept at using their phones than dealing with text-based Web sites. We need different pitches for each potential user.

Finally (and here my training as an editor pokes in), there are a number of different audiences who need to understand VoIP Drupal on different levels. Content providers need to understand what it can do and see models for incorporating it into their Drupal sites. Administrators need to understand how to find scripts and offer them to content providers. And programmers need to learn how to write fresh scripts. We also want to attract open source developers who could help enhance and maintain VoIP Drupal. There is even a tool called Visual VoIP Drupal that reduces the amount of programming skill required to create a new script pretty close to a minimum--that creates yet another audience.

Documentation needs

My goal in joining the informal VoiP Drupal promotion team was to use this project as a test case for exploring what software projects do for documentation, and how they could do better.

A number of sites have successfully implemented VoIP Drupal, some of them in quite sophisticated ways, but you could call these the alpha developers or early adopters. They managed, for instance, to find the reference documentation that requires several clicks to access, and which I did not notice for weeks. And needless to say, they required no other documentation, because the tutorials are extremely rudimentary.

I think that VoIP Drupal documentation is typical of early software projects--and in fact better than many. Projects tend to toss the reader a brief tutorial, provide some examples with inadequate explanatory text, and finally dunk the reader in the middle of an API reference. The tutorial tends to be fragile, in the sense that any problem encountered by the reader (a missing step, a change in environment) leaves her in an unrecoverable state, because there is no documentation about the way the system works and its assumptions. And the context for understanding reference documentation is missing, so that it can be used only by experienced developers who have seen similar programs in other environments.

Useful VoIP Drupal documentation includes (these are examples):

Our team knew that more descriptive text was needed to pull together these pieces, but whoever wrote a document would need some intensive time with a core developer. This was unfeasible in the rush to get the software in shape for DrupalCon. I found out about the difficulties of producing documents first-hand when I decided to tackle Visual VoIP Drupal, which looked simple and intuitive. Unfortunately, there were a lot of oddities in its behavior, and the simplicity of the interface didn't save me from having to know some of the subtler and less documented aspects of VoIP Drupal programming, such as handling input variables.

In a recent teleconference, I asked a bunch of preliminary questions and got a better idea of what documentation already covers, as well as a starting point for doing more documentation.

Current documentation tasks, in my opinion, include:

  • Expand the tutorials to show more of the capabilities of VoIP Drupal.

  • Provide explanations of key topics, such as different ways to handle voice input, keyboard input, and the metainformation provided by VoIP Drupal about each call. The developers' provision of a simple scripting system on top of PHP, and even more the creation of Visual VoIP Drupal, demonstrates their commitment to reaching non-programmers, but we have to follow through by filling in the background they lack.

  • Create a few videos or webinars on Visual VoIP Drupal.

  • Make links to the reference documentation more prominent, and link to it liberally in the tutorials and background documents. The use of doc strings from the code is reasonable for reference documentation, because nobody is asking it to look pretty and we want to maximize the probability that it will stay up to date.

  • Ask the community for examples and case studies, and describe what makes each one an interesting use of VoIP Drupal.

There's plenty that could be done, such as describing how to integrate VoIP Drupal into existing PHP code (and therefore more fully into existing Drupal pages) but that can be postponed. Leo said he's "particularly interested in working with Micky and the rest this group in the creation of a Visual VoIP Drupal webinar, and one about things we can do with VoIP Drupal right out of the box, with no or minimum programming."

What motivates people like Michele and me to put so much time into this project? Certainly, Michele wants to promote a project that she uses in her own work so that it thrives and continues to evolve. I can use what I learn from this work to provide services to other open source communities. But beyond all these individual rewards is a gut feeling that VoIP Drupal is cool. Using it is fun, and talking about it is also fun. Projects have achieved success for more light-weight reasons.

Cross-platform mobile development is a breeze with C#

Greg Shackles (@gshackles) is the author of "Mobile Development with C#," which is available for pre-order now and scheduled for release this spring.

During a recent interview, Shackles and I talked about C#'s role in the mobile space and coding best practices. Highlights from the discussion included:

  • Cross-platform mobile development is tough. The mature C# language is the only language that can be used across all of these platforms to produce a native experience. [Discussed at 00:03]


  • Reusing code is a must. Shackles thinks developers should try to separate business logic from user interface logic. [Discussed at 00:39]


  • Be on the watch for big enhancements when Windows Phone 8 is released, like near-field and app-to-app communications. [Discussed at 01:27]


  • Make an app that stands out by creating a really solid user experience. [Discussed at 02:45]

You can view the entire interview in the following video.

April 05 2012

Commerce Weekly: The do's and don'ts of geo marketing

Here's what caught my eye in the commerce space this week.

Placecast's CEO on the secret to successful targeted offers

PlacecastLast August, I wrote about Placecast, which has been working to deliver coupons and offers on behalf of its retail clients to opted-in customers when they hit geofenced areas. Placecast's platform allows merchants to set up a ring around their locations (or other locations, as described below) and then trigger an SMS to customers who have opted in to receive them. Placecast works with mobile carriers to deliver large tranches of opted-in customers to its merchant clients. This week at O'Reilly's Where Conference, Placecast CEO Alistair Goodman talked about the right and wrong way to deliver ads to a geofenced audience, based on the learning curve they have climbed over the past few years.

Some of these are obvious, like the need to link data about the customers' preferences with the location — the richer the data, the more relevant the message, and the more likely it is to hit home. Goodman explained this as a sort of stack, with positioning data (mostly from GPS, but supplemented with Wi-Fi and other data) at the lowest level. Just above that, a layer on context: What type of place is the user at (mall? stadium? park?) and what's the weather like? Atop that level, demographics and psychographics — who are the users and what do users in their consumer categories tend to go for? Atop that layer, the users' preferences: What do they want to be notified about, when, and how often? And finally, at the top of the stack, the offer itself: What is it the retailer is promoting?

A second key point is the need to find relevant locations — not just the retailer's store, which is obvious, but other places where the customer is likely to be receptive to the offers. For example, you might promote dog food or pet stores at a dog park, or a promo for a sports drink around a gym, or the sponsor of a concert around an arena. Interestingly, Goodman said that while merchants often ask Placecast to geofence around a competitor's store, he advises them that isn't a particularly effective marketing strategy: "If a customer is already headed into a certain store, a message urging them to visit a different location isn't likely to be very effective. A more effective way is to promote the message from a relevant public space." (I noticed the audience received this wisdom in total silence; you could almost hear the wheels of doubt spinning.)

Finally, Goodman said customers react better to offers when they believe it comes to them through this channel with some level of exclusivity. "Customers like it when they feel they're getting an offer that others aren't getting." So the coupons or other offers can't be the same as what's posted on the window of the store.

Goodman said the platform can deliver offers through a variety of channels, but most are delivered as SMS text messages, which remain tremendously effective. And they seem to be working: Goodman said that their research finds that 49% of store visits that occurred after receiving a Placecast ShopAlert were unplanned before the alert, while another 19% served as reminders to visit the store. In these cases, you might say those texts delivered twice.

X.commerce harnesses the technologies of eBay, PayPal and Magento to create the first end-to-end multi-channel commerce technology platform. Our vision is to enable merchants of every size, service providers and developers to thrive in a marketplace where in-store, online, mobile and social selling are all mission critical to business success. Learn more at x.com.

Jumping ship at Google Wallet?

Google WalletThe departure of Google Wallet co-founding engineer Rob von Behren to join payments startup Square aroused suspicion that Square might be looking to incorporate NFC in its system. Dan Balaban's article in NFC Times puts von Behren's departure in the context of a swath of high profile talent exits from a project that appears to be struggling to find partners and users. Balaban quotes a mobile commerce analyst who believes von Behren's joining Square almost certainly means a move by Square to support NFC. "Else, it would be like hiring Michael Jordan to get advice on golf," the analyst said.

In the past, Square's COO Keith Rabois has questioned the value of NFC, calling it, at last September's GigaOM Mobile Conference, "a technology in search of a value proposition." But as more mobile phones ship this year with the short-range wireless technology, it seems natural that Square would want to tap into it to facilitate its "Pay with Square" (formerly Card Case) system that allows customers to pay at merchants with their Square accounts.

Meanwhile, Balaban's article raises questions about the viability of the Google Wallet project. In addition to von Behren, fellow founding engineer Jonathan Wall and product lead Marc Freed-Finnegan left to start their own mobile-commerce startup, Tappmo, in March. Andrew Zaeske, former director of engineering for Wallet, is also said to have left the project. Speculation centers around disagreements between Wallet chief Osama Bedier (who joined Google from PayPal in February 2011) and other leaders of the team over the project's direction. It can't help that the refusal last autumn of Verizon to allow Google Wallet into its phones, and Verizon, AT&T, and T-Mobile's plans to launch their own mobile wallet under the Isis brand, cast into doubt whether Wallet will ever be able to expand beyond the Sprint network.

Will carriers like Facebook's post-IPO status?

Mobile carriers run the risk of losing text revenue from Facebook, as more of the service's users access it from mobile devices and use it as their primary communication channel. That's the view of Victor Basta, managing director of London-based Magister Advisors, which advises companies on acquisitions and public offerings. Basta told Bloomberg BusinessWeek that "Facebook's IPO is about the worst thing that could happen to network operators" since the pressure to demonstrate strong earnings to investors will make it harder for Facebook to share revenue with the carriers. Facebook's "over-the-top" service rides on the mobile networks, failing to share any of the revenue from advertising delivered over it and increasingly taking away from the carriers' SMS text earnings, as users send free Facebook messages instead.

"The fundamental challenge for network operators will be finding a way of becoming part of the Facebook ecosystem rather than simply external enablers," Basta said.

Tip us off

News tips and suggestions are always welcome, so please send them along.


If you're interested in learning more about the commerce space, check out DevZone on x.com, a collaboration between O'Reilly and X.commerce.


Related:

March 30 2012

Patterns snap mobile app designs into place

In the following interview, "Mobile Design Pattern Gallery" author Theresa Neil (@theresaneil) discusses interface design trends, the one app design mistake that pops up again and again, and the apps that get UI right.

What are the most interesting trends you're seeing in mobile interface design?

Theresa Neil: I'm most interested in the trends that arise when app makers try to address a cross-device design strategy. For example, the Springboard pattern — a grid of icons acting as a launchpad — is a popular navigation pattern since it is "OS neutral." Meaning, it doesn't rely on bottom tabs like iOS and BlackBerry, or on top tabs like Android, Windows Mobile and Symbian. The Springboard pattern can be easily adapted for each operating system without feeling foreign or weird to the user.

Sprinboard design pattern
The Springboard design pattern features a single page with multiple menu options. This pattern works well across mobile operating systems. (Screenshot from "Mobile Design Pattern Gallery.")

Your book includes UI "anti-patterns." What are those?

Theresa Neil: Anti-patterns are examples of mobile UI design patterns to avoid. Bill Scott, my co-author of "Designing Web Interfaces," has had a popular talk for many years featuring anti-patterns in web applications. We could just write off these examples as bad designs, but I think it is important to dig into them and figure out why they are bad.

What is the most common mobile UI mistake?

Theresa Neil: Anti-pattern no. 1 is "novel notions." Novel notions refer to designs that use a "novel" approach to a problem that could otherwise be solved with an existing pattern, a standard UI control, or a better metaphor.

This is not to say designers should dial back their creativity. Apps like Flipboard, Path and Clear have blazed a trail with novel solutions to navigation. But novel designs need to be rigorously tested and refined before being released. Just look at the reviews in the App Store: For every awesome app like Path, there are dozens of other apps that are rated one star for bad navigation or a confusing interface.

Which mobile apps have notable UI design?

Theresa Neil: Flipboard, Path, Clear — the typical superstars. But I also love Evernote, Trip Journal, Foursquare and Fring because these companies have done spectacular work with their app design strategies. For example, look at Foursquare on a BlackBerry, iPhone or a Windows 7 phone; the apps are optimized for each of the different operating systems, but they still feel like the same app.

Mobile Design Pattern Gallery — This book provides a reference to 70 mobile app design patterns, illustrated by more than 400 screenshots from current iOS, Android, BlackBerry, WebOS, Windows Mobile, and Symbian apps.

This interview was edited and condensed.

Related:

Reposted byRKidoitforthelulz

March 29 2012

Commerce Weekly: Google Wallet vs Isis is coming soon

Here's what caught my eye in commerce news this week.

Who's got the winning wallet?

Several recent articles have speculated about the coming competition between Google Wallet and the forthcoming mobile wallet from Isis, which is set to debut in tests in Austin and Salt Lake City this summer. Tech bloggers love a contest, and even though there's only one major player in this race so far, observers are handicapping the players before they even take the field.

MobilePaymentsToday.com ran a column comparing the merits of the two platforms in several categories. (Where was the massive infographic that we've all grown used to for this sort of thing?) Google took the prize in time-to-market (already out there, a little) and branding, while the nod went to Isis for building a solid ecosystem, with its support from three major U.S. wireless carriers and the top credit card networks and handset builders. Isis should also get the award for most imaginative and compelling demo video, based on the clip of Cyber Illusionist Marco Tempest at SXSW a few weeks ago (demo begins 15 seconds in, after the ad):



Of course, both of these plays depend on NFC wireless capability in phones, and while that's destined to ramp up soon, GigaOm reported that in 2011, NFC in the U.S. lagged far behind other regions. Of the 30 million NFC-capable handsets sold worldwide last year, about five million went to North America, 10 million went to Europe, and more than that went to Asia. Some mobile wallets, of course, don't rely on NFC: PayPal, for example, is getting ready to launch an updated version of its wallet that operates closer to the direct billing model, where you enter your mobile number on the retailer's keypad and then confirm when a text is sent to your mobile. PayPal's system is a bit less elegant than wireless tap and pay, but as we wrote a few weeks ago, it's ready now and available on any phone that supports texting.



We couldn't help notice that all this handicapping of the two most visible mobile wallets overlooked the potential of a third player that has yet to enter the arena. Only a few weeks ago, mobile payment geeks were abuzz about newly published patents from Apple that described a method for payment with credit cards that sends the receipt to the user's iTunes account. And since there are more than 200 million of those iTunes accounts (and 350 million iOS devices out there), that represents a significant installed user base that may be receptive to Apple's familiar interface applied to a mobile wallet. Those who think Apple is coming late to the party should be reminded that Apple has never had to be the first to a market to end up dominating it.

X.commerce harnesses the technologies of eBay, PayPal and Magento to create the first end-to-end multi-channel commerce technology platform. Our vision is to enable merchants of every size, service providers and developers to thrive in a marketplace where in-store, online, mobile and social selling are all mission critical to business success. Learn more at x.com.

In-app purchases continue to dominate

In-app purchase screenshotHere's more evidence that in-app purchases are driving most of the revenues in mobile apps. According to Inside Mobile Apps, Distimo, which specializes in tracking app store activity, reports that a majority of the top-grossing apps on iPad, iPhone and Android monetize with in-app purchases. The researcher found that, of the top 200 grossing apps in the iPad App Store, the iPhone App store, and the Google Play store in February, 74% of the iPad apps and 80% of the iPhone apps featured in-app purchases. The numbers are even more remarkable when taken with the additional insight that only 10% of all iPad apps and 6% of iPhone apps even offer in-app purchases. So, there appears to be an awful lot of iOS apps that aren't yet interested in playing in the winning game.

The number was lower on Android apps (56%). Inside Mobile Apps' Kathleen De Vere suggested that may be because Android has a shorter history with in-app purchases (only since last May) and, related, fewer Android apps offer in-app purchases.

The findings support other reports that have also suggested the superiority of the foot-in-the-door model, including one by Flurry Analytics last summer that found freemium emerging as the dominant model for generating revenue from mobile apps.

Tip us off

News tips and suggestions are always welcome, so please send them along.


If you're interested in learning more about the commerce space, check out DevZone on x.com, a collaboration between O'Reilly and X.commerce.


Related:

March 23 2012

Publishing News: Ereading on a landing plane

Though I wasted a good deal of time this week mesmerized by the Daily Dispatches from the Internet's Worst Reviewers website (hat tip to Joe Wikert and Kat Meyer), there were a few publishing stories that still caught my eye.

Tray tables must be upright, but (hopefully soon) you can leave your iPads on

ereaders.jpgIn December, the FAA approved iPad use for pilots in cockpits during takeoff and landing, but not for passengers. According to a post by Nick Bilton at the New York Times, the FAA decided this week that it may be time to bring passengers into the 21st century as well. Bilton reported the last time the FAA tested gadgets for approval was 2006 — and that testing requires a much greater time and expense investment than one might think:

"Abby Lunardini, vice president of corporate communications at Virgin America, explained that the current guidelines require that an airline must test each version of a single device before it can be approved by the FAA. For example, if the airline wanted to get approval for the iPad, it would have to test the first iPad, iPad 2 and the new iPad, each on a separate flight, with no passengers on the plane.

"It would have to do the same for every version of the Kindle. It would have to do it for every different model of plane in its fleet. And American, JetBlue, United, Air Wisconsin, etc., would have to do the same thing."

Bilton offered a reasonable solution to the time/cost problem: Each airline could offer up one plane, one day per month throughout testing and the bill would be sent to the device manufacturers that want devices approved — if you don't pony up, your device doesn't get tested. In any case, I look forward to not being scolded next time I forget the book I'm engrossed in needs to be shut off.

Mini TOC Chicago — Being held April 9, Mini TOC Chicago is a one-day event focusing on Chicago's thriving publishing, tech, and bookish-arts community.

Register to attend Mini TOC Chicago

If you're not selling direct, you're not getting all the data

Joe Wikert (@jwikert), GM and publisher at O'Reilly, took a look at the availability of publishing data this week. He argued that direct sales channels are worth the investment for publishers because when you sell directly to consumers, you have access to the entire data stream.

For example, O'Reilly recently conducted an ereader survey through its direct sales channel, and Wikert shared the results:

"So, what's the primary ereading device used by these early adopters and techno-enthusiasts? Their iPads. That's not shocking, but what's interesting is how only 25% of respondents said the iPad is their primary device. A whopping 46% said their laptop or desktop computer was their primary ereading device."

He also noted that among O'Reilly customers, the popular EPUB and Mobi formats were topped by PDF as the primary ereading format. This sort of information, Wikert argued, isn't likely to be transparent when you're relying on a third-party intermediary with an agenda. You can read his post here. And if you want more stats from the survey, Wikert tweeted them with the #ORMeStat hashtag.

One word for news: "Mobile"

The State of the News Media 2012, the annual report on American journalism from the Pew's Project for Excellence in Journalism, was released this week.

Overall trends uncovered in the study include a lack of social media influence — "the notion that large percentages of Americans now get their news mainly from recommendations from friends does not hold up" — and highlight the fact that privacy concerns are becoming a major issue for news revenues:

"To survive, news must find a way to make its digital advertising more effective — and more lucrative — and the gathering of consumer data is probably the key. Yet news organizations also must worry about violating the trust of their audiences."

Trends showed mobile is proving to be very important for news:

"... mobile news consumers are even more likely to turn to news organizations directly, through apps and home pages, rather than search or recommendations — strengthening the bond with traditional brands."

Technology may be more foe than friend, however. Though the study found that mobile technology is giving news consumption a boost (27% of Americans now get news on mobile devices), a study of the money shows that tech companies may be edging out traditional news channels:

"In 2011, five technology giants generated 68% of all digital ad revenue, according to the market research firm eMarketer — and that does not include Amazon and Apple, which make their money from devices and downloads. By 2015, roughly one out of every five display ad dollars is expected to go to Facebook, according to the same source ... 'Our analysis suggests that news is becoming a more important and pervasive part of people's lives,' PEJ Director Tom Rosenstiel said. 'But it remains unclear who will benefit economically from this growing appetite for news.'"

Full study results can be found here.

Got news?

Suggestions are always welcome, so feel free to send along your news scoops and ideas.

Photo: Evolution of Readers by jblyberg, on Flickr

Related:

March 21 2012

Four questions about Microsoft with Mary Jo Foley

Mary Jo Foley (@maryjofoley) is the author of the "All About Microsoft" column at ZDNet . She does a great job at keeping people informed about the world of Microsoft and she wrote a book herself not so long ago titled "Microsoft 2.0: How Microsoft Plans to Stay Relevant in the Post-Gates Era."

I recently interviewed Foley about a number of Microsoft's moves. Highlights from our discussion included:

  • Foley sees vertical opportunities for the Kinect SDK for Windows, from health care to education. Integrating the Kinect technology will also play a part in interacting with PowerPoint, ERPs and CRMs. [Discussed
    10 seconds in
    .]
  • How has the rollout for Windows 8 been different from previous operating systems? "Beta" doesn't mean what it used to — Google, for example, has many products in perpetual beta — but Foley thinks there's more to the Windows 8 release than just that. The Windows 8 rollout is a signal of how Microsoft develops the OS now, with the company setting things in stone earlier than with previous software products. [Discussed at 2:41.]
  • If you think Microsoft will loosen its grip on Metro design guidelines, think again. Foley pointed to Windows on ARM (WOA) as an example — there, Metro is the only choice. [Discussed at 4:39.]
  • What would someone choose a Windows 8 tablet over an iPad or Android tablet? Foley said the competitive difference may lie in sleeker hardware and integration with Microsoft's Office suite.
    [Discussed at href="http://www.youtube.com/watch?v=ODyKeX3x9C0#t=6m16s">6:16.]

You can view the entire interview in the following video.

March 12 2012

Understanding place and space in a decreasingly English world

I'm So Confused! by Ian Sane, on FlickrRobert Munro (@WWRob) is a graduate fellow at Stanford University and chief executive at Ibidon who's fascinated with languages that are spoken by very few. At Where 2012, Munro will examine differences in how people express place, distance, and space among the world's 5,000-plus languages. These are differences that location-aware app designers will have to pay attention to as the world's data becomes less and less predominantly English.

Our interview follows.

What are some of the ways that space and direction are expressed differently among cultures?

Robert Munro: We tend to think of spatial distinctions as absolute and clean-cut, but when you scratch the surface, it is clear that we encode space and direction in many very subtle and language-specific ways. If I said, "look in front of the house," do I mean "in front of" relative to you, me, or the house itself? Or if we've been looking at an aerial map together, maybe I just mean to the north, south, or roadside.

Even in English, location can be difficult to embed into technology. If you ride the light rail in Portland, Ore., you might hear an ethereal voice saying, "The doors on my right side will open." Is this the (somewhat creepy) disembodied voice from the train that you are inside, meaning the doors on the right in the direction of travel? Is it from the virtual driver facing the passengers, meaning the doors on the left in the direction of travel? Portland recently hosted the annual conference of America's top linguists; even they had to wait for the train to stop to figure it out.

Why are these differences important for geo developers to consider?

Robert Munro: The majority of the world's digital information is now in non-English unstructured text. There are some 5,000 languages in the connected world, each of them spoken by people operating potentially location-aware devices.

The location-based applications on those devices are abstracted from space, time and direction, using visual and verbal metaphors for each. Every language encodes space and time differently and there is a direct relationship between visual spatial metaphors and language. Recent research has found this link to be much stronger than once thought — even short-term changes in language can drastically alter the way we perceive space and time. For some languages, the future is in front of us, but for others it is behind us. Some languages use length is a metaphor for time (a long time) while some prefer volume (a large amount of time). Some languages will prefer relative directions (turn left) while others will only permit absolute directions (turn north). Location-based applications use every one of these metaphors, so it is important for developers to understand the rich breadth of spatial and temporal metaphors that they are (often unconsciously) coding into their applications. As the applications often have a visual language of their own, it is safe to say that they can also have a direct influence on their users' sense of space and time. After staring at a map before exploring some new place, did you ever feel like you then had an augmented reality view of the place thanks to that map? In a sense, you probably did.


Can you tell us about the work you did after the Haiti earthquake to crowdsource local information from a global diaspora of Haitians?

Robert MunroRobert Munro: Mission 4636 was a crowdsourced information service established in the wake of the 2010 earthquake in Haiti. People within the country were able to send free text messages that were then translated and mapped by crowdsourced workers and streamed back to responders within the country. We launched in 48 hours. I ran the actual crowdsourcing component — finding and managing thousands of Haitian Kreyol and French speakers globally who could help.

It taught me two important lessons. The first is that nothing beats local knowledge. Members of the Haitian diaspora thousands of miles away were quicker at geolocating vital locations in Haiti than many international workers on the ground. The second lesson that it taught me is that it is hard to find those who have the crucial local knowledge. At the time, I needed to reach out through social media, looking for (mostly) ad-hoc groups of people with Haitian affiliations. There simply wasn't a unified resource that links people by languages spoken.

This has influenced me greatly. For every corner of the world, there is a global network of largely untapped local knowledge, and it is just as applicable to travel and trade as it is to crisis response. It gives us one solution to the problem of encoding location in technology. For a given problem, there is probably someone online right now who does have the necessary local linguistic and geographic knowledge. In addition to making technology smarter across languages, we also need to be making technology that can better engage these individuals. With Idibon, we are doing both, building language-processing algorithms that can parse unstructured data in previously unknown languages and linking this to a global network of language speakers. In Haiti, we were able to transfer the system to local, paid workers within the country, continuing the local knowledge and providing employment where it was needed most. I would love to see this kind of approach adapted more broadly, turning people's knowledge of less well-known languages to their advantage.

Where Conference 2012 — O'Reilly's Where Conference, being held April 2-4 in San Francisco, is where the people working on and using location technologies explore emerging trends in software development, tools, business strategies and marketing.

Save 20% on registration with the code RADAR20

How is location used in viral forecasting by health organizations?

Robert Munro: Location is the oldest and newest component in viral forecasting. In the 1850s, John Snow founded both modern epidemiology and geographic information systems (GIS) when he mapped the location of a London cholera outbreak to a single water pump.

Today, unfortunately, the dynamic maps that you see in outbreak movies outpace the technologies of actual epidemic-tracking organizations. But this is rapidly changing on the back of communication technologies. While HIV took decades to be isolated, Bird Flu and Swine Flu were isolated weeks or months after they first appeared. We can go back and find early, open reports about Bird Flu and Swine Flu with the key signatures of a new virus. This could have enabled us to identify and contain them even earlier, and smarter information processing will allow this for future outbreaks. Within Global Viral Forecasting, a spin-in called epidemicIQ is doing just this, looking to track outbreaks as early as possible. (Disclosure: I was the CTO of epidemicIQ until recently and continue as an adviser.) Local knowledge is vital here, too: 90% of the world's outbreaks come from 10% of the land; 90% of the world's languages also come from 10% of the land. It is the same 10%.

Geographic information systems are finding their way back into real-time outbreak tracking, too. Open data about flight paths and transportation networks allows us to track the potential spread of an outbreak with a precision that was never before possible. At the moment, we are quickly closing the gap on how quickly we can track the spread of outbreaks. Will we soon be able to use the same technology to get ahead of outbreaks? I hope so.

Who else is doing interesting work in this area?

Robert Munro: For almost half a century, most language researchers assumed that the cross-language differences in space and time were more or less arbitrary. Within the last few years, a number of researchers, the Stanford psychologist Lera Boroditsky in particular, have produced strong evidence showing that they can manipulate people's sense of time and space by changing their language, even over very short periods. It has turned many people's assumptions about language and world-view right around.

In health, Nicholas A. Christakis at Harvard and James Fowler at the University of California San Diego have made some very interesting discoveries about the spread of disease, using online social networks as a powerful stand-in for geographic/interpersonal connections. They have been able to make reliable predictions about the spread of outbreaks and other communicable phenomena to several people out along social networks. It is a really exciting new approach.

This interview was edited and condensed. Photo: I'm So Confused! by Ian Sane, on Flickr

Related:

March 08 2012

Commerce Weekly: An app to end tab walkouts

Here are the commerce stories that caught my attention this week.

Tabbed Out connects check-ins with payment

For every one of us who's ever had a hard time catching the server's eye so we can make a hasty exit from the bar, here's the app you've been waiting for. Tabbed Out (available on Android and iOS) lets you check in and open a tab at restaurants and bars. When you set up the app, you link your credit card to it, so checking in delivers that info to the merchant's point-of-sale system. When you want to check out, you can do it on the app, even leaving the tip there instead of on the wet table. That's good for the merchant: There's no chance of getting walked out on, even if the patron leaves in a hurry or deletes the app.

Tabbed Out screens

It's also good for the patron: Not only does it allow you to flee when the urge strikes, but it might save you a trip back the next day. Every bar has a drawer full of abandoned credit cards, tabs opened by good-spirited folks early in the evening who, by the time they left, were too tipsy to remember to collect them on the way out. Do the same with Tabbed Out and the merchant can close the tab — and you don't have to return to the bar the next day to pick up your plastic.

The app offers some of the usual benefits we've grown to expect from a mobile check-in app — allow it to know your location, and it will also tell you what's nearby. Well, eventually it will. As of this week, it's only available at 450 locations in 34 states. Starting this weekend, some of those locations (the ones in Austin, Texas) will begin accepting PayPal as a payment option, too. A spokesperson for Tabbed Out says the company plans to make the PayPal option part of its standard offerings as it continues to roll out nationwide. So, this is another foothold for PayPal in the real world: Now you can use it to charge supplies at Home Depot, then pay for that brew you buy to reward yourself at the end of the day.

X.commerce harnesses the technologies of eBay, PayPal and Magento to create the first end-to-end multi-channel commerce technology platform. Our vision is to enable merchants of every size, service providers and developers to thrive in a marketplace where in-store, online, mobile and social selling are all mission critical to business success. Learn more at x.com.

Square coming to NYC taxis

An iPad using Square as a cash register Square's back in the news this week, with an upgraded cash register app (timed to coincide with the new iPad announcement) and more details on its rollout to New York City taxis. The iPad cash register isn't exactly new: Square has been pushing it for more than a year, and Cult Of Mac did a nice little round up of nifty iPad holders back in January 2011. But the company has relaunched the app and its integration with Card Case, the buyer's app that lets you run a tab using just your name at Square-accepting retailers (if you can find one).

Bigger news may be that, as The New York Times reports, Square will begin a pilot program in 30 NYC taxi cabs, with iPads mounted where those little TVs are now. (They better bolt them in pretty good!) The big innovation here, at least for the rider, is that you can swipe your card anytime during the ride. Then just sign the screen with your finger and you can hop right out at your destination; no more waiting to sign a credit-card receipt. Cabbies get something out of it too — faster payments and a silent iPad instead of a noisy TV with looped audio.

Despite these innovations, anyone who's been excited watching Square's development has probably also felt the disappointment that goes along with not seeing it used … well, just about anywhere. Dan Frommer, the tech journalist who blogs his own news at SplatF, certainly feels that disappointment. Still, he's enough of an enthusiast to review the company's releases over the past year of its daily processing volumes. While they're still a drop in the ocean compared to more visible options, like credit cards and even PayPal, Square seems to be headed in the right direction, and on a steepening curve that has reached $11 million a day. Considering the few businesses that show up on my Card Case app right now, that's an impressive number of lattes, massages, and farm-fresh produce.

iWallet is coming

While the rest of the Apple-lovin' world focused on the details of the new retina-display 4G iPad, payment geeks were poring over the details of a patent released Tuesday describing features of a mobile wallet to be used in some future version of the iPhone. Patently Apple reported that, while we've seen a number of patents published over the past year dealing with NFC communication and transactions, this patent details credit-card transaction rules, including a note that credit card companies will send statements (or at least receipts) directly to a buyer's iTunes account. "The iWallet project just became a little more real today," PatentlyApple noted.


Tip us off

News tips and suggestions are always welcome, so please send them along.


If you're interested in learning more about the commerce space, check out DevZone on x.com, a collaboration between O'Reilly and X.commerce.


Related:

Reposted byRK RK

March 07 2012

Buttons were an inspired UI hack, but now we've got better options

If you've ever seen a child interact with an iPad, you've seen the power of the touch interface in action. Is this a sign of what's to come — will we be touching and swiping screens rather tapping buttons? I reached out to Josh Clark (@globalmoxie), founder of Global Moxie and author of "Tapworthy," to get his thoughts on the future of touch and computer interaction, and whether or not buttons face extinction.

Clark says a touch-based UI is more intuitive to the way we think and act in the world. He also says touch is just the beginning — speech, facial expression, and physical gestures are on they way, and we need to start thinking about content in these contexts.

Clark will expand on these ideas at Mini TOC Austin on March 9 in Austin, Texas.

Our interview follows.

Are we close to seeing the end of buttons?

josh_clark.pngJosh Clark: I frequently say that buttons are a hack, and people sometimes take that the wrong way. I don't mean it in a particularly negative way. I think buttons are an inspired hack, a workaround that we've needed just to get stuff done. That's true in the real world as well as the virtual: A light switch over here to turn on a light over there isn't especially intuitive, and it's something that has to be learned, and re-learned for every room we walk into. That light switch introduces a middle man, a layer of separation between the action and the thing you really want to work on, which is the light. The switch is a hack, but a brilliant one because it's just not practical to climb up a ladder in a dark room to screw in the light bulb.

Buttons in interfaces are a similar kind of hack — an abstraction we've needed to make the desktop interface work for 30 years. The cursor, the mouse, buttons, tabs, menus ... these are all prosthetics we've been using to wrangle content and information.

With touchscreen interfaces, though, designers can create the illusion of acting on information and content directly, manipulating it like a physical object that you can touch and stretch and drag and nudge. Those interactions tickle our brains in different ways from how traditional interfaces work because we don't have to process that middle layer of UI conventions. We can just touch the content directly in many cases. It's a great way to help cut through complexity.

The result is so much more intuitive, so much more natural to the way we think and act in the world. The proof is how quickly people with no computing experience — people like toddlers and seniors — take so quickly to the iPad. They're actually better with these interfaces than the rest of us because they aren't poisoned by 30 years of desktop interface conventions. Follow the toddlers; they're better at it than we are.

So, yes, in some contexts, buttons and other administrative debris of the traditional interface have run their course. But buttons remain useful in some contexts, especially for more abstract tasks that aren't easily represented physically. The keyboard is a great example, as are actions like "send to Twitter," which don't have readily obvious physical components. And just as important, buttons are labeled with clear calls to action. As we turn the corner into popularizing touch interactions, buttons will still have a place.

Mini TOC Austin — Being held March 9, 2012 — right before SXSW — O'Reilly Tools of Change presents Mini TOC Austin, a one-day event focusing on Austin's thriving publishing, tech, and bookish-arts community.

Register to attend Mini TOC Austin

What kinds of issues do touch- and gesture-oriented interfaces present?

Josh Clark: There are issues for both designers and users. In general, if a touchscreen element looks or behaves like a physical object, people will try to interact with it like one. If your interface looks like a book, people will try to turn its pages. For centuries, designers have dressed up their designs to look like physical objects, but that's always just been eye candy in the past. With touch, users approach those designs very differently; they're promises about how the interface works. So designers have to be careful to deliver on those promises. Don't make your interface look like a book, for example, if it really works through desktop-like buttons. (I'm looking at you, Contacts app for iPad.)

So, you can create really intuitive interfaces by making them look or behave like physical objects. That doesn't mean that everything has to look just like a real-world object. Windows Phone and the forthcoming Windows 8 interface, for example, use a very flat tile-like metaphor. It doesn't look like a 3-D gadget or artifact, but it does behave with real-world physics. It's easy to figure out how to slide and work the content on the screen. People figure that stuff out really quickly.

The next hurdle — and the big opportunity for touch interfaces — is moving to more abstract gestures: two- and three-finger swipes, a full-hand pinch, and so on. In those cases, gestures become the keyboard shortcuts of touch and begin to let you create applications that you play more than you use, almost like an instrument. But wait, here I am talking about abstract gestures; didn't I just say that abstractions — like buttons — are less than ideal? Well, yeah, the trouble is you don't want to have the overhead of processing an interface, of thinking through how it works. The thing about physical abstractions (like gestures) versus visual abstractions (like buttons) is that physical actions can be absorbed into muscle memory. That kind of subconscious knowledge is actually much faster than visual processing — it's why touch typists are so much faster than people who visually peck at the keys. So, once you learn and absorb those physical actions — a two-finger swipe always does this or that — then you can actually move really quickly through an interface in the same way a pianist or a typist moves through a keyboard. Intent fluidly translated to action.

But how do you teach that stuff? Swiping a card, pinching a map, or tapping a photo are all based on actions we know from the physical world. But a two-finger swipe has no prior meaning. It's not something we'll guess. Gestures are invisible with no labels, so that means they have to be taught.

Screenshot from Apple's built-in trackpad tutorial
Screenshot from Apple's trackpad tutorial.

In what ways can UI design alleviate these learning issues?

Josh Clark: Designers should approach this by thinking through how we learn any physical action in the real world: observation of visual cues, demonstration, and practice. Too often, designers fall back on instruction manuals (iPad apps that open with a big screen of gesture diagrams) or screencasts. Neither are very effective.

Instead, designers have to do a better job of coaching people in context, showing our audiences how and when to use a gesture in the moment. More of us need to study video game design because games are great at this. In so many video games, you're dropped into a world where you don't even know what your goal is, let alone what you're capable of or what obstacles you might encounter. The game rides along with you, tracking your progress, taking note of what you've encountered and what you haven't, and giving in-context instruction, tips, and demonstrations as you go. That's what more apps and websites should do. Don't wait for people to somehow find a hidden gesture shortcut; tell people about it when they need it. Show an animation of the gesture and wait for them to copy it. Demonstration and practice — that's how we learn all physical actions, from playing an instrument to learning a tennis serve.

How do you see computer interaction evolving?

Josh Clark: It's a really exciting time for interaction design because so many new technologies are becoming mature and affordable. Touch got there a few years ago. Speech is just now arriving. Computer vision with face recognition and gesture recognition like Kinect are coming along. So, we have all these areas where computers are learning to understand our particularly human forms of communication.

In the past, we had to learn to act and think like the machine. At the command line, we had to write in the computer's language, not our own. The desktop graphical user interface was a big step forward in making things more humane through visuals, but it was still oriented around how computers saw the world, not humans. When you consider the additions of touch, speech, facial expression, and physical gesture, you have nearly the whole range of human (and humane) communication tools. As computers learn the subtleties of those expressions, our interfaces can become more human and more intuitive, too.

Touchscreens are leading this charge for now, but touch isn't appropriate in every context. Speech is obviously great for the car, for walking, for any context where you need your eyes elsewhere. We're going to see interfaces that use these different modes of communication in context-appropriate combinations. But that means we have to start thinking hard about how our content works in all these different contexts. So many are struggling just to figure out how to make the content adapt to a smaller screen. How about how your content sounds when spoken? How about when it can be touched, or how it should respond to physical gestures or facial expressions? There's lots of work ahead.

Are Google's rumored heads-up-display glasses a sign of things to come?

Josh Clark: I'm sure that all kinds of new displays will have a role in the digital future. I'm not especially clever about figuring out which technology will be a huge hit. If someone had told me five years ago that the immediate future would be all about a glass phone with no buttons, I'd have said they were nuts. I think both software and context and, above all, human empathy make the difference in how and when a hardware technology becomes truly useful. The stuff I've seen of the heads-up-display glasses seems a bit awkward and unnatural. The twitchy way you have to move your head to navigate the screen seems to ask you to behave a little robot-like. I think trends and expectations are moving in an opposite direction — technology that adapts to human means of expression, not humans adapting to technology.

This interview was edited and condensed.

Related:

Older posts are this way If this message doesn't go away, click anywhere on the page to continue loading posts.
Could not load more posts
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
Just a second, loading more posts...
You've reached the end.