I’ve come across any number of interesting startups in my ongoing grok of the mobile world (related posts: 1, 2, 3). And the pace has quickened as founders have begun to reach out to me to share their work. As you might expect, there’s a large group of folks building ambitious stuff – services that assume the current hegemony in mobile won’t stand for much longer. These I find fascinating – and worthy of deeper dives.
First up is Jack Mobile, a stealthy search startup founded a year or so ago by Charles Jolley, previously at Facebook and Apple, and Mike Hanson, a senior engineer at Mozilla and Cisco who early in his career wrote version 1.0 of the Sherlock search app for Apple. Jack was funded early this year by Greylock, where Mike was an EIR.
I’d link to something about Jack – but there’s pretty much nothing save a single page asking “What Is Jack?” Now that Charles and Mike have given me a peek into what Jack is in fact all about, I can report that it’s fascinating stuff, and at its heart is the problem of search in a post web world, followed quite directly by the problem of search’s UI overall. Whn you break free from the assumptions of sitting at a desk in front of a PC, what might search look like? What is search when your device is a phone, or a watch, or embedded in your clothing or the air around you?
Jack is trying to answer that question, and the team is rethinking some core user interface assumptions along the way.
Search on mobile is by almost any measure broken – the core assumptions of what makes search work on the web are absent on your device. On your phone, there are no links to index, no publicly accessible commons of web pages to crawl and analyze. Just a phalanx of isolated chiclets – disconnected apps, each focused on a particular service. But that doesn’t mean we don’t need to search in mobile, in fact, we search a lot on our phones. But the results we get ain’t that great. In the main, that’s because when we search on our phone, we get answers from…the web. But as Jolley and Hanson pointed out, answers from the web often fail when presented to us in the context of mobile.
Mobile search queries are just…different. Let’s explore why:
– Context. When you search on your phone (or later, on any “liberated” device), you’re more likely than not in completely different context from when you’re “on the web.” Mobile searches tend to be service related – “How do I get to this address,” and/or location driven: “What are good nightspots nearby.”
– Query & Corpus. Because of this context, *what* we want to search is focused in a far smaller potential corpus of material. Mobile searches tend to have one exact answer – we aren’t loking for a list of links that we then want to peruse, we want an answer to a specific contextual question – mobile searches bias toward service and action as the query result. That means search’s presumptive barrier of completeness (the cost Google bears of keeping the entire Internet in RAM, for example) is not a barrier on mobile. You don’t have to have ALL the possible information “indexed” – just the right information. And what information is that? Well, that leads us to ….
– Signal. With mobile, rich new signals are available that could (and should) inform search results (but don’t). Certainly the most robust such signal is your current location, but that’s just the start. Others include your location history (where you’ve been), the apps loaded on your phone, your usage history with those apps, and the structure inherent in those apps to begin with. Which begs a huge possible difference in…
– User Interface. Search on mobile, for now, is identical to search on the web. It’s a command line interface, where you type in your query, and you get blue links for results. Google’s been working hard to address this, and the combination of its universal search product, which surfaces “one true answer”, with voice search, is a real step forward. But the folks at Jack showed me another potential search interface for mobile, and I found it quite compelling. That approach? Well, I’d call it “conversational.”
The Conversational Search Interface
Way back in 2004 I met with Gary Flake, then a senior technology executive at Overture, a leading search firm of the day (Yahoo! later acquired Overture, which fueled Yahoo!’s search results until the Microsoft deal in 2009.) Even way back then, before mobile was a thing, I was frustrated with search’s interface.
I asked him why we couldn’t move forward in search interface – the “ten blue links” approach was so … flat. I wanted to ask one question, get results, and then ask another. Or better yet, I wanted the service to ask me a question – “You entered ‘Jaguars’ – did you mean the football team, the car, the cats, or something else?” Gary looked at me ruefully and said something I’ve never forgotten: “If only I had just one modal dialog box…”
What he meant was that search, at that point, was a race for the best ten blue links, and anything that got in the way of that, like a modal dialog box that popped up and asked a refining question, would mean that a very large percentage of folks would abandon the search. And abandonment of the search meant loss of revenue.
But that idea – of search as a series of back and forth exchanges, a conversation if you will – has always stuck with me. So imagine my surprise when Jolley and Hanson showed me a very early prototype of Jack Mobile’s search interface and it looked like….a conversation!
Jolley and Hanson have asked me to not report the details of their prototype interface, but suffice to say, it’s quite different, and it looks and feels far more like a back and forth than anything on the web. It’s delightful, and using the service is also cool. Jack knows where you are, so if you ask it “Guardians of the Galaxy” it’ll find showtimes near where you are, and return that information as the result. If you ask it “Italian restaurants,” Jack won’t give you a list of places with the most Google+ reviews – it’ll give you highly rated eateries near where you are right now, perhaps enhanced by reviews relevant to you given the fact that you have the GrubHub or OpenTable app on your phone.
Jack is still in very early stages, but the co-founders had a number of key insights from their work so far. The first has to do with completeness – while long tail edge cases rule the roost in web search, mobile has far more distribution of “head end” search – which means you can narrow your indexing and your algorithms and still satisfy a large majority of queries.
Also, mobile search is deeply personal – there’s almost no such thing as one size fits all result. In mobile, results should be rewarded because they are the most likely answer, not because a ranking system has pre-determined them as most authoritative. Searching for “BMW 3 series” while standing at a Mercedes dealership should most certainly bring a different result than the same search from a Taco Bell on Interstate 5. While personalized search has become a mainstream attribute of Google, the truth is, it’s quite shallow – on the web, Google knows precious little about you. But your phone knows quite a bit. Unlocking all that data is still too hard, but it’s coming.
But perhaps the most interesting implication of Jack’s approach to search lies in how it might drive a new ecosystem between “publishers” and “audience members.” Web search, Hanson points out, is all about the consumer – the creator of the web page is a second-class citizen, stuck in a suckers’ deal of sorts: You have to “publish” your presence on the web, or risk irrelevance, but you are entirely at the mercy of black box forces you don’t understand when it comes to how people might find you. Hanson posits a different model for Jack’s index, one in which publishers deliver their app and content structures to Jack via a proprietary feed of discrete, small units tagged to specific query types. If this sounds a bit like semantic search, well it is. Hanson, a veteran of open web standards fights via his work at Mozilla, told me he has “deep scar tissue” around the topic, but at the same time, he and Jolley sense that with mobile, a new kind of level playing field just might allow semantic, personalized search to truly emerge.
There are far more questions than answers hanging over Jack, but that’s why it’s interesting – here’s a small, well funded team of search, web, and mobile experts really leaning into a new way to think about a massive problem/opportunity set. It’s certainly one to watch in 2015.
5 thoughts on “What Will Search Look Like In Mobile? A Visit With Jack”
Thank you, John, for such an in-depth, precise and thorough review of the state of mobi vs. web search (and introduction to some aspects of Jack Mobile). Precise? Well, you stated: “Search on mobile is by almost any measure broken – the core assumptions of what makes search work on the web are absent on your device.” Bingo!
Sadly, this is the direction we’re heading — when ego & instant gratification reign. I recommend the following:
Many thanks to John problems are considered in depth and very accurate overall mood. Search on websie the phone will be immediate measures, we should have an online search for the phone
Worthy pursuit – mobile search!
Perhaps this explains why Apple has chosen not to invest in building a competing search engine, they forsee Nex-Gen mobile search really more device (context) and UI driven.