Skip to main content

Will superwallets power HarmonyOs



I read the Wallstreet Journal story about the unveiling of Huawei’s “new” HarmonyOs and felt that a couple of points were “conveniently” left out of the reporting.

So, yes HarmonyOs is a new microkernel design that aims to supersede the current Linux kernel in Android OS, however, that doesn’t mean it can’t run Android apps. In fact, porting existing Android apps over is in the best case a simple recompile. In the worst case it’s probably stripping out any Google dependencies. But even that can be helped if Huawei is smart enough to provide its own “Google Mobile Service” layer with the same APIs. So in short, I’m not sure a new operating system would be such a big deal as long as all the APIs and libraries are present. In an ironic twist, the Trump administration gave Huawei “permission” to run its own operating system and Google doesn’t like it at all. But not for the reason they are saying, the so called “security threats” are a smokescreen - Google is really scared of a new competitor that has the power to break-up the Google ecosystem. If Huawei is going in that direction, Samsung might as well… 

To understand what that means, we have to understand the numbers involved here and also ask a very basic question: “at what point do you have enough users (critical mass) to sustain a  true platform business?”. In other words, when do you attract enough developers to your platform on a sustained basis? We could use Apple as a way to measure this a bit.

Apple is selling now less than 200 million iPhones per year and has slipped to the third spot in iPhone sales numbers. We also know that Apple has sold 2.2 billion phones since 2007 and of those phones, Apple claims it has 900 million active iPhone users (and 1.4 billion overall Apple device users).

Huawei has 500 million phones in circulation in 170 countries, and it’s now selling 200 million phones a year. So Apple has an ecosystem advantage of 400 million users. However, at these dimensions, I suspect Huawei could very well run it’s own distribution.  In fact they are already doing so in China today. Yes, Huawei’s Android based operating system that is on every Chinese Huawei phone is in fact already Google-free because Google doesn’t operate in China and the Chinese government doesn’t want foreign companies to gain access to their citizen’s data.

So, why talk about Hongmeng or HarmonyOs when Huawei already has a “theoretical” solution? Why wouldn’t they just forge ahead and take the best part of the open source android and build that out?

I suggested that it would make sense for Huawei to forge ahead with this plan not just because it would “free” them from Google, it is also possibly a requirement in Europe because of the Google unbundling ruling and it has strategic ramifications where Huawei could clearly mark its own territory. 


But the real reason for Hongmeng or HarmonyOs has much more to do with creating their own independent codebase for all their devices. Huawei tries to solve two things: a) dependency from foreign influences and b) complete ownership of intellectual property. Think about it this way: Apple pursues the same strategy with iOS, MacOs, WatchOs, iPadOS etc. It’s all based on the same codebase and it is fully Apple owned. A single codebase simplifies things tremendously. You can avoid a lot of redundancies by doing that and ultimately go to market faster and save costs.

The real question is if they can actually pull this off for the non-Chinese market where Microsoft and Google dominate and thus attract software companies and developers. There have been many such attempts in the past to break those “monopolies” and every time it failed because of lack of third-party software.

I think this time is different and I give this one a good chance to succeed because of two reasons: the ecosystem advantage that Huawei has in its home market and the rise of super wallets. If they can make it work with tight integration of all the must-haves services and apps (Alipay, WeChat, Grab, WhatsApp, Facebook etc. etc.) then I suspect users will no longer see a big difference between Android. And that might just be enough to launch a new operating system and slowly roll it out elsewhere. Also, the fact that they will have developer tools and maybe even better incentives for developers will probably help along.

Let’s see how this turns out.


Comments

Post a Comment

Popular posts from this blog

The case for central bank digital currency as public infrastructure to enable digital assets

I have dabbled a fair amount with all sorts of crypto currencies and their respective permissionless networks. In fact, I have been dabbling since 2012 which is by my last count a whopping 12 years. While I have always maintained that I do believe the general concept for digitization and programmability of assets is on the right path, its implementation, the user experience, the accessibility, the fraudulent activities, and the overall inefficiencies permissionless DLTs have, never made me into a true believer. I have stated that opinion on several occasions, here , here and here . There are still barriers to entry when it comes to digitization of assets: sustainable- and interoperable infrastructure. To illustrate this, I recently asked a notary public here in Zurich, why they can’t store the notarized documents as PDFs, the answer surprised me: because they must keep records for at least 70 years. Now, think about what would have happened if we stored these documents on floppy disks...
Post a Comment
Read more

I've Been Vibe Coding for 2 Months, Here's What I Believe Will Happen

In the past few months, I've embarked on an experiment that has fundamentally changed how I approach software development. I've been "vibe coding" - essentially directing AI to build software for me without writing a single line of code myself. This journey has been eye-opening, and I'd like to share what I've learned and where I think this is all heading. My Vibe Coding Journey I started vibe coding with Claude and Anthropic's Sonnet 3.5 model, later upgrading to Sonnet 3.7, Claude Code, and other tools. My goal was straightforward but comprehensive: create a CRM system with all the features I needed: Contact management (CRUD operations, relationships, email integration, notes) Calendar management (scheduling meetings, avoiding conflicts) Group management for organizing contacts A campaign system with templates A standalone application using the CRM's APIs for external contacts to book meetings direct The technical evolution of this project was inter...
Post a Comment
Read more

Vibe Coding Alert! How I Rebuilt a Wix Site and Fed the “AI Will End SaaS” Panic

My better half is an artist and maintains a Wix.com site. For the second time in two years, Wix decided to raise the hosting fees. That’s when I suggested to my spouse that I could rebuild the website and host it on Firebase (where I host most of my projects). I assumed this wouldn’t be a big deal (I was wrong) and started researching ways to use a lightweight CMS with Firebase support. Such a system exists — it’s called FireCMS — and it’s excellent. Before I dive deeper, here’s her original site (no longer a paid Wix site):  Miyuki's WIX site Her instructions were clear: replicate it as closely as possible. So I went to work. I created a product development document with use cases, scope, screenshots from the original site, the required features, and of course FireCMS integration. I used ChatGPT to draft the document, then set up a new Firebase instance, and finally launched the Vibe Coding agent (Claude Code). The process wasn’t too different from my other projects, but what sur...
2 comments
Read more