Inbiza Labs

The thin edge of the mobile money wedge: NFC

May 11th, 2010

This year at the CTIA Wireless 2010 conference in Las Vegas I attended a seminar on mobile money. The overarching theme of the seminar was the desire to break the payment duopoly of VISA and MasterCard and the technology required to facilitate this. A consensus emerged that micro-payment was the thin edge of the wedge for breaking the duopoly and Near Field Communication (NFC) is the champion technology to deliver this.

Micro-payment is generally understood as a transaction under $10 that is primarily used for “convenience purchases”. Ten-dollars is the magic number because it marks the threshold below which consumers will make spontaneous purchases and because it is not risky for underwriting purposes. In addition, people generally do not begrudge paying a small fee for the convenience. For example, most people faced with a situation where they didn’t have change to plug a parking meter would be willing to pay a $0.30 transaction fee for $3.00 worth of parking rather than risk getting a $45.00 ticket. The best example – and the proverbial `killer app’ for micro-payment – is transportation ticketing. It’s worth mentioning that both the parking industry and transit authorities recognize these opportunities and are working to capitalize on them.

The mechanism used to deliver micro-payment capabilities to the end users is contact-less technology integrated into a mobile phone – specifically, Near Field Communication enabled smart phones. NFC has been the next-big-thing in this industry for years; however, the consensus at the mobile money seminars was that the technology would gain traction in the late 2010s. This is, in no small part, attributed to a commitment by VIVOtech and Nokia to get the technology to both the merchant (through the VIVOtech terminal) and the customer (through the mobile phone); this solves the chicken-and-egg problem that has been plaguing the industry for years. Apple has also staked a claim to NFC based on some recent patent applications. NFC is absolutely essential to mobile money because it provides everyone with a common, standardized technology to work with. Without it, the convenience factor would evaporate and customers would face the nightmare of different smart cards for every application from ticketing and parking to loyalty programs.

So what does this mean to you, your business, and your mobile app? It means that right now is the time to be strategizing about how you are going to leverage NFC for your payment solution, your loyalty program, or your coupon/marketing campaign. If you don’t use NFC, mobile money will blaze in on the next iPhone release and you will not only be scrambling to understand mobile-money, but frantic to regain a competitive advantage and implement NFC.

Going Git

December 27th, 2009

I was never a big fan of distributed source code management – I was perfectly happy delivering our projects through Subversion. Then, shortly after our TransDrive project was completed, we went to the 2009 Qt Developer Days conference and my opinions changed. Our client asked for some last minute changes and what followed was no surprise – Murphy’s law taught me something the hard way.

My source code was out of sync on my laptop, and, due to high US data roaming rates, I could not tether to sync it with the main server. We went straight to our flight where I spent several hours being less productive than I would have liked. On the second day of the conference, the Internet connection flaked out and I could not sync with the main server; once again, I was not as productive as I could have been.

When we returned from the trip I promptly started researching distributed source code management (DSCM). What I learnt from my research is this: All the main DSCM applications are more-or-less the same and the differences that do exist are more important to the developer’s workflow than the application’s technical merit. While we love and use Python regularly, out of Mercurial and git we went with the latter. After much reading and testing git and Mercurial we eventually settled on git for a few reasons:

  • Used by projects we are heavily dependant on: Qt and Linux;
  • Branching and merging techniques align with our workflow;
  • Great Linux and OS X support;
  • Very good Subversion integration.

For me, the second and last points were key. The branching and merging in git worked according to my beliefs and workflow and was therefore a natural transition for me. The last point is important because we need to continue work on TransDrive and thus integrate with Subversion.

The take away points here are: Expect the best but prepare for the worst – don’t let technical issues block your business. The second point is to go with what’s right for you – don’t decide on software because of trivial technical differences.

Website goes live

December 24th, 2009

Exciting times! Inbiza’s website goes live. Thanks to everyone who helped us out, and a special thanks to freshmark for a job well done.

-->