Clay Tech

"clay-works make things real"

translated from clazytech.com

Xcode, Android, and Arduino Share One Future

This article was moved here from the old blog mixture-art.net, where it was written in April 2013. The style and information remain as they were at the time.

I happened to talk about this with a colleague the other day, so I thought I’d write up something I think about often.

“Freemium”

Have you heard this word?

It sounds like an economics term, but there’s nothing complicated behind it. Put simply, it’s a way of doing business that makes good use of “free.”

Chris Anderson’s “Free” is a very famous book. Fittingly, the e-book edition was itself free.

Free: How Today’s Smartest Businesses Profit by Giving Something for Nothing / Chris Anderson

I won’t go through the book in detail, but the gist is this:

some people succeed by using “free” to expand business opportunities, and others fail — squeezed out by the free economy or trapped by meaningless freebies.

image-3

The book walks through various examples and a history of how things changed. It’s a substantial read.

An example everyone knows is handing out tissues for advertising. A “now that you mention it” example is playing a song on the radio to boost sales.

The world is full of freemium models of every kind. Let me pick out a few that stand out.

In keyword order, let’s start with

Xcode

Xcode is, roughly, “a development environment for building iOS apps.” That understanding is good enough for now. (It can do plenty of other things too, but that’s not what I want to discuss here, so I’ll skip it.)

Apple built out the App Store environment around the time the iPhone 3G launched. At that point, it released Xcode for free.

iOS applications are written in a language called Objective-C. (That’s not entirely accurate, but it’s unrelated to the main point, so I’ll skip it.) It feels like a cousin of C++, but it isn’t exactly that.

For a lot of software developers, the reaction was: “Objective-C? Seriously, I don’t want to learn some new language.”

But reality moved in exactly the opposite direction. A great many software developers rushed to pick up Objective-C. The merits of the language itself mattered, but what mattered enormously was that an excellent integrated development environment, Xcode, was ready from the start.

And it was free.

You could just try it out, and if you didn’t like it, you could stop.

Everyone started out with roughly the attitude of “well, it’s new, let’s give it a shot,” and then got pulled in.

Once a market formed and its value was recognized, people with different motivations — “I want to do this as a job,” “I want to make money with apps” — started picking up Objective-C in growing numbers.

The phase had shifted to the next stage.

By becoming the de facto standard this way, Apple made it look as though it had opened up the mobile app market all by itself, when in fact countless companies and individuals, large and small, at every level of skill, had gone out and opened it up themselves, on their own initiative.

And the whole system was built so that every bit of the resulting value flowed neatly back to Apple.

image-6

A lot of app developers chasing a windfall only realized this later.

Looking at this whole flow, you have to marvel at the brilliance of the freemium move — offering an outstanding development environment like Xcode for free.

On to the next keyword.

Android

Android.

When Android was first announced, it struck people as a business that didn’t quite feel like Google. Measured by “share,” it’s been a huge success, but because the revenue model is rather roundabout, it’s genuinely hard to tell how much it actually contributes to revenue.

I hear its internal relationship with the company’s existing high-margin teams (the ad business), and with Chrome, which it directly collides with, remains awkward even now.

Now, about that roundaboutness —

what did people think when Android was first released for free?

Did they think, “Well, it’s Google, of course it’s free, naturally”?

Or did their eyes pop out: “A mobile OS, for free?!”

Before the smartphone era, Symbian and the like were the mainstream mobile OS. Handset makers using Symbian must have paid hefty deal fees to Nokia (and before that, PSION), or shared revenue in some form.

In the broader sense of “OS,” Unix/Linux is a free OS. But that was free from the start — built by volunteers, open source. Put simply: it wasn’t created for profit by some company, so of course it’s free. That’s the logic there.

Or there might have been a third reaction:

“Well, the kernel is Linux-based, so of course it’s released under the GPL.”

Some people understood things that well. But then the reverse question arises: why did Google build Android on a Linux base in the first place?

The answer is simple. The premise, from the start, was to release it for free.

Now compare this to iOS. Apple doesn’t offer iOS to anyone, anywhere, and has no intention of doing so. Of course not. It’s packed with the results of an enormous investment of time and money. Of course not.

Hmm.

It starts to get confusing, what’s right and what’s wrong here.

To understand this, you first need to grasp the premise that Google’s business model is an advertising model.

Google doesn’t run ads itself, so “how do we get as many people as possible to see our clients’ ads” is what determines Google’s revenue.

Going forward, the main stage for that “seeing” is the smartphone.

So you take an overwhelming share of that platform.

Do that, and the ad revenue should eventually follow.

That’s the gist of it. Once you unpack it, the logic is actually simple.

image-5

And indeed, Android’s share has grown explosively. No wonder — the OS was free, after all.

By the way, porting Android onto a CPU with some track record, assuming nothing especially complex is involved, feels like roughly “four people, two months.” In other words, once the parts to be used are decided, in about two months you have “a smartphone that actually works decently.”

Compare that to building an OS from scratch: “thirty people, two to three years.”

Of course people jump at that “free” option. So far, so good. The rest is monetization and verifying its effect, but given how much share it’s taken, it’s reasonable to imagine optimistically that the results won’t be too bad.

Android surely isn’t going to fold anytime soon.

As an aside, when it comes to this kind of stance toward freemium,

Japan is weak, America is strong. Frankly speaking.

I have to say, truly, “the country of BUY1GET1FREE was strong.”

Last up is

Arduino

Arduino.

You might sense this one is a little different in flavor from the other two.

A quick explanation: Arduino started out as a project for students doing experiments and prototypes, with the goal of “openly building a cheap, simple, easy-to-use platform.”

