Yo! Minimalist Notifications, API and the Internet of Things

Yo LogoThought it was a joke, but having 4 hours of code resulting in $1m of VC funding, at an estimated $10M company valuation, raised quite a few eyebrows. The Yo! project team have now released their API, and with it some possibilities – over and above the initial ability to just say “Yo!” to a friend. At the time he provided some of the funds, John Borthwick of Betaworks said that there is a future of delivering binary status updates, or even commands to objects to throw an on/off switch remotely (blog post here). The first green shoots are now appearing.

The main enhancement is the ability to carry a payload with the Yo!, such as a URL. Hence your Yo!, when received, can be used to invoke an application or web page with a bookmark already put in place. That facilitates a notification, which is effectively guaranteed to have arrived, to say “look at this”. Probably extensible to all sorts of other tasks.

The other big change is the provision of an API, which allows anyone to create a Yo! list of people to notify against a defined name. So, in theory, I could create a virtual user called “IANWARING-SIMPLICITY-SELLS”, and to publicise that to my blog audience. If any user wants to subscribe, they just send a “Yo!” to that user, and bingo, they are subscribed and it is listed (as another contact) on their phone handset. If I then release a new blog post, I can use a couple of lines of Javascript or PHP to send the notification to the whole subscriber base, carrying the URL of the new post; one key press to view. If anyone wants to unsubscribe, they just drop the username on their handset, and the subscriber list updates.

Other applications described include:

  • Getting a Yo! when a FedEx package is on it’s way
  • Getting a Yo! when your favourite sports team scores – “Yo us at ASTONVILLA and we’ll Yo when we score a goal!
  • Getting a Yo! when someone famous you follow tweets or posts to Instagram
  • Breaking News from a trusted source
  • Tell me when this product comes into stock at my local retailer
  • To see if there are rental bicycles available near to you (it can Yo! you back)
  • You receive a payment on PayPal
  • To be told when it starts raining in a specific town
  • Your stocks positions go up or down by a specific percentage
  • Tell me when my wife arrives safely at work, or our kids at their travel destination

but I guess there are other “Internet of Things” applications to switch on home lights, open garage doors, switch on (or turn off) the oven. Or to Yo! you if your front door has opened unexpectedly (carrying a link to the picture of who’s there?). Simple one click subscriptions. So, an extra way to operate Apple HomeKit (which today controls home appliance networks only through Siri voice control).

Early users are showing simple Restful URLs and http GET/POSTs to trigger events to the Yo! API. I’ve also seen someone say that it will work with CoPA (Constrained Application Protocol), a lightweight protocol stack suitable for use within simple electronic devices.

Hence, notifications that are implemented easily and over which you have total control. Something Apple appear to be anal about, particularly in a future world where you’ll be walking past low energy bluetooth beacons in retail settings every few yards. Your appetite to be handed notifications will degrade quickly with volumes if there are virtual attention beggars every few paces. Apple have been locking down access to their iBeacon licensees to limit the chance of this happening.

With the Yo! API, the first of many notification services (alongside Google Now, and Apples own notification services), and a simple one at that. One that can be mixed with IFTTT (if this, then that), a simple web based logic and task action system also produced by Betaworks. And which may well be accessible directly from embedded electronics around us.

The one remaining puzzle is how the authors will be able to monetise their work (their main asset is an idea of the type and frequency of notifications you welcome receiving, and that you seek). Still a bit short of Google’s core business (which historically was to monetise purchase intentions) at this stage in Yo!’s development. So, suggestions in the case of Yo! most welcome.

 

Apple iWatch: Watch, Fashion, Sensors or all three?

iWatch Concept Guess Late last year there was an excellent 60 minute episode of the Cubed.fm Podcast by Benedict Evans and Ben Bajarin, with guest Bill Geiser, CEO of Metawatch. Bill had been working on Smart watches for over 20 years, starting with wearables to measure his swimming activity, working for over 8 years as running Fossil‘s Watch Technology Division, before buying out that division to start Metawatch. He has also consulted for Sony in the design and manufacture of their Smart watches, for Microsoft SPOT technology and for Palm on their watch efforts. The Podcast is a really fascinating background on the history and likely future directions of this (widely believed to be) nascent industry: listen here.

