Software

I happily pay Ben Thompson to read his daily thoughts on Stratechery. Not only do I enjoy seeing his thought process unfold, but I also have a really soft spot for someone who has been able to get direct to his customers, finding a niche that allows him to just do his thing, and be successful along the way. This is one of the great enablers of the Internet era. Because we have broken many of the borders, or distribution friction, we are able to see niche areas go deep and do well. This unbundling is fantastic for diversity. Without this we need to aggregate and then popularism naturally forces the hand on what content gets shared the most and touches people.

Ben talks a lot about this topic itself, and often points to Marc Andreessen’s old chestnut that there are “only two ways to make money in business: One is to bundle; the other is unbundle”. The pendulum swings, and those who get to the other side quickly can benefit from that momentum.

We are currently witnessing the unbundling of mobile, and it is fascinating to see people try to understand how deeply the pendulum will swing and where to get ready to add value to the ecosystem. I feel like a broken record when I remind myself and others how long mobile took to take off. It was The Big Thing tm at JavaOne for many years before it was.

You remember when…

the networks were slow and atrocious (and WAP? nuff said)
screens were tiny and low quality (and when we got to touch screens they were far from feeling like they do today)
input was often painful (as great as T9 was for those who assimilated it, and as great as hardware keyboards were).

We could keep going on, but man, it was bad. It just took time for all of the evolution to get good enough, and when it did, it clicked.

I really enjoyed seeing yet another view of just how big it was, and is. Just compare it to the other revolutions in computing:

Mobile is up up up up up and to the right

We bundled computing, communications (phone, texting => social), entertainment (media) and the hitch hikers guide to the galaxy (The Web) all together. You can carry it all around in your pocket with a usable screen and input that keeps getting better.

This is a popular bundle and it is still growing. We are also seeing attempts to unbundle again, in a phased way.

Remember when the desktop was the “digital hub” in the home? iTunes on a computer was the source of truth, and other devices could tether and untether. This has now been taken over by either mobile devices or the cloud itself. The most literal example here is with watches. The first version of watches required your mobile device, and over time this changed (NOTE: Wear 2.0 just launched!) This is critical. One of the great uses of wearables is fitness, and you don’t want to have to run with a watch AND your device.

So, what are we unbundling here?

