Contrasting Apple and Alphabet’s Approaches to Healthcare

A little while ago, I wrote a post on tech companies’ efforts in the education sector and how I felt they were lacking (I subsequently wrote a follow-up post about Apple’s Swift Playgrounds app being a step in the right direction). In that post, I mentioned there were other areas where large tech companies appeared to be making significant bets, including healthcare. Today, I wanted to dive deeper into that area, since we’ve seen another big partnership announcement from Alphabet’s Verily division this week and we’re also fresh off a set of announcements about the Apple Watch last week.

Alphabet’s Verily Bet

One of the more prominent and established “Other Bets” at Google’s parent company Alphabet is Verily, its life sciences division. It’s one of the three Other Bets said to be generating meaningful revenue, along with Nest and Google Fiber. But it’s also very unlike those other two businesses, in that it’s not a consumer-facing product or service company. Rather, Verily has been mostly developing technologies and then partnering with other established firms which can provide the clinical, research, and marketing expertise to take inventions to market. So far, Verily (and its predecessor, Google Life Sciences) has announced several of these partnerships with various companies, as shown in the table below:

verily-partnerships

What’s interesting about Alphabet’s approach is it is diving very deep into specialized areas within healthcare, developing technology designed to diagnose and treat specific conditions. Several of the partnerships outlined above are focused on diabetes specifically, for example – this isn’t about general purpose technology being applied to healthcare as an afterthought. That makes Alphabet somewhat unique among big generalized tech companies, most of whom have lent more generic technology to the specialists rather than diving deep themselves. The business models are also curious, featuring a mix of joint ventures, licensing payments, and others. And of course, most of these projects are expected to take years to produce results, in keeping with the normal development cycles for clinical treatments.

If you read enough about Verily’s various efforts, you’ll also find some skepticism from experts in the field. Some of this can be written off as sour grapes from would-be partners, but some of it also comes from people Alphabet has actively consulted on its various efforts and who have come away unimpressed. The main focus of Alphabet’s diabetes work is on miniaturization technology and its partners have spoken highly of its efforts there, but some of its approaches have been tried before and failed, so it will be interesting to see how the contact lenses effort, for example, pans out.

Apple’s ResearchKit and HealthKit

When Apple first announced ResearchKit, I wrote it up as a unique approach to healthcare, though very different from Google’s. Whereas Google’s approach is to work in a very direct fashion on specific, narrow fields within healthcare, Apple’s approach has been to leverage its general purpose technology to help doctors and research institutions do what they do more easily and consistently, all the while making life easier for the patient or research subject. Having covered enterprise service providers for a long time, I found it striking Apple had turned the usual model on its head by focusing on the end user – the patient – rather than the institutions.

This approach, too, has pros and cons. On the plus side, Apple makes its massive installed base of devices, including a growing base of Apple Watches, available as conduits for collecting, tracking, and gathering data on various conditions as part of both treatment and research projects. What’s more, Apple isn’t charging for this capability, but is making it freely available to whoever wants to use it. On the downside, this is general purpose technology not designed for the diagnosis or treatment of specific conditions but designed first and foremost with more generic purposes such as fitness tracking in mind. As such, Apple’s approach can never go quite as deep as technology designed for narrow use cases, although we’ve already seen many applications of both HealthKit and ResearchKit from inventive researchers and care providers.

Above, I talked about the unusual business models for Verily’s various efforts but in contrast, there is no business model at all for these two initiatives from Apple, at least for now. What is clear, though, is Apple is taking this new area of R&D very seriously and Tim Cook’s recent comments about the sheer scale of the healthcare market suggests he sees a financial opportunity here too. I’m very curious to see what shape Apple’s future efforts might take – it’s easy to imagine the partnerships today with Hermès and Nike with the Apple Watch could find counterparts among the major pharmaceutical companies and healthcare systems. These partnerships might develop more specialized versions of the Apple Watch or, perhaps more likely, additional devices which could serve as accessories to the Watch or iPhone and add additional sensing and tracking capabilities. Tim Cook has already suggested he doesn’t want to have to put the Watch itself through the FDA approval process, but these other devices might be better suited for that route.

Doing Good a Motivating Factor

While I’ve focused on the structures and business models of Alphabet’s and Apple’s healthcare initiatives, it’s clear there’s more than just financial incentives at play. If you listen to executives from either Apple or Verily, it becomes clear they’re motivated by a desire to do good in the world. As I’ve mentioned in several previous posts, I believe big tech companies have a duty to use their technological expertise to move the world forward in meaningful ways, changing lives for the better and solving significant problems. It’s great to see both these companies operating in this way. And I’d be remiss if I neglected to acknowledge that these are far from the only two big tech companies doing good work here – I simply wanted to focus on these two today, to keep things simple.

Published by

Jan Dawson

