Huawei and other mobile “tech giants””: you should break free from

Credit: csp_praisaeng

In short: Google-free Android, progressive web apps: there is a big opportunity in the mobile world for market disruption.

Today we learned that Huawei won’t be able to ship Android any more on their smartphones, with likely severe consequences for their mobile device business.

Why? Geopolitics

Huawei has probably played a questionable game with user data and corporate data. This has led governments to discourage the usage of Huawei devices, which is a fair and understandable attitude.

However, what Huawei really didn’t understand is that their dependency on Google/Android technology and services would put them into this terrible situation. Discussions have moved out beyond regular commercial and trade arguments, and are now clearly out of control.

They should have learned from the past: USA has a significant track record when it comes to embargoes and export restrictions. They don’t even hesitate to force their allies to apply the same restrictions, by threatening them more or less directly, commercially and financially.

For Huawei, what we witness today is the result of 10 years of strategic blindness. They should have realized that when they sell a smartphone, most of the value is in the software, not in the hardware. Therefore, they shouldn’t have become so reliant on Google/Android for the software: this hard dependency is a major risk for any mobile business.

Smartphone makers should (really) unite around a common, independent, project

In the 90s, big tech firms like Intel, IBM and others came to understand that they ought not rely solely on Microsoft/Sun/Oracle as business software partners. They could see that putting all their eggs in one basket was huge risk for their continued businesses in the long run.

So what did they do? They started to support Linux, the geek OS of the 90s! They invested in Linux companies, they joined the Linux Foundation. And now Linux is everywhere, and Intel, IBM and others still have strong and diversified businesses.

Android should be like Linux. It should be an infrastructure software project upon which other businesses can build more value and yet stay independent from monopolistic proprietary software vendors.

The time is right, and the opportunity is huge

Growing concerns about data privacy and other emerging technologies make now the right time to disrupt the mobile market and begin a new era in this field.

The /e/OS is proof that a credible alternative is possible. It can replace the Google flavor of Android. It’s Google-free at every level, yet still compatible with all Android applications, and provides by default a more virtuous environment in terms of default online services: search, mail, drive… All these ship by default with the /e/OS and provide a great option for people and organizations who aspire to something better and more ethical to use in our new digital world.

Ultimately, we will also have to break free from Google services and the Android application environment. And that’s where a new, emerging technology will help: progressive web applications (PWA) are a new way to design and release mobile applications. PWAs are multi-platform (and thus cheaper and faster to implement and maintain for app publishers). They can be used instantly, without the need to pre-install them, but still retain the same benefits of native mobile apps when it comes to things like local storage and off-line functionality.

With PWAs, there will be no longer any need for the Google Play store: publishers will be able to serve their apps directly to the consumer, or through repositories which aren’t closed worlds. /e/ will start to add support for progressive web apps through their repository of applications.

Ultimately we will probably be able to build an ecosystem where all apps are no longer reliant on the Android framework. After this period of transition where native Android apps and PWAs will co-exist, any free-software mobile operating system, such as KaiOS, PureOS and others, will gain the full benefit of this new app ecosystem.

We stand right now at the crossroads in many things: geopolitical change, privacy concerns, new technologies… Would you, smartphone makers, collaborate to build a better and more ethical mobile ecosystem, along with open-source communities, whilst regaining improved value from this market?

The opportunity is huge; it’s not too late, but the time to act is now.

— Gaël Duval, /e/ Founder

9 Likes

Hi @gael, nice post :+1:
A very interesting take on the current feuds and what it means for the wider Android ecosystem.
However, your focus on PWAs really confuses me about the purpose of /e/. PWAs can be true cross-platform apps and can be installed without using a store if the OS platform permits this. However, since PWAs are cross platform, and you seem to be advocating moving away from Android-specific apps (which are built to run on the ART using Android APIs, etc) then why is /e/ built on Android at all? This is a rhetorical question, since I completely understand why you built on Android (because we get then get access to all the apps which have been made for Android, as they vastly outnumber the quantity of PWAs available at present). However, the fact that your post focuses on PWAs may lead some to be a bit confused about /e/…

… and make them think you are interested in the web-as-a-platform and therefore the revival of FirefoxOS! Now whilst I would be very interested in that project as well, I don’t think it is what you intend for /e/… or is it?

On the specific point of bringing PWA support to /e/ I fully support it. I will look for the appropriate topic to post my thoughts in.

Cheers :smile:

1 Like

Yes I do know and it was not Google, despite what they say. Google came up with the term “progressive web app” but they were actually first “invented” by Mozilla for Firefox OS. In Firefox OS they were not a W3C standard yet and followed Mozilla’s “mozapp” implementation, but they are essentially the same as progressive web apps are now.

Yes PWAs use JavaScript, but in a PWA you only download it once so in that case it’s no different from code you’d be running in any other app.

1 Like