Compute: it makes sense to have a system that can do “enough” itself, but can also use compute from other parts of the system (watch using mobile, mobile using desktop, everything using cloud 🙂 A really important part of this is bringing the power of ML to where you need it to be. As our best experiences all use ML somewhere, we need progressive ML enhancement, including being able to run some of this offline (e.g. TensorFlow crunching in the cloud => run detection locally on device)
Network: not having to go through your mobile device only, and also using the power of P2P (you see amazing examples of this in areas of the world with really weak and expensive networks)
Input and Output: This is huge. We are breaking out of touch screens of a certain size and virtual keyboards to include voice (including ambient), wearables, and optimized form factors.

After platforms have done the heavy lifting to break the bundle apart it unleashes even more opportunities. As you build product, your constraints are changed and the levels of context compound to let you do amazing things. Sometimes this comes via quick access for power:

“Hey Google, if you notice that I fall asleep can you pause my media?”
“… please reset my ad id once a month”
“… make sure my garage door is closed after 10pm”
“… how often did Wendy come over in February?”

At other times it is joining multiple modes together (I have talked about this in the past) and being able to naturally morph between voice and screen access. We do tend to use our senses together. One of my complaints about some voice UI is that it forces me to close my eyes and put my hands behind my back, and surely we will be able to do better.

The platforms need to be broken up to allow for this, and this brings us to hardware and software…

Hardware Unbundling

How do we enable breaking up the phone into various pieces, and also allow bundling up those packages? This is where IoT comes to play. With Android Things I get to see teams morph and bundle in front of my very eyes, and it is exciting to see when they stick. I know that it is early days, but this is an area that in aggregate will clearly scale massively on the Internet.

Software Unbundling

https://twitter.com/maxlynch/status/835541439513772032

We talk about unbundling and bundling in software all the time. With the desktop Web we bundled experience delivery where one web app could reach a massive audience. But then, when it came to unbundling with mobile, many companies didn’t have nice APIs with the web clients sitting in front. This allowed for translation engines such as usablenet and moovweb to come in to offer the quick fix to get you going with mobile. This allowed many of us to have a beer and laugh about the old times…. “do you remember when we went in and had to hack a layer of Struts Actions to output JSON instead of HTML? Man that was a brittle POS!” There was a lot of pain and a lot of money to be made as the industry tried to turn a tight corner as quickly as possible, and the long tail is probably only half way through that corner!

As we lean into the unbundling, do you have the right pieces in place to enable high quality experiences to be built for your users in short order? Do you know your business and use cases well enough to know which context are king for you, and how to best reach them all?

We may not know the exact details of the future graph. How large will the overall ecosystems become? It is hard to compare to mobile, but your niche may still be a massive opportunity. It is also humbling to realize that on one side the numbers that we considered to be massive hits were tiny back in the day (millions vs. billions) and on the other, global mobile growth is still far from done.

Do you remember Joel’s post from 2006 discussing how 24 people were involved in a trivial “Off” menu feature?

I was re-reading it (you can’t help but have a bit of a smirk as you do so) and thinking about the mammoth task at hand right now in Redmond.

Windows is an epic beast that has grown over decades. Now imagine taking the general large task of improving it and then adding the fact that each platform / fork needs to be merged for Windows 10. At a high level it is an easy thing to say:

“Look, we can’t have separate OSes for phone, embedded, desktop, server, Xbox, we need one experience to rule them all!”

Now imagine being the engineering teams. Think of all of the work that needed to be done to even understand what to do?

Each OS team understands their own world, and now they need to share and communicate that knowledge by mind melding with the other teams. Imagine all of the short cuts that were taken a long the way: “guys, we just need to fork that and make it work for Xbox… we gotta ship!” times a thousand.

This is a common pattern in the life of large projects. To move fast you want to minimize communication costs and have small teams with clear goals where the solution is mapped in their mind. If you get to a point where you want to converge the distinct efforts then the world stops as you collectively work out what to merge, what to scrap, and what to retool.

The more that you share and leverage, the more that you need to think about the abstractions; designing them to be flexible. You have to be better at predicting the future, which is really hard to do. At certain scales the standardization has been proven to be truly worth it (e.g. ARM, distributed systems on commodity hardware) but 99% of the time I have seen teams choose abstractions that were too restrictive and the so called leverage was wiped away with the communication and integration costs.

When you write code you tend to only refactor after the third usage. What is the appropriate equivalent for large scale abstractions?

One Platform To Rule Them All

Let’s say that there are three instances of a product. One path is to have three teams run at their own speed and write everything from scratch. They may choose to use the same low level stacks (e.g. they all use node running on AWS) and differ on others (some use PostgreSQL, Redis, React on the front end, others go with other options). Each team runs at full pace, but get no leverage from each other.

On the other end of the scale one team builds a full platform that has all of the features required for the three different products. Now you get to share a lot more, but you also have much pain in that the platform needs to fully morph. This approach can be great if the three products are very similar, but it can be awful if there are many differences. Once up and running you also need to work out how to prioritize across the products. If they aren’t balanced then it is very easy to end up with one product that is the most popular owning the bulk of the back log. In that case it sucks to be the other two. It can help to dedicate resources to each product, but then you are splitting on people resources vs. backlog work.

Apple and Microsoft

Windows 10 isn’t the only operating system in this dance. iOS was born in classic Apple style. A team was formed to go after the mission. They could steal people. They fork and run.

I have also heard that the org structure has changed a lot in the last few years. Consolidation has happened (e.g. one power management team to support iOS and OS X).

I don’t know about you, but I have felt like my recent Apple products have been less stable (both iOS and OS X). Is this just the weight of product development? It does feel like the teams are being pushed too hard. Those yearly releases must be brutal! But, I also wonder if part of the issue is pivoting to a more shared world.

One Adaptive World

Why is this work happening at the same time? You can see the argument:

It is time to have one adaptive computing platform. A unified experience. A unified store. The future isn’t a desktop and a phone. The future is connecting together inputs, compute, storage, and outputs.

This makes sense to me. My “phone” is a small scale compute, storage, inputs and outputs that are always with me, and it can connect to various external accessories to allow me to do more. Microsoft HoloLens (a.k.a 3d Bob!) is a glimpse to one aspect of another world of extensibility.

The future is exciting. Hopefully it won’t be the external dystopia of Ready Player One (I can’t wait to see the movie when it comes out!), but something greater outside of the matrix.

As we continue to build this future at an accelerating rate I will raise a glass to the engineers and teams who are having to go through grueling hard work to get there. Getting to the vision of Windows 10 is going to be a massive task, with beasts at every turn. These teams must be working on huge refactoring and rebuilding right at a time that there is intense pressure to ship cool new features and products.

My hat is off to you. Your companies future depends on you. Hacking on v1 is the easy part. What you are doing is the real work. The good news is that it has been done before.

Good luck.

The Unbundling of Mobile

How many Microsofties does it take to squish everything into Windows 10?

One Platform To Rule Them All

Apple and Microsoft

One Adaptive World