Following that podcast, i’ve always listened carefully to the ebbs and flows of likely smart watch releases from Google, and from Apple (largely to see how they’ve built further than the great work by Pebble). Apple duly started registering the iWatch trademark in several countries (nominally in class 9 and 14, representative of Jewelry, precious metal and watch devices). There was a flurry of patent applications from Apple in January 2014 of Liquid Metal and Sapphire materials, which included references to potential wrist-based devices.

There have also been a steady stream of rumours that an Apple watch product would likely include sensors that could pair with health related applications (over low energy bluetooth) to the users iPhone.

Apple duly recruited Angela Ahrendts, previously CEO of Burberry, to head up Apple’s Retail Operations. Shortly followed by Nike Fuelband Consultant Jay Blahnik and several Medical technology hires. Nike (where Apple CEO Tim Cook is a Director) laid off it’s Fuelband hardware team, citing a future focus on software only. And just this weekend, it was announced that Apple had recruited the Tag Heuer Watches VP of Sales (here).

That article on the Verge had a video of an interview from CNBC with Jean-Claude Biver, who is Head of Watch brands for LVMH – including Louis Vuitton, Hennessey and TAG Heuer. The bizarre thing (to me) he mentioned was that his employee who’d just left for a contract at Apple was not going to a Direct Competitor, and that he wished him well. He also cited a “Made in Switzerland” marketing asset as being something Apple could then leverage. I sincerely think he’s not naive, as Apple may well impact his market quite significantly if there was a significant product overlap. I sort of suspect that his reaction was that of someone partnering Apple in the near future, not of someone waiting for an inbound tidal wave from an foreign competitor.

Google, at their I/O Developers Conference last week, duly announced Android Wear, among which was support for Smart Watches from Samsung, LG and Motorola. Besides normal time and date use, include the ability to receive the excellent “Google Now” notifications from the users phone handset, plus process email. The core hope is that application developers will start to write their own applications to use this new set of hardware devices.

Two thoughts come to mind.

A couple of weeks back, my wife needed a new battery in one of her Swatch watches. With that, we visited the Swatch Shop outside the Arndale Centre in Manchester. While her battery was being replaced, I looked at all the displays, and indeed at least three range catalogues. Beautiful fashionable devices that convey status and personal expression. Jane duly decided to buy another Swatch that matched an evening outfit likely to be worn to an upcoming family Wedding Anniversary. A watch battery replacement turned into an £85 new sale!

Thought #1 is that the Samsung and LG watches are, not to put a finer point on it, far from fashion items (I nearly said “ugly”). Available in around 5 variations, which map to the same base unit shape and different colour wrist bands. LG likewise. The Moto 360 is better looking (bulky and circular). That said, it’s typically Fashion/Status industry suicide with an offer like this. Bill Geiser related that “one size fits all” is a dangerous strategy; suppliers typically build a common “watch movement” platform, but wrap this in an assortment of enclosures to appeal to a broad audience.

My brain sort of locks on to a possibility, given a complete absence of conventional watch manufacturers involved with Google’s work, to wonder if Apple are OEM’ing (or licensing) a “watch guts” platform usable by Watch manufacturers to use in their own enclosures.

Thought #2 relates to sensors. There are often cited assumptions that Apple’s iWatch will provide a series of sensors to feed user activity and vital signs into their iPhone based Health application. On that assumption, i’ve been noting the sort of sensors required to feed the measures maintained “out of the box” by their iPhone health app, and agonising as to if these would fit on a single wrist based device.

The main one that has been bugging me – and which would solve a need for millions of users – is that of measuring glucose levels in the bloodstream of people with Diabetes. This is usually collected today with invasive blood sampling; I suspect little demand for a watch that vampire bites the users wrist. I found today that there are devices that can measure blood glucose levels by shining Infrared Light at a skin surface using near-infrared absorption spectroscopy. One such article here.

