Tagged: iOS Toggle Comment Threads | Keyboard Shortcuts

  • feedwordpress 05:15:45 on 2015/01/12 Permalink
    Tags: , app store, , , , , iOS, , , ,   

    App Stores Must Go 

    The post App Stores Must Go appeared first on John Battelle's Search Blog.

    appstores2014 was the year the industry woke up to the power of mobile app installs, and the advertising platforms that drive them. Facebook’s impressive mobile revenue numbers – 66% of its Q3 2014 revenue and growing  – are a proxy for the mobile economy at large, and while the company doesn’t divulge what percentage of that revenue is app install advertising, estimates range from a third to a half – which means that Facebook made anywhere from $700 million to more than a billion dollars in one quarter on app install advertising. That’s potentially $4 billion+ a year of app installs, just on Facebook. Yow. That kind of growth is reminiscent of search revenues a decade ago.

    But as I’ve written before, app installs are only the beginning of an ongoing marketing relationship that an app publisher must have with its consumer. It’s one thing to get your app installed, but quite another to get people to keep opening it, using it, and ultimately, doing things that create revenue for you. The next step after app install revenue is “app re-engagement,” and the battle to win this emerging category is already underway, with all the major platforms (Twitter, Yahoo, Google, Facebook) rolling out products, and a slew of startups vying for share (and M&A glory, I’d wager).

    Over time, app install revenue is bound to wane, and app re-engagement revenue will wax, to the point where the latter is inevitably larger than the former. Neither will disappear entirely, of course, but as the mobile model matures, it’s likely they will take new form. But the following three steps will remain constant – they were true before apps (when we called Internet services “websites”), and they were true before the Internet itself:

    1. Get people to notice your product or service, and engage with it for the first time. 
    2. Get people to come back, and keep sampling your product or service. 
    3. Get people to regularly give you their money for your product or service.

    We’ve now got a reliable model for #1: It’s the combination of the app store platform and app install advertising. #2 is coming along as well, as I mentioned above.

    But what of #3? It’s one thing to get someone to give you a few bucks for your app, but how can you keep them giving you money (or doing things that make you money, like ordering on GrubHub)? If app makers are spending an unhealthy percentage of their capital on advertising, innovation in product will suffer, and we won’t get apps that people are willing to continually pay for. It strikes me, after any number of conversations I’ve had around the state of mobile, that mobile markets in the US will slowly but surely evolve toward the norms currently in place in Asia, where advertising is a minority of mobile revenues, and in-app commerce of all kinds is the standard. After all, that’s how it is for business in general – advertising is a small but significant percentage of overall revenues.

    But for this to occur, our process of app discovery and engagement has to rationalize – it’s simply too expensive to build a loyal audience in mobile, and the top 1-2% of apps can afford to price the rest of the market out. This is the great failure – or cynical intention – of Apple and Google’s hobbled app store strategy. There simply should not be one app store per platform – they’re what Steve Jobs would call “orifices” – monopolistic constructs created to consolidate control. App stores stifle innovation – they are damage, and the Internet will eventually route around them. 2015 should be the year that becomes evident.

    My other recent musings on mobile can be found here.  

    The post App Stores Must Go appeared first on John Battelle's Search Blog.

     
  • feedwordpress 23:17:03 on 2014/10/05 Permalink
    Tags: alex austin, , , , , iOS, , mobile quickening, ,   

    The Next Stage of Mobile Quickening: Links Get Intelligent 

    The post The Next Stage of Mobile Quickening: Links Get Intelligent appeared first on John Battelle's Search Blog.

    HowItWorks

    How Branch Metrics works…click to enlarge.

    Early in a conversation with Alex Austin, CEO of mobile startup Branch Metrics, I had to interrupt and ask what seemed like a really dumb question. “So, wait, Alex, you’re telling me that the essence of your company’s solution is that it….makes sure a link works?”

    Alex had heard the question before. But yes, in truth, what his company specializes in is making sure that a link works in a very particular kind of mobile use case. And doing so is a lot harder than it might seem, he added. Branch Metrics, a three-year old startup that began as a way to create and share photo albums from your iPhone, is now devoted entirely to solving what should be a dead easy problem, but thanks to the way the mobile ecosystem has played out, it’s just not. (Alex has written up a great overview of his journey at Branch, worth reading here).

    A month or so I wrote Early Lessons From My Mobile Deep Dive: The Quickening Is Nigh, an overview of my initial learnings as I explored today’s mobile landscape. A major conclusion: the emergence of deep linking is leading to entirely new opportunities in mobile, and the mobile marketing machine is a key place to explore if you want to understand the implications.

    Since then, I’ve spent more time talking to folks like Alex, and I’ve come to another conclusion: the next step in the mobile quickening will be intelligent links.

    Now, before you go Googling “intelligent links” – I’ll admit there is no clear nomenclature per se, because in the past we’ve not had a need for such a distinction. After all, on the open web, all links can be intelligent, because they can pass information from site to site via cookies, redirects, and various increasingly sophisticated hacks.

    Not so in mobile.

    In his wonderful post outlining Branch’s initial failures and eventual pivot, Alex notes: “The biggest growth issue we faced in our mobile app was the fact that Apple doesn’t let you track users and pass context through the install process. …To break down this barrier would mean making the mobile app ecosystem more like the functionality we’re used to on the web.”

    So that’s what Branch set out to do – in essence, to make mobile work more like the web. Branch’s initial photo book product may have failed for any number of reasons, but what stood out for Alex was how hard it was for the product to self-replicate across a customer base. A customer would create a cool photo book, and then want to share it with a friend. Of course, the best way to share is via a link to the photo book – that’s the viral calling card. But when a friend clicks on the link, Branch ran into the limits of mobile apps. It gets kind of convoluted, so let me break it down in steps:

    1. Customer downloads Branch and uses it to create a cool photo book.

    2. Customer wants to share the photo book with her friends, which she does using Branch’s internal sharing features.

    3. Branch’s sharing features generate a deep link that is sent via email (or a Tweet, or Facebook, etc).

    4. Friend receives invitation via email to check out a cool photo book.

    5. Friend clicks on Branch’s deep link.

    6. Friend does NOT have Branch’s app installed, so is linked to the Branch app download landing page in the iTunes store.

    **THIS IS FRICTION POINT #1. In an ideal world, a potential customer should not have to go through the Apple app store just to view a cool media object that’s been shared (this wouldn’t happen on the web). **

    7. Friend decides to download the app, tells Apple OK, accepts the app’s terms and services, fires up the app, and….

    8. Sees the generic welcome screen that the app brings up for every new user. Now he has to create a new account, set a password, etc. Confused, he wonders whatever happened to the photo book he was looking for.

    **THIS IS FRICTION POINT #2. The friend just wanted to check out the cool photo book, but the information of the original URL, which pointed to the actual media object, has been lost.**

    9. Friend is confused as how to actually use the Branch app to see his friend’s cool photo book. He pokes around a bit, but quickly loses interest when he sees a new notification from SnapChat, or Facebook, or whatever.

    10. Friend never becomes a new customer of Branch, nor ever actually sees the photo book.

    This is a deeply lame experience, and one that seriously limits any app developer’s business. “You can’t have someone have to type their password in, and go through a long install and configuration to start using the app,” Alex told me.

    So Branch pivoted, and created a lightweight SDK (software development kit) that, when installed by the app maker, allows the media object in question to appear once the app is installed.

    Sounds super simple, but according to Alex, it was quite complicated, not least because getting app makers to install SDKs is non-trivial. However, Branch is finding traction with scores of app makers because the company solves a major marketing problem in mobile – how to create more fluid conversion and engagement paths which ultimately lead to more customers.

    This is the evolution of the intelligent mobile link – something that’s sorely needed in the mobile ecosystem. It all starts with the ability to pass data through a link – something that Apple has not allowed in the past. But Branch’s elegant hack around Apple’s shortsighted policy is one more important step toward creating a truly mobile web, one that combines the richness and device-specific capabilities of an app with the universality of an open web architecture.

    “It’s like 1995″ in mobile apps, Alex concluded. “We are just figuring out how to turn on the Internet on the phone.”

    When I start to think about where this goes from here, I start to get very excited – intelligent links are the beginning of a whole new mobile experience. The next step is to break down the hegemony of the app store itself – why should we have to go through an authentication, download, and configuration process just to see what’s behind a link? We shouldn’t, and soon, I imagine we won’t. Of course this has serious implications for the hegemonies of Apple and Google’s app store choke points, but in the end, both companies are all about creating great experiences for their users, right?

    Take it one step beyond erasing the app store friction, and we can imagine a world where apps work like always on-call services, at the ready to execute their portion of a fluid user experience. Explaining that experience will be the subject of a future post. But for now,  amen for folks like Alex and companies like Branch Metrics. Keep up the good work.

    The post The Next Stage of Mobile Quickening: Links Get Intelligent appeared first on John Battelle's Search Blog.

     
  • feedwordpress 23:24:00 on 2014/08/18 Permalink
    Tags: , appboy, , , , , , iOS, Kahuna, , mobile development, , URX   

    Why I’m Watching Deep Linking In Mobile 

    The post Why I’m Watching Deep Linking In Mobile appeared first on John Battelle's Search Blog.

    first web page

    The first ever web page, created by Sir Tim Berners Lee to explain, naturally, the WWW.

    We are at a turning point in the mobile app ecosystem where deeplinking is becoming a priority and not just a feature.URX blog

    This week marks the beginning of a journey I’m taking to understand “deep linking” in mobile. I’ve kept one eye on the space for some time, but it’s clearly heating up. Last Spring three major mobile players – Facebook, Google, and Apple – all announced significant developments in deep linking. Twitter has also fortified its deep linking capabilities of late, as has Yahoo.

    Most of these major players are supporting deep linking for commercial reasons – their business is driven by advertising, and a huge cut of mobile advertising revenues are in turn driven by app installs. Marketers want to be able to link directly to specific places inside their apps, so they can drive qualified leads to convert (and measure effectiveness/optimize campaigns). To be clear, these are the ads that show up inside apps on your mobile phone encouraging you to download a free game or service. These install ads make up a huge percentage of mobile advertising revenue, though it’s hard to find hard figures for exactly what percentage. Current estimates range between 30 and 50% - either way, that makes them the largest category of mobile advertising, period.

    This all reminds me of how search played out on the desktop Web – search was a huge percentage of overall “online advertising” revenues in the early days, but it took a while before analysts started breaking search out as a category independent of “online advertising.” Twenty years into search, that category still represents more than 40% of all online ad revenues. So yep, I’m watching deep linking, because I think there’s a big there there.

    But there’s a funny hitch to the evolution of linking inside our mobile ecosystem. On the Web, the link is pretty much the atomic unit of value – from the get go, *anyone* could create a link from one web page to another. The web was built on links, and in the early days those links were built, for the most part, by *users* of the web – people like you and me. We built link-heavy websites, we blogged and linked profusely, we emailed links around, and in doing so we connected static web pages one to another, all in the name of navigation, discovery, and ease of use. It was only later, as search rose to prominence and people started to realize the commercial value of links, that the SEO industry became a commercial monster. In short, linking behavior predated commercial exploitation.

    But in the mobile web, commercial exploitation is driving linking behavior, and I find that fascinating. Certainly there’s any number of reasons for this, from Apple’s early iOS design decisions to the fact that apps are, for the most part, personalized experiences that are not driven by the early web’s model of static pages meant for consumption by any and all comers. Regardless, I’ve got a hunch about deep linking - I’m hoping it’s the seedbed for a major shift in how we experience mobile computing. For now, mobile deep linking is the purview of developers and savvy mobile marketers. But I think in time this may change. I wrote a bit about that hunch here:

    …while developer-driven deep links are great, the next step in mobile won’t really take off until average folks like you and I can easily create and share our own links within apps. Once the “consumers” start creating links, mobile will finally break out of this ridiculous pre-web phase it’s been stuck in for the past seven or so years, and we’ll see a mobile web worthy of its potential.

    I imagine a time when applications encourage their users to share links from inside apps, and everyone finds that sharing behavior will create a positive feedback loop similar to the one that drove the rise of the original Web. From there, any number of innovations will arise, speculating on what those might be is worthy of several future posts.

    For now, I’ve come across a crop of startups focusing on deep linking as well various industry efforts in the field (I have Semil Shah and Roy Bahat, among others, to thank for my early lessons in the space). In the coming weeks, I’m meeting with many of them, including URX, Kahuna, DeeplinkAppboy and several stealth startups, and of course larger players like Twitter. As I get smart, and if I find interesting stuff, I’ll report back here. In the meantime, if you’ve got any suggestions for me, please leave them in comments or ping me on Twitter. Thanks!

    The post Why I’m Watching Deep Linking In Mobile appeared first on John Battelle's Search Blog.

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
esc
cancel