True to that word “open,” all its design information is published online. Some people use it to build and sell their own PCBs, and others build and sell entirely different derivative platforms based on Arduino.

It’s GPL — that is, copyleft — hardware.

The firmware development environment for running Arduino comes bundled with it too, and if you’ve dabbled even a little in programming, you can get a board running with just two or three lines of code. Thanks to that ease of use, it has become widely used over the past several years among media artists and aspiring media artists.

Now, that “copyleft” I mentioned earlier refers to

the dream-like arrangement where “all derivative works are OK!” Android, mentioned earlier, falls into that category too. (To be precise there are partial caveats and so on, but they don’t affect the main argument, so I’ll skip them.)

On top of that, a secondary author must permit tertiary and quaternary derivative works built on theirs. In fact, they’re expected to support it.

It’s a fairly open, generative concept, to that extent.

image-4

Unix and Linux, mentioned earlier, fall squarely into this category, and thanks to that open way of thinking, a great deal of volunteer cooperation gathered around them, resulting in an OS of sufficiently usable quality built entirely for free.

Now, why did I bother lining up these three for this theme?

I can finally get to that.

First, this notion of copyleft doesn’t apply to Xcode at all.

Apple provides Xcode in binary form, so modification isn’t permitted, and the iOS libraries are a black box, obviously not modifiable either. In the end, essentially all the concrete revenue is built to flow through Apple.

Android is published completely openly, with the stance that anyone can build secondary or tertiary derivative works from it. But in reality, even though that’s the stated position, nobody really has the guts or the effort to substantially rebuild something as complex as an OS and create a derivative version. In practice, everyone is more or less just lightly customizing the raw Android that Google provides and using that. In other words, everyone is, in a sense, still in the palm of Google’s hand. Partly because of that, or perhaps not, the revenue situation feels like a wait-and-see. At this point, I don’t think there are obviously tremendous results to point to yet.

The former is pretty direct — a somewhat forceful, brute-force approach, but it can be called a meticulously engineered freemium.

The latter is extremely roundabout and hard to follow, but in the end, it can be called a freemium played with a straight bat.

Now, which one will win?

Which one will survive into the future?

Apple is already an overwhelmingly dominant giant company. No one seems able to defy it. Its strategy is tightly coordinated, and its monetization is airtight.

Android, despite its share, has an uncertain position even within Google itself, and its contribution to revenue seems to be, let’s say, still an open question. I don’t think the quality of the OS itself can be said to beat iOS. And yet, its greatest appeal lies in being free, open, and freely modifiable. The number of companies and fields that have newly adopted Android in just the past few years is beyond counting.

Which culture will win?

What counts as “winning” is, of course, the fundamental question underlying all this, but it’s a genuinely important question — defining it clearly and predicting the outcome might even connect to predicting the future of the industry itself.

image-7

Then there’s Arduino, which clearly belongs on Android’s side of this divide.

It doesn’t yet have anything you could call real force, and no explosive momentum. Monetization was never really its goal to begin with, so that’s unclear too. But the DNA of free, open, freely modifiable is unmistakably there.

Will some fitting role come its way in the future?

These days you often hear stories like “an elementary school kid built a smartphone app.” The barrier to software development has dropped, and it’s become easy to get started.

So can you imagine something like this?

“An elementary school kid built their own original smartphone using smaphoduino as a summer craft project.” “All the parts can be bought on Amazon, so my allowance was plenty.”

Some people start companies off the back of smartphone apps. One person, with no fancy equipment, can get to monetization quickly.

So how about this?

“A design watch made by an art school student on the Arduino-xxx platform becomes a huge hit.” “Production handled by Duino Electronics, a major manufacturer of Arduino-family products.” “Since the platform itself is very cheap, we managed to keep costs down.” “Development time? About a month, I’d say.”

“That thick-headed idiot of a department head! My new product proposal won’t get approved at all!” “Oh? What kind of thing is it? Show me, show me.” “Look, it’s like this, and this. There’s latent market need, and we can turn a profit. And on top of that, here, here, this part is the real breakthrough!” “Ooh, nice, that’s good. I’d want that myself.” “Right?! Right?! Let’s build it!” “Yeah. So, should we actually make it?” “Seriously?!” “Yeah. With this, combining the xxxduino that just came out, Arduino-@@@, and the ###duino-extension, and then using that customization product program from Duino Electronics that’s gotten famous lately…” “OK! Let’s prototype it right away. And then throw it into the next product meeting!” “Huh? What are you talking about, we’re going to sell it, right? Let’s just sell it.” “Wait, you can even do that?” “Of course. It’s not just Duino Electronics — there are a lot of productization services specializing in Arduino lately. There are schemes where they’ll build something from just an idea and a block diagram and share the revenue with you, and of course you can also do as much as you can yourself and sell it through Amazoduino.” “That’s it! Alright, let’s do this!”

Something like that.

The world might change.

Can’t we share that kind of premonition?

Unlike the explosive, bubble-like excitement that the internet and the smartphone brought about,

this would be a slow paradigm shift aimed at the future.

Arduino here is just one example I’ve raised. In the future, some other free platform might come along and define an era. That’s not something I can know.

But I want to hope for it.

In the end, an era longs for the next era.

My hopes, everyone’s hopes — things like that form a collective whole.

So what is the next era, then?

The answer isn’t just lying around somewhere nearby, but polishing one of the things that is lying around nearby always, every time, leads to the answer for the next era.


Originally published in Japanese at https://clazytech.com/2013/04/1987/. Translated with LLM assistance and reviewed before publication.