The main gotcha is that the primary areas where such readings a best taken are on the ear drum or on the inside of an arm’s elbow joint. Neither the ideal position for a watch, but well within the reach of earbuds or a separate sensor. Both could communicate with the Health App directly wired to an iPhone or over a low energy bluetooth connection.

Blood pressure may also need such an external sensor. There are, of course, plenty of sensors that may find their way into a watch style form factor, and indeed there are Apple patents that discuss some typical ones they can sense from a wrist-attached device. That said, you’re working against limited real estate for the devices electronics, display and indeed the size of battery needed to power it’s operation.

In summary, I wonder aloud if Apple are providing an OEM watch movement for use by conventional Watch suppliers, and whether the Health sensor characteristics are better served by a raft of third party, low energy bluetooth devices rather than an iWatch itself.

About the only sure thing is that when Apple do finally announce their iWatch, that my wife will expect me to be early in the queue to buy hers. And that I won’t disappoint her. Until then, iWatch rumours updated here.

European Courts have been great; just one fumble to correct

Delete Spoof Logo

We have an outstanding parliament that works in the Public Interest. Where mobile roaming charges are being eroded into oblivion, where there is tacit support in law for the principles of Net Neutrality, and where the Minister is fully supportive of a forward looking (for consumers) Digital future. That is the European Parliament, and the excellent work of Neelie Kroes and her staff.

The one blight on the EC’s otherwise excellent work has been the decision to enact – then outsource – a “Right to be Forgotten” process to a commercial third party. The car started skidding off the road of sensibility very early in the process, albeit underpinned by one valid core assumption.

Fundamentally, there are protections in place, where a personal financial misfortune or a criminal offence in a persons formative years has occurred, to have a public disclosure time limit enshrined in law. This is to prevent undue prejudice after an agreed time, and to allow the afflicted to carry on their affairs without penalty or undue suffering after lessons have been both internalised and not repeated.

There are public data maintenance and reporting limits on some cases of data on a criminal reference database, or on financial conduct databases, that are mandated to be erased from the public record a specific number of years after first being placed there. This was the case with the Spanish Gentleman who believed his privacy was being violated by the publication of a bankruptcy asset sale well past this statutory public financial reporting boundary, in a newspaper who attributed that sale to him personally.

In my humble opinion, the resolution of the court should have been to (quietly) order the Newspaper to remove (or obfuscate) his name from that article at source. Job done; this then formally disassociated his name from the event, and all downstream (searchable) references to it likewise, so achieving the alignment of his privacy with the usual public record financial reporting acts in law.

By leaving the source in place, and merely telling search engine providers to enact processes to allow individuals to request removal of unwanted facts from the search indexes only, opens the door to a litany of undesirable consequences – and indeed leaves the original article on a newspaper web site untouched and in direct violation of the subjects right to privacy over 7 years after his bankruptcy; this association should now have no place on the public record.

Besides timescales coded into law on specific timescales where certain classes of personal data can remain on the public record, there are also ample remedies at law in place for enforcing removal (and seeking compensation for) the publication of libellous or slanderous material. Or indeed the refusal to take-down such material in a timely manner with, or without, a corresponding written apology where this is judged appropriate. No new laws needed; it is then clear that factual content has its status reinforced in history.

In the event, we’re now subject to a morass of take-down requests that have no legal basis for support. Of the initial volume (of 10’s of 1,000’s of removal requests):

  • 31 percent of requests from the UK and Ireland related to frauds or scams
  • 20 percent to arrests or convictions for violent or serious crimes
  • 12 percent to child pornography arrests
  • 5 percent to the government and police
  • 2 percent related to celebrities

That is demonstrably not serving the public interest.

I do sincerely hope the European Justices that enacted the current process will reflect on the monster they have created, and instead change the focus to enact privacy of individuals in line with the financial and criminal record keeping edicts of publicly accessible data coded in law already. In that way, justice will be served, and we will no longer be subjected to a process outsourced to a third party who should never be put in a position of judge and jury.

That is what the courts are for, where the laws are very specific, and in which the public was full confidence.

