\documentclass[10pt]{article}

\usepackage{fullpage}
\usepackage{setspace}
\usepackage{parskip}
\usepackage{titlesec}
\usepackage[section]{placeins}
\usepackage{xcolor}
\usepackage{breakcites}
\usepackage{lineno}
\usepackage{hyphenat}





\PassOptionsToPackage{hyphens}{url}
\usepackage[colorlinks = true,
            linkcolor = blue,
            urlcolor  = blue,
            citecolor = blue,
            anchorcolor = blue]{hyperref}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother


\usepackage[round]{natbib}
\let\cite\citep




\renewenvironment{abstract}
  {{\bfseries\noindent{\abstractname}\par\nobreak}\footnotesize}
  {\bigskip}

\titlespacing{\section}{0pt}{*3}{*1}
\titlespacing{\subsection}{0pt}{*2}{*0.5}
\titlespacing{\subsubsection}{0pt}{*1.5}{0pt}


\usepackage{authblk}


\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}%

\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[english]{babel}










\begin{document}

\title{23andme's API\ldots{}}



\author[1]{John Wilbanks}%
\affil[1]{DEL-FI}%


\vspace{-1em}



  
  \date{May 22, 2024}


\begingroup
\let\center\flushleft
\let\endcenter\endflushleft
\maketitle
\endgroup








\sloppy


So, big news today in the DTC genomics world was that 23andme has
decided to publish an API. The blog announcement optimistically
announces that there is ``no monopoly on great ideas''and encourages
developers to apply for access to write applications to the API.

I've gotten quite a few requests for my thoughts on the announcement.

I'm torn between wanting to praise 23andme and wanting to scream DANGER
DANGER DANGER at the top of my lungs. So, I'm going to do both.

First, bravo. Publishing an API is smart business move for 23andme, and
holds the potential to create a lot of genomics apps on the data they
hold.

Second, DANGER. Publishing an API is a smart business move. Let me
repeat that: it's a business move. It's not because they're nice.

There is a very serious difference between ``we've opened our API to
you'' and freedom. Developers must apply for permission to make
applications. Developers must tell 23andme, before developing, what
their apps will do. And there is nothing that prevents the strategic
shrinking of an API, or the subtle or not so subtle pressure to turn off
applications that compete with core business functions or revenues of
23andme. '

The fundamental problem is monetization. If you write an awesome app to
a closed API, it makes good business sense to give you the Sopranos
treatment. You make the app, it gets popular, you get the bust out.

Twitter started with a wide open API and is basically phasing it out.
Sucks if you invested your time there. Or if you're like Dalton
Caldwell, being strongarmed by Facebook when his app competed with FB's
App Center.

So that's the fundamental thing. Develop to a corporate API knowing full
well that if you are successful, there's a better chance that you wind
up Scaltino and not Zuckerberg. And despite all the press that App.net
is getting now, remember that social networks achieve network effects
before they shut down functions in the API. And once a social network
gets to that network effect, it's very hard to build a competitor from
the open.

Anyone out there use Diaspora? Didn't think so.

Code carefully, my friends. And choose your monopolies wisely.

\selectlanguage{english}
\FloatBarrier
\end{document}