Jan Dawson is Founder and Chief Analyst at Jackdaw Research, a technology research and consulting firm focused on consumer technology. During his sixteen years as a technology analyst, Jan has covered everything from DSL to LTE, and from policy and regulation to smartphones and tablets. As such, he brings a unique perspective to the consumer technology space, pulling together insights on communications and content services, device hardware and software, and online services to provide big-picture market analysis and strategic advice to his clients. Jan has worked with many of the world’s largest operators, device and infrastructure vendors, online service providers and others to shape their strategies and help them understand the market. Prior to founding Jackdaw, Jan worked at Ovum for a number of years, most recently as Chief Telecoms Analyst, responsible for Ovum’s telecoms research agenda globally.

15 thoughts on “Contrasting Apple and Alphabet’s Approaches to Healthcare”

  1. Such an Apple slant. Why?

    You correctly point out Apple’s ubiquity as a benefit. Doesn’t Android have something close to 4x the ubiquity? No mention of that. Also no mention of Android’s multi vendor benefits over Apple’s single vendor device supply.

    Absolutely correct that Apple’s devices, under Apple’s current practices, cannot be used to treat any disease for most classes of medical devices. Doing so requires full disclosure to FDA that the entirely of the system is both safe and effective. This would include both hardware and software.

    I don’t see Apple opening up to that degree for anyone.
    Google doesn’t have that problem

    1. I don’t think this article is an Android vs. Apple. Nor is it about secrecy because you can disclose to the FDA without telling the rest of the world about the details of your hardware and software.

      The article is just about two different approaches.

      Google’s approach seems to be the more common one among healthcare startups. Startups with promising technologies often partner with larger and more experienced Pharma companies to bring their products to market. The interesting thing is that Google’s approach is not necessarily utilising their expertise in large data, or exploiting the huge Android user base, but more dependent on miniaturisation.

      Apple’s approach is more unique, and it would be interesting to see where they want to take it. It also makes use of Apple’s large user base and their privacy stance. There is obvious synergy. Google could take Apple’s approach of course, assuming that they could manage the privacy issues.

      1. “I don’t think this article is an Android vs. Apple.”

        Most respectfully, the title is…
        Contrasting Apple and Alphabet’s Approaches to Healthcare

        “Nor is it about secrecy because you can disclose to the FDA”
        Yeah, I don’t think APple wants to do that, never mind the rest of the world.

        1. It may be an Alphabet vs. Apple article, but it’s not Android vs. iPhone.

          Actually, that’s what’s interesting. Apple is building their healthcare efforts on top of their most successful business. Google on the other hand, is not building their healthcare efforts upon Search nor Android nor Maps nor YouTube. I see no synergies with other parts of Aplphabet’s businesses.

          1. Will Healthkit run on Android, Windows, Linux? If not, I don’t know how it cannot be iOS (not iPhone) versus Android. Until I’m proven to be wrong, this smells to me as a means of “forcing” people into iOS.

            If you’ll indulge me in a little macabre humor…
            I’m certain some folks would tell me that I have a choice, iOS or die… 😉

          2. I don’t necessarily disagree that using HealthKit to force people to move to iOS may be one of the monetisation strategies for Apple’s health efforts.

            Actually, it’s the monetisation side that I have trouble seeing. For Alphabet, it’s simple because it’s an old fashioned monetisation strategy. For Apple, it’s less clear.

          3. I thought I thought some (all?) aspects of HealthKit were open source. I seem to recall that been announced when Apple introduced HealthKit. Please clarify if I am incorrect.

          4. I don’t think that being open-source or not is much of an issue. A software giant like Google should easily be able to create a HealthKit clone if they wanted too.

            If Google is hesitating to clone HealthKit, it might be because of encryption. Apple encrypts HealthKit data so that even Apple can’t see it. It might not be in Google’s interest to match that.

      2. I find the Airpods interesting re: healthcare. The Airpods are obviously more than just wireless earbuds, they’re part of Apple building out a wearable platform, what I’ve been calling the Apple Network of Things. The ear is a great place for health related sensors.

        1. Agree, and what’s left to be seen is whether it will now become acceptable to keep your AirPods in your ears when you’re supposed to be listening to someone. Will the tolerance be higher than for Google Glass.

          1. The tolerance should be higher than for Google Glass, since an Airpod is far less intrusive. But I see this as a network of wearables, you’ll be able to pop the Airpods out and have the Apple Watch notify you via the taptic engine on your wrist, and if it’s something important you can take a moment and insert one Airpod. It’s going to be very useful having Siri right in your ear.

    2. No Apple slant here – just presenting the pros and cons of both approaches. To date, Google hasn’t attempted anything like HealthKit or ResearchKit with Android – should it choose to do so, that could be very impactful, but it simply hasn’t, so its ubiquity is irrelevant in this discussion. I’m focused on what the companies are doing today and have indicated they may do in future.

Leave a Reply

Your email address will not be published. Required fields are marked *