The Moving Target that is Enterprise IT infrastructures

Docker Logo

A flurry of recent Open Source Enterprise announcements, one relating to Docker – allowing Linux containers containing all their needed components to be built, distributed and then run atop Linux based servers. With this came the inference that Virtualisation was likely to get relegated to legacy application loads. Docker appears to have support right across the board – at least for Linux workloads – covering all the major public cloud vendors. I’m still unsure where that leaves the other niche that is Windows apps.

The next announcement was that of Apache Mesos, which is the software originally built by ex-Google Twitter engineers – largely the replicate the Google Borg software used to fire up multi-server workloads across Google’s internal infrastructure. This used to good effect to manage Twitters internal infrastructure and to consign their “Fail Whale” to much rarer appearances. At the same time, Google open sourced a version of their software – I’ve not yet made out if it’s derived from the 10+ year old Borg or more recent Omega projects – to do likewise, albeit at smaller scale than Google achieve inhouse. The one thing that bugs me is that I can never remember it’s name (i’m off trying to find reference to it again – and now I return 15 minutes later!).

“Google announced Kubernetes, a lean yet powerful open-source container manager that deploys containers into a fleet of machines, provides health management and replication capabilities, and makes it easy for containers to connect to one another and the outside world. (For the curious, Kubernetes (koo-ber-nay’-tace) is Greek for “helmsman” of a ship)”.

That took some finding. Koo-ber-nay-tace. No exactly memorable.

However, it looks like it’ll be a while before these packaging, deployment and associated management technologies get ingrained in Enterprise IT workloads. A lot of legacy systems out there are simply not architected to run on scale-out infrastructures yet, and it’s a source of wonder what the major Enterprise software vendors are running in their own labs. If indeed they have an appetite to disrupt themselves before others attempt to.

I still cringe with how one ERP system I used to use had the cost collection mechanisms running as a background batch process, and the margins of the running business went all over the place like a skidding car as orders were loaded. Particularly at end of quarter customer spend spikes, where the complexity of relational table joins had a replicated mirror copy of the transaction system consistently running 20-25 minutes behind the live system. I should probably cringe even more given there’s no obvious attempt by startups to fundamentally redesign an ERP system from the ground up using modern techniques. At least yet.

Startups appear to be much more heavily focussed on much lighter mobile based applications – of which there are a million different bets chasing VC money. Moving Enterprise IT workloads into much more cost effective (but loosely coupled) public cloud based infrastructure – and that take full advantage of its economics – is likely to take a little longer. I sometimes agonise over what change(s) would precipitate that transition – and whether that’s a monolith app, or a network of simple ones daisy chained together.

I think we need a 2014 networked version of Silicon Office or Hypercard to trigger some progress. Certainly their abject simplicity is no more, and we’re consigned to the lower level, piecemeal building bricks – like JavaScript – which is what life was like in assembler before high level languages liberated us. Some way to go.

The Internet of Things withers – while HealthKit ratchets along

FDA Approved Logo

I sometimes shudder at the estimates, as once outlined by executives at Cisco, that reckons the market for “Internet of Things” – communicating sensors embedded everywhere – would be likely be a $19 trillion market. A market is normally people willing to invest to make money, save money, to improve convenience or reduce waste. Or a mix. I then look at various analysts reports where they size both the future – and the current market size. I really can’t work out how they arrive at today’s estimated monetary amounts, let alone do the leap of faith into the future stellar revenue numbers. Just like IBM with their alleged ‘Cloud’ volumes, it’s difficult to make out what current products are stuffed inside the current alleged volumes.

One of my sons friends is a Sales Director for a distributor of sensors. There appear good use cases in Utility networks, such as monitoring water or gas flow and to estimate where leaks are appearing, and their loss dimensions. This is apparently already well served. As are industrial applications, based on pneumatics, fluid flow and hook ups to SCADA equipment. A bit of RFID so stock movements can be automatically checked through their distribution process. Outside of these, there are the 3 usual consumer areas; that of cars, health and home equipment control – the very three areas that both Apple and Google appear to be focussed on.

