It’s clear that the old school approach to media buying is behind the lack of commitment to mobile spending. I am not a true believer in the idea that traditional media strategies (banners and rich media units) will ultimately work in mobile, but before the riddle is solved one thing is certain: we need more data in the channel to figure it out. Since no brands are offering free placements, there needs to be a much greater level of spending to definitively see what works and what doesn’t. Until then, these drips and drabs of trickle-funds will not yield anything compelling enough to open the floodgates. We are at a strange inflection point in mobile marketing, where virtually all brand marketers finally agree that mobile is real – hell, critical – but no one really knows the “formula” to unleash its power from a ROI perspective. So, brands wait for the money to return and keep one toe in the water until it arrives. What’s needed is something that won’t likely happen: an industry consortium of brands across verticals who collectively agree to spend another 10-20% of their media and marketing dollars to mobile in 13 Q4 and 14Q2/2 to flood the channel with campaigns (as well planned and strategically sound as is possible of course) to generate some real data that can be evaluated by mid-year 2014. Someone will make it through the glass ceiling. This will never happen. Brands will continue their Hamlet-like approach to mobile – pontificating, philosophizing, ruminating, doubting and waiting for their money to return.
Ok, so here’s a more accurate and current update to my earlier post about the so-called “Facebook phone”.
Seems like what Zuck is doing is now allowing any Android phone user to essentially turn their device into a “Facebook phone” by simply downloading an app called “Home”. This app places a new Facebook layer over the existing Android OS, which makes Facebook the primary interface for all basic phone functions. I was accurate that there will be a new device from HTC called the HTC First – which will be the first phone to be sold with Home pre-loaded into the OS. But, on April 12, any Android user can go to the Google Play store and download Home and turn their Android phone into a Facebook phone.
According to TechCrunch: Anyone who has the most recent version of the current Facebook App as well as Messenger will be able to download Home. If so, you will apparently get some kind of banner alert to download Home from the Google Play store. When you launch it the first time, you can decide to “try once”, or choose “always” to swap in Home for you home screen from then on. Facebook will try to make Home available on tablets within a few months, and it’s supposed to be a great experience there. Every month, Facebook will release a Home update to add new features and make it accessible to new devices. The Newsfeed feature will be called “Cover Feed” and will display what are called “Chat Heads”, or little bubbles with the face/head of your friends when you receive a chat or message from them. These Chat Heads will appear at the top of the screen within any app or feature that you use on the phone and can be ignored or responded to via some swiping options.
Overall, the idea is to fully layer or integrate Facebook into the entire Android experience, which for all intents and purposes makes the Facebook experience a 24/7 always on environment for users. This is could be a real boon for people who already rely heavily on Facebook for updates, chats, invites, groupings, etc. on Facebook – and weave these functions more ubiquitously into their daily use. It could also drive people to WANT to integrate Facebook’s tools into their usage if they find that the new Home OS works well, and provides more speed and connectivity to their social network.
This is an interesting and very clever strategy. By creating a universally accessible app for any Android user, Facebook has created a very robust distribution strategy. You have to think that a lot of Android users are at the least going to download it and try it (the Home app allows for a “try it once” option- smart) and play with it for a little while. Some will stick, some will not. But this strategy exponentially increases the pool of potential users.
Amazingly, Google cooperated with this – which is shocking frankly, as Google’s entire Android strategy is going to get killed by this new app.
Here’s why: One of Google’s primary objectives for the development of Android was to force users to rely on Google’s proprietary tools: Gmail, Search, Google Maps, Google Chat, etc. and hence continue to feed the beast with the heaps of data that nourish its colossal search juggernaut. With Home, Facebook bypasses all of these tools by letting users simply use Facebook for most of these functions. Why Google would be ok with this is curious. Could be that Zuck is playing a very clever game of gotcha – in forcing Google to make a Sophie’s Choice about its commitment to Open Source Free Range integrations. We shall see how it plays out.
Facebook is announcing the launch of their first “Facebook Phone” today at 1pm. Alot of buzz on this new gadget is filling the net. I thought I’d weigh in.
What is it?
First its important for folks to understand that Facebook is not “building” its own phone. They do not have the desire nor muscle to get into the device manufacturing business. Apparently, this will be a new customized version of Android that will offer a fully immersive Facebook integration – its an Application Layer to the existing Android OS that essentially makes Facebook ( and all of its components) the interface for the user that uses the phone. They are partnering with HTC to create this new version – apparently called the HTC First, and bring it market in a very opportunistic way. They are looking to target the midlevel mobile phone users that do not currently own the higher end smartphones like iPhone 5 or Galaxy III – these folks are more inclined to “upgrade” to a more affordable phone that gets them into the more sophisticated device market without hitting their wallets on the higher end phones that are out of reach. This is a good strategy as this integration and device may be the impetus for these users to make that switch. Plus these people tend to rely a lot on Facebook as a core social connection platform.
As we have seen over the last few years, Facebook has been building and acquiring a suite of Facebook components that all work as a part of the larger Facebook ecosystem: Messenger, Instagram, Voice Calling, etc, and all of these sub-apps can be independently placed on both iPhones and Android phones today. So, over time, Facebook has essentially been creating their own “replacement” apps for all of the core OS apps of iOS and Android – in an attempt to gain more user integration on an adhoc basis. The issue for them in this scenario, is that due to their landlord/tenant status on iPhones and current Android phones they are subject to the laws inherent to being inside of a controlled environment. What this new concept does is free them from those shackles and allows Facebook to be the main if only choice for users to perform their basic functions. The thinking here is that a vast chunk of Facebook users are on the Facebook app for a majority of the time each day anyway – looking at their feeds, sharing updates, texting their friends and sharing and viewing pictures, etc. This new device will make those functions the core of the experience. The main screen will apparently look like a Facebook welcome screen and all of the user interactions will be done through Facebook’s platform.
So, why are they really doing this?
- At the end of the day its data. Data is Facebook’s mother’s milk. The more user data that they can cull, the more targeted their ads can be and more revenue they can drive. So, getting those other pesky interfaces out of the way allows Facebook to essentially be the entire data gateway for this device and hence will be allow them to capture ALL of the user data that is captured on the phone.
- International and Emerging Market Penetration: This new OS will also be used as a strategy to gain ground in emerging markets like India, Russia, China and Brazil, where feature phone usage is still the norm. Putting a cheap device into those markets with a simple version of Facebook baked in will capture new Facebook users for the long term when computers and advanced devices are more prevalent. These Facebook phone users will be hooked at this point and likely create online Facebook accounts once they have the means to in order to maintain the connections that they have established via mobile. Pretty slick.
- Expose Apples weakness. I don’t know if this is a defined strategy – but it makes sense. Apple is know for its closed and controlled environment, hence this kind of partnership would not even be possible on an OS device. Android is know for its open source customization. Users may flock more to Android phones as this initiative exposes some folks to the limitations of Apples controlled platform. Maybe.
- Mobile is Facebook’s future- and they know it. Getting some kind of beach front in the mobile space was an inevitability and this approach makes the most business sense.
Wil users care?
Who knows? I don’t – aside from my interest as a mobile professional, I don’t have enough of a reliance on Facebook to see this as a value prop. But users who DO use Facebook as their primary tool set and are social citizens may buy in. Assuming that there are enough people out there who have lower end phones and see this as their affordable upgrade opportunity (and it carriers and HTC can make it affordable enough for users to get in) they will likely bite. Who knows? Perhaps once this launch proves successful, Facebook has designs to bake this new OS into more advanced Smartphones ( like the HTC One Second? ) it may be a new offering in the smartphone display case.
The event is at 1pm today. I’ll see how right or wrong I am then.
“@#$$%$%@. Why won’t (input name of Brand or CMO, or Marketing Director here) actually try something risky and innovative for once? I’m tired of bringing ideas to the table, only to have them road-blocked by these bureaucrats. They demand fresh ideas, but they never have the onions to actually execute. Why am I wasting my $#$%*!@ time?”
It seems that there’s some law, similar to Moore’s Law, which postulates that the more new marketing innovations are made available to brands, the more risk-averse brands become. This “Inertia Curve” doesn’t seem to be getting any better. Too much choice sends marketers under a rock for some reason. I’m sure the economy and job security are a large part of this – but that can’t be all. It just can’t. We all know that down times like this are the BEST times for making waves. So where are the thinkers? Where did they go?
Marketing professionals (myself included) are pulling their hair out performing acrobatic Bo jangles in the conference room, while our clients pore over mindless ROI projections and assess “brand risk” scenarios. It’s enough to make one throw in the towel. Media buyers and planners will always get a seat at the table, but talk about something fresh like mobile, and brands become Hamlet.
I read an excellent article about A.G. Alley’s new book ‘Playing to Win’ where the marketing titan discusses his assessment of today’s corporate brand culture. He summed up exactly what me and my colleagues are feeling a lot of today.
“They think they have a hot product or hot service, and these don’t last forever. They think that benchmarking, best practices and copying what the rest of the industry does is a strategy. They try to be all things to all people. “
So in essence, he points out how brands rest on their laurels and play it safe – kicking the proverbial budget down the road without thinking about the bigger picture. And in this kind of environment, no ground-breaking marketing decisions can be made. So for those of us who got into mobile marketing to cause a stir and do something exciting, the search for risk-taking clients is like hunting for the elusive Yeti.
The Mobile channel is rife with this mentality. While we are certainly seeing a great deal more respect paid to mobile (there are some stellar standouts who are taking risks that are paying off) it’s still an afterthought for most mainstream brands. Great ideas are brought to the table, but the scraps of shekels that remain after the standard TV and Media budgets are consumed are not enough to move the needle – but just enough to make the CMO feel like he checked the innovation box for the quarter. The problem with this approach is that no significant mobile campaign will ever succeed unless the proper resources and focus is placed on it. So, they fail. And the cycle continues. Bean counters prevail, and it’s back to the basics.
Here are a few things that CMOs who are stuck in the mud can to do to move the needle on their innovations:
1) Re-think ROI: Marketers have become spoiled by metrics like CTR, CPC and Conversion Tables. This Spreadsheet Culture has created a new breed of market-think that by its nature shuns innovation and turns brand marketing into a Bloomberg Terminal. This is no way to move ahead. Mind you, I am not shunning the value (or necessity) of managing returns, however, I am espousing the return of bleeding edge thinking that got most top brands to where they are in the first place. Take a look at your massive TV buys. What ‘measurable’ return do they get you (and please don’t cite Neilson ratings)? Brand marketing is risky. But it’s what drives the rest of the train. Have the guts to slice off a significant hunk of your TV budget for Q4 and spend it on a truly integrated mobile campaign. Sure, you will get push back from your CFO, but there is more inherent brand lift from doing something new, than making a cooler TV spot. Create an experimental budget that is designed to make some smart mistakes. Learn along the way and in the process make some real waves. You will enjoy your job again.
2) Think about Your Consumer: Remember the days when the consumer came first? Consumers are now doing more on mobile and social than any other medium. I know, I know. TV trumps all. But Second-Screen marketing is now a reality. Users now EXPECT more innovation and demand a mix of brand messages. Traditional marketing tactics will always have their respective roles, but branch out and think about how your consumers are buying, shopping and sharing. Most good CMOs know this stuff, but for some reason when it comes to budget allocation time, they don’t take bold action.
3) Downtime is the Right Time: Slow economies are hibernation times for innovation, but economic wisdom supports the idea that these are best times to make changes. Your competition likely has their head in the sand, too. Lets face it, once things look up again (and who knows when that will be anyway?) brands will gain the confidence to break out the red-velvet blazer. Break yours out now. You wont need to spend as much as you wont need to break through a lot of clutter – and your audience wont be over loaded with trinkets.
4) Listen to your Trusted Advisors: Your agencies are good at what they do (well, most of them are). Listen to them. They don’t want to lose your business, so it’s not in their best interest to do things that wont reflect good on them. You hired them to bring a fresh outside perspective and likely slogged through a brain-melting RFP process to select them. So let them do their job. I talk to a lot of pretty smart agency executives who have some really impactful and responsible ideas for their clients – and can’t get them to act. We do care about your business regardless of how self-serving our motivation may seem to be at times. We win by making you win.
I hope I wake up tomorrow morning to a new radio show.
Mobile HTML5, and the Race to App Ubiquity
For the uninitiated, you may have heard rumblings over the last year or so about this thing called “HTML5” app development. This wonky discussion is getting even more heated up recently and while it seems like a topic best suited to Stack Overflow chat rooms or WebMonkey, the fact is that this development trend will likely have a direct impact on everyday app users. In fact, many pedestrian smartphone users are likely interacting with HTML5 apps and don’t even know it.
HTML5 – What the hell is it?
Ok, according to Wikipedia:
“HTML5 is a markup language for structuring and presenting content for the World Wide Web and a core technology of the Internet. It is the fifth revision of the HTML standard (created in 1990 and standardized as HTML4 as of 1997) and, as of December 2012, is a W3C Candidate Recommendation. Its core aims have been to improve the language with support for the latest multimedia while keeping it easily readable by humans and consistently understood by computers and devices (web browsers, parsers, etc.).”
For those of you who are still scratching your heads, here’s a more pedestrian definition from Mediascope’s blog page:
“HTML stands for “Hyper Text Markup Language” which is geek-speak for “a set of rules that tell computers how to interpret code to display websites.”(seriously, there are literal sets of rules) HTML5 is the 5th version of these rules, and brings major upgrades to the capabilities of websites. To oversimplify the explanation, HTML5 is a convergence of several technologies currently used to make websites interactive.”
So, what is the big deal here? you may be asking. Well, simply put, this new development standard allows mobile apps to be built essentially as websites instead of downloadable applications. Right now, if you are, say, an iPhone user, and wanted to check out a new app you just read about, you would as, per usual, go to the Apple App Store, perform a search, find the desired app, and then download it from the store to your phone. This process literally places a packet of code directly into brain of your phone –which, depending of the functionality of the app – is powered by the device itself and runs “natively” on your phone, in many cases whether you are on the internet or not (again, depending on the app – for example, many game apps run independent of the internet – which is why we see so many people playing mobile games on their phones when down in the subway). What HTML5 development standards offer is a “bypass” of this process, by allowing web-based “apps” to run over the internet via the mobile web browser (in the case of iPhone, this is the default Safari browser). This emerging platform makes for some very provocative implications for users, app developers and the big OS giants (namely Google and Apple – and also Microsoft and Blackberry).
As the sophistication of HTML5 development matures, app developers will be able to build and deploy applications without having the deal with the toll booth and inspection process that Apple and Google (to a lesser degree) impose on apps before they are deemed consumer worthy. So, to provide some context for the reader, imagine a future where there is no longer an “app store” any more. Simply mobile internet-based links that allow anyone on any device to immediately gain access to app experiences via the web. No such thing as iPhone apps, or Android apps, or Blackberry apps or Microsoft apps or Whatever apps. These distinctions would disappear, and one web-based development initiative would be compatible to any smartphone user. Seems interesting no? Well in some ways that future is already here. In a number of instances for some apps, this deployment and development strategy is already being utilized. Take for example, YouTube. A totally HTML5-based mobile site. It looks like an app on your phone – but the YouTube icon on your smartphone is really just a “Bookmark” link to the mobile website. Netflix also utilizes this same development and deployment strategy. There are many other examples in the mobile webisphere that you can check out here: http://www.mobilehtml5.com/
Pretty cool. So, why is this not more the norm?
Good question. And this is where it gets complicated. Basically the big debate about HTML5 development came to a head when back in 2011, Zuckerberg finally released a NON- HTML5 version of the Facebook app. Yup. Facebook was from the outset, an HTML5 app. And it sucked. You remember how awful it was? How it crashed all of the time, and didn’t load, and never seemed to work and was a slow, cruddy mess? Well, it was because the visionaries at FB decided that an HTML5 deployment – for all of the reason above – was the way to go for its huge user base. And it was a good idea, frankly. A bit ahead of its time, but a good idea. In order to save face (pardon the pun) for years, Zuck tried to fix and mend and tweak the app to improve it – claiming that soon the HTML5 development standard would mature at the right pace and meet the needs of his development team. But it didn’t happen. So, in 2011, FB released a brand new “native” FB app – and the improvement was immediate. So, that brings us to the answer to the question, what is this not the norm? Because for all of the promises and opportunities that HTML5 development offers, its still a lousy experience for most of the more complex applications we use everyday. Here’s why:
1) The mobile internet, well, sucks. Lets face it. The mobile internet, while an incredible and earth-changing technology, has not kept pace with the way that we want to use it. Its unreliable, its patchy, its fragmented, and its frustrating. At least in the Western part of the world (Asia is light years ahead of us on this – but that’s for another post). So, running sophisticated, high-interactivity apps over the mobile web is a risky proposition. That’s what Facebook experienced. Hence, only specific types of apps are appropriate for HTML5 deployment – and those are the ones that best suit the platform (low interactivity, “thin” content). Banking apps, and shopping apps, as examples, are too information-heavy for a web-based experience, so these and others like this, are typically built in native format.
2) HTML5 is just not there yet. It’s still a nascent technology. The code standards are still fragmented. Development cycles don’t ubiquitously translate across all mobile operating systems (apps built this way still need some moderate “tweaking” per OS to ensure that they work across all devices and OS versions), and there is a great deal of disagreement among the community as to what will become standard and what is still open to interpretation. So most of these apps are skunkworks initiatives (other than the YouTube’s and Netflix’s of the world) or labors of love.
3) The Platforms Are Not Supportive – As you can imagine, the core players, Apple, Google and Microsoft, are very threatened by this development (Apple has the most to lose, frankly). They RELY on the platform ubiquity that keeps their users tethered to their devices. The App Store deployment strategy offers Apple a closed-gate environment where they can play traffic cop and gatekeeper to both the app developer community (who must comply with Apple’s strict app development standards) and the Apple device users like you and me who must go through Apple’s store to buy apps (and music and movies and books and magazines and soon clothes, devices, food, and who-the-hell-knows-what). So, as you can clearly see, allowing consumers to have access to all of this great stuff via the internet is a huge threat to their entire toll booth business model. Word on the street is that Apple sees the inevitability of this coming wave, and is simply going to develop some other standard or gate to maintain its hold – and I wouldn’t count them out. They are good at this sort of thing. But lets just say that the immaturity and unreliability of HTML5 at the moment is not something that Apple is weeping over.
4) App Developers are divided – While it seems to make for a boon to app developers to remove the shackles and deploy apps via the internet, the fact is it’s a mixed bag. Many app developers have spent years putting together their native app development capabilities and processes. And they make good money being a good citizen to Apple. And they like it this way. Others are clamoring for the day that the technology and maturity develops so they can get around the gate and start a direct to consumer business. So there is some polarity in the developer community which hampers R&D.
Summation: Keep looking
So, in short, its clear that the HTML5 development debate will only get louder and louder in 2013 as more and more of these type of engagements make it to the web and are successful. A few interesting development are occurring in the developing world. According the Business Insider’s Mobile Intelligencer:
• Gree, the Japanese social mobile gaming giant, has built an HTML5 platform to speed adoption of its games in the 169 countries where it’s already present.
• Telefónica has 175 million mobile customers across Latin America, as well as an investment in Chinese carrier Unicom. Telefónica wants to push HTML5 not just for mobile development, but also as an operating system via theFirefox mobile platform.
• Chinese manufacturer ZTE has also signed on to carry handsets powered by the Firefox mobile OS, in a bid to reduce dependency on Android.
And it looks like Mozilla is now creating a new mobile operating system based on Firefox that is supposed to launch this year – which is based entirely on HTML5. These kind of developments will only push forward acceptance and standardization of HTML5 development – and US based operators are going to take notice and see a new business opportunity in there. So, dear users, your apps may take a different turn in the coming year. Happy Apping.
Somehow, as fate would have it, I became a Mac person. It was all-unintentional, but here I am. But that’s just a precursor to a real issue that I became more starkly aware of recently. So, just to get you up to speed:
Induction Phase 1: Smartphone:
It all started, like most, with my purchase of an iPhone 4 in 2010. I was a Blackberry holdout at this time – in love with my QWERTY and my BBM community. The iPhone 3G was a nice salvo to the tech industry, but the 4 really set the stage for Apple’s vision for how mobile communications would advance into a more ubiquitous ecosystem. The iPhone was the new cool phone to have, and being a mobile marketing professional it made practical sense for me to be using the very thing that provided the framework for what it was I was advocating at the time. I kept my Blackberry 9000 clutched in my hand for 2 years after this – walking around with two devices. Once this became too problematic (and BB failed to get itself up to par with Apple) I weepingly ditched my qwerty and officially became an iPhone user (Fade in violins).
Induction Phase 2: Laptop:
The iPhone’s compatibility with my Toshiba laptop was not an issue for me – and having used PCs for over a decade I was still very comfortable with the Windows OS feel and organizational logic. I was hard-wired for the Windows OS – and I was fine. Last year when I was in my initial discussions with WWD&S about coming aboard, one of the partners, snickered at me during one of our meetings, “so, you ready to be Mac guy?”. It didn’t strike me until that moment that they were a Mac-based office. “Uh, I guess so”. I saw her smiling at me – my expression looking like the host of a dinner party just asked me if I would like to try the fried liverwurst and gorgonzola rolls. Two months later when I officially came on board, we explored the option of letting me keep my Toshiba, but it soon became obvious that the workaround was not optimal for a whole host of reasons (interconnectivity, file-sharing, OS incompatibility, network issues, etc.). So I relented and they equipped me with a new MacBook Air. I’ll concede it’s a gorgeous machine. In the Apple tradition, their total control over the box and software makes for a lovely integration of form and function. I’m still getting used to the OS (I jumped in at Mountain Lion, so I didn’t have to work off any of the UX/UI paradigm shifts that some of my stalwart Mac users reported). In getting used the new OS environment, I would describe the re-mapping of my brain like going from working inside a structured grid made of silicate (Windows 7), to working inside of a room made of gelatin (OS ML). Every nuance now has this rounded-edge feel, and the navigational dynamics are more fluid and “gooey” than Windows. It’s been a strange experience and my brain still wants to find files, store documents, switch applications and move around the Windows way. Anyway, perhaps more on that some other time.
Induction Phase 3: Tablet:
WWD&S recently had a Holiday party, and one of the gifts for the staff was an iPad mini. I was overwhelmed by the generosity of this – and really excited, as I held off on getting a tablet while I waited to see which one would be best option in the array of new ones coming into the market. So, now, here I was, firmly placed with the entire Apple user ecosystem. All of my devices synced to my iCloud content and my iTunes account/library, all of my devices receiving the same iMessage at the same time (which results in a very strange moment: which one do I use to respond? And, what made me choose that one? A weird experience for sure).
So, here I am. A fully ensconced Mac person. Surrounded by Apple’s 360 consumer offering. And much like riding around for the first few weeks in a new brand of car (like when my Pop went from GM to Acura), I found myself making some attitude adjustments when I opened up the Mac in public – embracing myself as a Mac person. But then something else happened: At CES in January, I took some time to peruse the Samsung exhibit area – and played around with their new selection of Galaxy phone and Tablets (Phablets?). I was taken in by some of the innovations that Samsung is loading into these devices – and started thinking, “hey, this may be a good option”. But it struck me. I’m stuck now. I have all of my stuff in iTunes, iCloud, iMessage, iThis iThat, and migrating to a new “platform” would be a royal pain in the ass. Which forced me to ask: Would it be worth the effort? Do I love these new Android features so much that I would be willing to extricate myself from this nicely organized (well, most of the time) soft-OS world? The answer was no. It wasn’t. So I walked on and made my way to the LG booth, feeling kind of dejected and defeated over that realization.
Cost of Migration:
This puts me square into the conundrum that both consumers and the big platforms are wrestling with: The Platform Trap.
This of course is not just my experience. Apple and Google and Facebook (and now Microsoft and maybe even Blackberry) are long past selling products or devices. They sell platforms and ecosystems, designed specifically to create indispensability. These platforms “require” total immersion in a controlled system of tools in order to gain the full benefit of the preferred platform. The idea is pretty simple – and it’s getting harder and harder for consumers to make sense of. For example, Google smartly created Gmail way back in the Stone Age, and now has established a huge base of users: 288 million unique Globally and 80 million domestically. This was the beginning of Google’s plan to create ubiquity and drive users to link up to all of Google’s other services – Google Docs (now Drive), Google Calendar, Maps, etc. For those who selected Android as their mobile platform of choice, the Google app integrations were a seamless experience – and only further promoted the cementing of those users into Google’s eco-system. But what about iPhone users like me? For us, there are options, but we are not getting the full value of the Google app offerings while stuck inside of the Apple world. Sure, Apple has created their own versions of each of these tools, and some are inferior – so we are forced to work in a fragmented world, patching together a series of tools based on familiarity and paths of least resistance. God forbid a better mousetrap comes along that is not compatible, and we are left with being left out – and resentful of this rut we have been wedged into without our consent.
Open Source or Closed Gate?
This issue gets even more complicated when we layer in the different approaches that these platform giants take when it comes to their systems. Apple is a notoriously over-controlling landlord, and has strict rules as to how users can personalize, customize and change their devices (simple: they can’t). This approach was driven by Jobs’ vision that Apple knows how to best manage their world, users are going to be thrilled with their choices and all will be good on the planet. And as they do a great job for the most part, the majority of their users are satisfied with Apple’s governing style. Google took the opposite approach: Lets create a world that anyone can modify, personalize and customize. Lets let developers use our world as a playground and work with users to make the best end-result. This has its obvious benefits as well as some annoying issues: crappy apps fill the store, OS fragmentation is rife – wreaking havoc on the consumers choices and options, and the experience is inconsistent. But it’s really innovative. But they are still stuck.
These platform firewalls are only getting more defined, and as more and more device choices come to market, and consumers are lured into considering their options, its getting harder and harder to keep hold on brand loyalty. So who pays the price?
1) We do. If we are committed to a device, we are going to see things in the market that we cannot have or take full advantage of – be left peering into to the store window with our faces pressed up to the glass looking at cool stuff that we just can’t use. And if we want to make the jump from OS to OS, we will have to endure the pain of migration: like switching banks, tantamount to root canal surgery. So, as the market matures, and newer cooler and more functional stuff comes online, we will all be forced into this position at some point.
2) The Platforms do. I am sure that Google, Apple and their ilk are all snickering and hand wringing over this grand scheme that they have perpetrated but they lose, too. While they maintain retention (and mind you, retention and loyalty are not the same thing – I am not “loyal” if I am trapped), they lose opportunities for growth. Within a year, everyone will own a smartphone, an by virtue of their device selection they will have by default committed to a platform (whether they know it or not). Because carrier contracts last 2 years, that gives users ample time to entrench themselves into their selected platform (reads like an evil conspiracy, I know) and hence be far less inclined to switch. So, NEW customers are going to be harder and harder for these guys to capture. They are going to be cannibalized by their own design.
3) Carriers do. So what? Who cares? We all hate the damn carriers anyway. But nonetheless, they will have a hard time getting new customers for the same reason. Even with number porting, until the carriers offer the same features, people will stay on their carrier even though it can be like chaining oneself to a rotting, infected corpse. (Still think I don’t like the carriers?).
4) Enterprises do. This is a growing issue. BYOD is now on the rise at Corporations, which is creating a slew of issues (more on this topic in my next post) ranging from security, privacy, IT support, Device Management, etc. Many of these companies are being forced into this position as more and more executives are also locked into these eco-systems and don’t want to be forced to have to switch over to another – or, be forced to carry around 2 (sometimes 3) devices. As a result, an entire industry has been created around Mobile Device Management to build a working infrastructure around platform fragmentation. This becomes an insidious process – spreading throughout the IT infrastructure via Security, Privacy, Storage, Retrieval, App Store management, Application versioning and messaging systems.
In the end, this issue does not seem to be improving. With the announcement of the new Blackberry “platform” last week, and the huge push by Microsoft to maintain their chokehold on businesses, the game of platform indispensability will only continue.
Well, time to run, as my iPhone, iPad and iMessage app are all sending me the same message. Need to go decide which one to respond to.
Back in October, I had the privilege of presenting at the MXM Branded App Show Off during Ad Week. http://www.mediacrossmedia.com/mxm_series/nyc/oct_1_2012_branded_app/. Matt Snyder has been doing a great job in establishing the Mobile Monday’s event – and seeding the mobile community here in NY. He worked with the different mobile associations of NYC and put together this event specifically for Advertising Week. According to his YouTube page, “the goal of this event is to create an opportunity for the community to learn about the best Apps for brand marketing build by developers, agencies and marketers in NYC”. The event featured 7 different Branded Apps presented to the audience while being moderated by a panel of 8 judges. The event took place at Union Square Ball Room on Oct 1st 2012.
Here’s a recap of the event: (you can also see some photos of the event on his Facebook page here. https://www.facebook.com/media/set/?set=a.436505746386162.89136.151610504875689&type=1
There were roughly 600 people in attendance. The 7 app presenters were apparently selected from roughly 50 registrants. The parameters for consideration were that the apps being showcased had to be designed for the purposes of promoting a specific brand – and for building the business of said brand. The event kicked off with a standard opening networking reception and bar schmooze – followed by intros from the hosts. Next were the presentations/demos – in a “battle of the brand” type showcase – by the selected Branded App presenters – that were moderated by a panel of judges:
- David Berkowitz- 360i
- Scott Jensen – MTV
- Taynah Reis – GDI
- Andrew Reis – SamStella
- Jake Ward – App Developers Alliance
- Timothy Ware – WSJ
- Chad Mumm – The Verge
- Richard Ting – R/GA
The 7 Branded App presenters were:
- Northface – Northface was the winner of this App –Off event.
- Duracell Powermat- Powermaster app – Provides a means by which consumers can not only monitor their current battery power, but also allows users to find Powermat HotSpot locations nearby AND also “nominate” places that they want to be HoptSpot enabled. This is a Social Gaming feature that drives advocacy and recruits users as a part of a grid-building movement to spread the word of wireless power. It features full social integrations and a badge winning program with leaderboard.
- Disney Parks – This app won the “Audience Award”.
- Girl Scouts
Each presenter walked the panel through the app and its features and were asked to focus on these points in the presentation:
- What were the core business goals for the app?
- What you did to build the Brand, and achieve those goals
- What was the effect of your efforts- brand value
- Any audience or ROI figures you could share
- Did your brand marketing effort lead to actual purchases or sales of the product and why.
- How did awareness get converted into ( for example) intent, purchase, support, loyalty and advocacy for the Brand.
- Any lessons learnt
Overall, it was a pretty diverse grouping of brands and approaches. Overall, what was clear is that mobile apps are still a tactic that demands innovation. Just making an app is no longer enough. I see 7 key things that are MUSTs for successful apps:
Content – App must either solve a real problem for the user – or must be a highly addictive time waster.
Functionality- Simply put, the app must work. i.e., if there’s a bar code scanner- it should open smoothly and connect to the desired content with no hiccups or issues; if it’s got an mCommerce store, it needs to close the sale for the user seamlessly and smoothly.
Design- it has to look good. Apps are getting sexier and sexier – and consumers want innovation and sleek design.
Usability – Kind of like Functionality – but this is more about how intuitive the app is – button sizes, locations of elements, user flow from screen to screen – placement of content on screen, etc.
Information Architecture – The logic of the navigation needs to be well thought out so it syncs up in a natural flow.
User Input- It needs to be easy for users to enter information into the app where required. Some apps are now auto-filling content or have great image recognition technology that can read credit cards.
Mobile Context – Where and when is the user using the app? Does the app take into consideration the location/time/activity/history/preferences of the user? This makes the app experience more personal and relevant.
Trust – Security – Does the user feel comfortable entering data into the app? How will it be used?