To which you can probably add Low Power Bluetooth Beacons, which will allow a phone handset to know it’s precise location, even where GPS co-ordinates are not available (inside shopping centres as an example). If you’re in an open field with sight of the horizon around you in all directions, circa 14 GPS satellites should be “visible”; if your handset sees two of them, it can suss your x and y co-ordinates to a meter or so. If it sees 3 satellites, that’s normally enough to calculate your x, y and z co-ordinates – ie: geographic location and height above sea level. If it can only see 1 or none, it needs another clue. Hence a super secret rollout where vendors are offering these LEB beacons and can trade the translation from their individual identifiers to their exact location.

In Apple’s case, Apple Passbook Loyalty Cards and Boarding Passes are already getting triggered with an icon on the iOS 8 home screen when you’re adjacent to a Starbucks outlet or Virgin Atlantic Check-in desk; one icon press, and your payment card or boarding pass is there for you already. I dare say the same functionality is appearing in Google Now on Android; it can already suss when I get out of my car and start to walk, and keeps a note of my parking location – so I can ask it to navigate me back precisely. It’s also started to tell me what web sites people look at when they are in the same restaurant that i’m sitting in (normally the web site or menu of the restaurant itself).

We’re in a lull between Apple’s Worldwide Developer Conference, and next weeks equivalent Google I/O developer event, where Googles version of Health and HomeKit may well appear. Maybe further developments to link your cars Engine Control Unit to the Internet as well (currently better engaged by Phil Windley’s FUSE project). Apple appear to have done a stick and twist on connecting an iPhone to a cars audio system only, where the cars electronics use Blackberry’s QNX embedded Linux software; Android implementations from Google are more ambitious but (given long car model cycle times) likely to take longer to hit volume deployments. Unless we get an unexpected announcement at Google I/O next week.

My one surprise is that my previous blog post on Apples HomeKit got an order of magnitude more readers than my two posts on the Health app and the HealthKit API (posts here and here). I’d never expected that using your iPhone as a universal, voice controlled home lock/light/door remote would be so interesting to people. I also hear that Nest (now a Google subsidiary) are about to formally announce shipment of their 500,000th room temperature control. Not sure about their Smoke Alarm volumes to date though.

That apart, I noticed today that the US Food and Drug Administration had, in March, issued some clarifications on what type of mobile connected devices would not warrant regulatory classification as a medical device in the USA. They were:

  1. Mobile apps for providers that help track or manage patient immunizations by assessing the need for immunization, consent form, and immunization lot number

  2. Mobile apps that provide drug-drug interactions and relevant safety information (side effects, drug interactions, active ingredient) as a report based on demographic data (age, gender), clinical information (current diagnosis), and current medications

  3. Mobile apps that enable, during an encounter, a health care provider to access their patient’s personal health record (health information) that is either hosted on a web-based or other platform

So, it looks like Apple Health application and their HealthKit API have already skipped past the need for regulatory approvals there already. The only thing i’ve not managed to suss is how they measure blood pressure and glucose levels on a wearable device without being invasive. I’ve seen someone mention that a hi res camera is normally sufficient to detect pulse rates by seeing image changes on a picture of a patients wrist. I’ve also seen an inference that suitably equipped glasses can suss basic blood composition looking at what is exposed visibly in the iris of an eye. But if Apple’s iWatch – as commonly rumoured – can detect Glucose levels for Diabetes patients, i’m still agonising how they’d do it. Short of eating or attaching another (probably disposable) Low Energy Bluetooth sensor for the phone handset to collect data from.

That looks like it’ll be Q4 before we’ll all know the story. All I know right now is that Apple produce an iWatch, and indeed return the iPhone design to being more rounded like the 3S was, that my wife will expect me to be in the queue on release date to buy them both for her.

Death of the Web Home Page. What replaces it??

Go Back You Are Going Wrong Way Sign

One of the gold nuggets on the “This week in Google” podcast this week was that some US News sites historically had 20% of their web traffic coming in through their front door home page. 80% of their traffic arrived from links elsewhere that landed on individual articles deep inside their site. More recently, that has dropped to 10%.

If they’re anything like my site, only a small proportion of these “deep links” will come from search engine traffic (for me, search sources account for around 20% of traffic most days). Of those that do, many arrive searching for something more basic than what I have for them here. By far my most popular “accident” is my post about “Google: where did I park my car?”. This is a feature of Google Now on my Nexus 5 handset, but I guess many folks are just tapping that query into Google’s search box absolutely raw (and raw Google will be clueless – you need a handset reporting your GPS location and the fact it sensed your transition from driving to walking for this to work). My second common one is people trying to see if Tesco sell the Google Chromecast, which invariably lands on me giving a demo of Chromecast working with a Tesco Hudl tablet.

My major boosts in traffic come when someone famous spots a suitably tagged Twitter or LinkedIn article that appears topical. My biggest surge ever was when Geoffrey Moore, author of “Crossing the Chasm”, mentioned my one page PDF that summarised his whole book on LinkedIn. The second largest when my post that congratulated Apple for the security depth in their CloudKit API, as a fresh change to the sort of shenanigans that several UK public sector data releases violate, appeared on the O’Reilly Radar blog. Outside of those two, I bump along at between 50-200 reads per day, driven primarily by my (in)ability to tag posts on social networks well enough to get flashes of attention.

10% coming through home pages though; that haunts me a bit. Is that indicative of a sea change to single, simple task completion by a mobile app? Or that content is being littered around in small, single article chunks, much like the music industry is seeing a transition from Album Compilations to Singles? I guess one example is this weeks purchase of Songza by Google – and indeed Beats by Apple – giving both companies access to curated playlists. Medium is one literary equivalent, as is Longreads. However, I can’t imagine their existence explains the delta between searches and targeted landing directly into your web site.

So, if a home page is no longer a valid thing to have, what takes it’s place? Ideas or answers on a postcard (or comment here) please!

Explaining Distributed Data Consistency to IT novices? Well, …

Greek Shepherd

it’s all greek to me. Bruce Stidston cited a post on Google+ where Yonatan Zunger, Chief Architect of Google+, tried to explain Data Consistency by way of Greeks enacting laws onto statute books on disparate islands. Very long post here. It highlights the challenges of maintaining data consistency when pieces of your data are distributed over many locations, and the logistics of trying to keep them all in sync – in a way that should be understandable to the lay – albeit patient – reader.

The treatise missed out the concept of two-phased commit, which is a way of doing handshakes between two (identical copies) of a database to ensure a transaction gets played successfully on both the master and the replica sited elsewhere on a network. So, if you get some sort of failure mid transaction, both sides get returned to a consistent state without anything going down the cracks. Important if that data is monetary balance transfers between bank accounts for example.

The thing that impressed me most – and which i’d largely taken for granted – is how MongoDB (the most popular Open Source NoSQL Database in the world) can handle virtually all the use cases cited in the article out of the box, with no add-ons. You can specify “happy go lucky”, majority or all replicas consistent before confirming write completion. And if a definitive “Tyrant” fails, there’s an automatic vote among the surviving instances for which secondary copy becomes the new primary (and on rejoining, the changes are journaled back to consistency). And those instances can be distributed in different locations on the internet.

Bruce contended that Google may not like it’s blocking mechanics (which will slow down access while data is written) to retain consistency on it’s own search database. However, I think Google will be very read heavy, and it won’t usually be a disaster if changes are journaled onto new Google search results to its readers. No money to go between the cracks in their case, any changes just appear the next time you enact the same search; one very big moving target.

Ensuring money doesn’t go down the cracks is what Blockchains design out (majority votes, then change declines to update attempts after that’s achieved). That’s why it can take up to 10 minutes for a Bitcoin transaction to get verified. I wrote introductory pieces about Bitcoin and potential Blockchain applications some time back if those are of interest.

So, i’m sure there must be a more pithy summary someone could draw, but it would add blockchains to the discussion, and probably relate some of the artistry behind hashes and Git/Github to manage large, multiuser, multiple location code, data and writing projects. However, that’s for the IT guys. They should know this stuff, and know what to apply in any given business context.

Footnote: I’ve related MongoDB as that is the one NoSQL database I have accreditations in, having completed two excellent online courses with them (while i’m typically a senior manager, I like to dip into new technologies to understand their capabilities – and to act as a bullshit repellent!). Details of said courses here. The same functionality may well be available with other NoSQL databases.

Uber in London: The Streisand Effect keeps on giving

Uber Logo

With the same overall theme as yesterday, if you’re looking at your future, step one is to look at what your customers would value, then to work back to the service components to deliver it.

I’ve followed Uber since I first discovered them in San Francisco, and it looks a simple model – to the user. You want to go from where you are to another local destination. You typically see where the closest driver is to you on your smartphone. You ask your handset for a price to go to a specific destination. It tells you. If you accept, the car is ordered and comes to pick you up. When you get dropped off, your credit card is charged, and both you and the taxi driver get the opportunity to rate each other. Job done.

Behind that facade is a model of supply and demand. Taxi drivers that can clock on and off at will. At times of high demand and dwindling available ride capacity, prices are ramped up (to “surge” pricing) to encourage more drivers onto the road. Drivers and customers with voluminous bad ratings removed. Drivers paid well enough to make more money than those in most taxi firms ($80-90,000/year in New York), or the freedom to work part time – even down to a level where your reward is to pay for your car for a few hours per week of work, and have free use of it at other times.

The service is simple and compelling enough that i’d have thought tax firms would have cottoned onto how the service works, and to replicate it before Uber ever appeared on these shores. But, with a wasted five years, they’ve appeared – and Taxi drivers all over Europe decided to run the most effective advertising campaign for an upstart competitor in their history. A one-day 850% subscriber growth; that really takes some doing, even if you were on the same side.

I’m just surprised that whoever called the go-slows all over Europe didn’t take the time out to study what we in the tech industry know as “The Streisand Effect” – Wikipedia reference here. BBC Radio 2 even ran a segment on Uber at lunchtime today, followed by every TV News Bulletin i’ve heard since. I downloaded the app as a result of hearing it on that lunchtime slot, as I guess many others did too (albeit no coverage in my area 50 miles West of London – yet). Given the five years of missed prep time, I think they’ve now lost – or find themselves in fast follower mode to incorporate similar technology into their service before they have a mass exodus to Uber (of customers, then drivers).

London Cabbies do know all the practical use of rat runs that SatNav systems are still learning, but even that is a matter of time now. I suspect appealing for regulation will, at best, only delay the inevitable.

The safest option – given users love the simplicity and lack of surprises in the service – is to get busy quickly. Plenty of mobile phone app prototyping help available on the very patch that London Black Cab drivers serve.

More evidence of the Relentless Migration from CapEx to OpEx

Google Self Driving Car

There’s been quite a lot of commentary in the last week following Google co-founder Sergey Brin’s presentation at the Re/code Conference; he got to show this video of the next iteration of their self driving cars. For a bit of history leading up to that announcement, i’d recommend watching two videos on the progress of this project to date, and then the video Sergey showed last week:

  1. Sebastian Thrun – the project lead – giving a presentation about self driving cars in 2011 and showing a few of them in action here (it lasts 4 mins, 14 seconds).
  2. A video that Google produced with a twist near the end here (3 mins 1 second long).
  3. And the video of the new exploratory design announced this week here (2 mins 53 seconds).

My brain diverted another way to most. Have you ever seen and experienced Uber? You open an app on your Smartphone, which identifies where you are located. You tell it where you’d like to travel to, and it will tell you (a) how long a wait until a taxi will arrive to collect you and (b) the fixed cost of the journey. If you accept both, your taxi is scheduled, collects you, drops you off and the charge made to your credit card. Done! The system is set so that both driver and passenger rate their experience, so that good service from both ends of the transaction is maintained.

It’s probably well known that most cars purchased are tremendously under utilised and taking up valuable parking space in Cities all over the world. There are separate innovations where drivers can clock on and off at any time they wish, and obviously less resources available results in the pricing rising – to encourage more Uber drivers back online to service the demand. There are also periods of exceptional demand where Uber will jack the prices right up – transparently to all – to ensure there are the right number of drivers available to service the very busy customer demand periods (like rush hours).

Uber have stirred controversy in the Taxi industry because anyone (with lack of bad references) can be a Uber driver, and part time working is a personal choice. Those who work full time, as self employed drivers, often get much higher pay than most routine licensed Taxi drivers; in New York, reckoned to be north of $90,000/year gross and (after car finance and depreciation costs) around $60,000/year. Drivers who operate part time can use the income to offset the cost of their cars, partly or completely, if that is their choice.

The bit that caught my imagination was what would happen if a City (or a private company) bought a fleet of these Google cars and hooked them into Uber. After use, they go to their next collection point or back to a well researched cache – ready for the best possible service to the next likely passenger. Or to the Petrol Station to be refueled (and I hope a manufacturer recall doesn’t end up with fleets of them working back to their factory, all at once!).

I guess in the early days, there will be idiots on the road who’ll try to psych them out, but once an integral piece of local life, I think a Google/Uber combination would be tremendous. Not least, as yet another glowing example that paying for a shared resource is much cheaper than the inefficiencies inherent in expensive, rarely used Capital assets.

CapEx is the past, OpEx is the future.

Recommended Bedtime Reading, and signing off for a bit…

I’ve never really been a big fiction fan. About the only author i’ve read extensively (outside high technology and business stuff – don’t yawn) was by Michael Crichton. At least the books that have yet to be turned into films. Well, all except “Disclosure”, where Demi Moore sexually harasses Michael Douglas and then throws the company’s political establishment against him when he refuses to succumb to her charms. But I digress.

There’s been a lot of comment on the blogs and twitter feeds I follow on the West Coast of the USA that keep on citing a new book by Andy Weir called “The Martian”. I tried to buy it on my last trip abroad, thinking i’d go buy the voiced version on Audible to listen to, but baulked at it’s then £20+ price tag. However, it appeared on an Amazon email last week for under £10 in hardback form, so I bought it.

Finished it today (like many of the USA folks, completely immersed in it for two days between work bursts). I’m completely with them; it is a fantastic book, and would make a great film. A modern day Robinson Crusoe, but one accidentally left behind on Mars. At least Crusoe had to worry more about Cannibals than continuously working around all the life support systems, and food, to last long enough to be rescued. If indeed NASA didn’t just leave him behind to eat his poison pills. Thoroughly recommended, and superbly written throughout.

Tomorrow, i’m off to Cornwall for a short break before I start my next assignment, which will start on June 2nd. Really looking forward to it. As such, the frequency of my blog posts are, with effect from today, going to drop to one per week. I think my daily posts have now caught up with my brain nuances, and the newsflow in High Technology has started to slow. At least until Apple have their Worldwide Developers Conference at the start of June, and Google do their matching I/O conference a week or two later.

In the three months or so i’ve been writing this blog, a few articles keep on getting lots of page views well after their posting data. The Crossing the Chasm one got reposted on LinkedIn by the original author of the book i’d summarised, and I started to get warnings from WordPress that I appeared to have an incoming tidal wave for 3 days running.

For some reason, my mention of Chromecast working on the Tesco Hudl tablet gets regular traffic, nominally by hoards of people querying Google to see if Tesco sell Chromecast in the UK.

Surprisingly few look at my tips for spotting the 4 key trends to look at with any business, in order to suss out what dimensions are and are not working. Or the other post about how to conduct yourself in a price war (there are only two things you focus on, and all paths to action stem from there).

I’m gone for a week, and to see how adept my 2 year old granddaughter has got on her iPad Mini we bought her (a necessity, as when she visits us, I never could get it back until she leaves again). She is impressively native on it with photos and with YouTube. Even tries to swipe “Skip Ad” on ITV on the telly.

So, signing off until May 30th. See you once i’m back.