I have actually developed for this platform. KaiOS powers Jio Phone and Reliance JIO is by far their largest customer (and also an investor from what I know).<p>The thing I like about this platform is that it runs most web technologies. You can thank Firefox OS for that. We used React ecosystem to develop apps for KaiOS and they worked well enough. Jio Phone ships with Video and Audio streaming apps which are all built on either React or Angular and use HTML5. I think all of that was possible on Firefox OS as well and they haven't really changed anything substantially. We were given links to archived FirefoxOS documentation pages when we asked for documentation.<p>They have managed to package FirefoxOS for enterprise customers. From what I know the KaiOS team comprises of people who worked on parts of Firefox OS (but not the core FirefoxOS team).
This makes me wonder why FirefoxOS shut down and why did it not try to market itself like KaiOS has managed to do.
It seems like folks aren't aware that KaiOS is that runs on the JioPhone, a super cheap & popular feature phone in India, bundled with a super cheap data plan:<p><a href="https://economictimes.indiatimes.com/tech/hardware/jiophone-deliveries-likely-to-start-over-weekend/articleshow/60783048.cms" rel="nofollow">https://economictimes.indiatimes.com/tech/hardware/jiophone-...</a><p>To get some sense for the importance of this phone, this is the only feature phone you can get the Google Assistant on: <a href="https://www.androidauthority.com/google-assistant-coming-feature-phones-starting-indias-jiophone-820110/" rel="nofollow">https://www.androidauthority.com/google-assistant-coming-fea...</a>
Looks like the new HMD-Nokia "banana" is powered by KaiOS [1].<p>[1] <a href="https://www.nokia.com/en_int/phones/nokia-8110-4g" rel="nofollow">https://www.nokia.com/en_int/phones/nokia-8110-4g</a>
A chromatic nightmare paired with zero information, and that zero is stretched to fit a multi...thing I can't scroll properly. I sincerely hope whoever made that website isn't involved with the operating system.
Please give us back the web made by people for people, not these abominations made by designers for investors.
Let's face it, web on mobile has failed.<p>Web abstraction layer for UI is too heavy and very limited. Even today we can't have multithreaded scrolling or manage painting with the latest web standards.<p>Native platforms don't have to worry about "other browsers" so they can optimize their UI abstraction layer specific to their target devices. They also don't have to wait for ever to get consensus for new APIs and architectures firm multiple parties that don't specially care about your platform.<p>No wonder native apps are so much better for the user and with recent developments in tooling they are as easy to work with as th eweb technologies
To me the mistake that was made with Firefox os was going after android instead of going after chromebooks. If firefox os had been designed to run on commodity x86 hardware like chromium os it would not have fallen so hard because a lot of people would be able to run it on an old laptop even if no one was making official hardware for it. Because these run html5 web apps the lack of appstore depth would have been a non-issue as well.
From the FAQ<p><i>Can I develop apps for KaiOS?</i><p><i>KaiOS is a curated platform for apps and we are working closely with app developers to provide the best experience for our users. At the moment we are not accepting submissions into the Store, but will do so in the future.</i><p><i>If you are interested in developing apps for KaiOS in the future, leave your email in our developers section. We will notify you when of important product updates. You can also follow us on Twitter to stay up to date.</i><p>I'm not sure if this is really a good way to get developers on board given the ease of starting and experimenting on iOS and Android.
I couldn't find a link to the source code. Then I found this:<p>>KaiOS is based on the Firefox OS open-source project and we are committed to abide by the rules of the applicable open source licenses. Therefore, we’ll make the source code available to the extent required by the applicable open source licenses.<p>Haha. Good luck with your OS. Next.
I'm on a high horse (I'm able to afford an iPhone), but what kind of problem does this solve? To me, it looks like Nokia now has Android, their own operating system, and this to upkeep. Does anyone else remember what happened when they last time partnered with an experimental mobile operating system? I think it was Microsoft last time.<p>Would love to hear some reasoning from the folks from HMD about this.
This is definitely a promising OS. The fact that they have a maps app is extremely important. I think they'll also need a WhatsApp app to be truly competitive. They could use a few other mainstream messaging apps too. The mbasic Facebook messenger should work fine on this OS.
I'd like to see <a href="https://www.redox-os.org/" rel="nofollow">https://www.redox-os.org/</a> ported to mobile phones and perhaps integrated with this or FirefoxOS somehow.
From the website, it appears that all apps are written in HTML5+CSS+JS, however they target feature phones with 256MB of RAM and claim to have a long battery life.<p>Considering how much resources some electron apps need and how battery hungry they are, what's the "secret" here? Is it a subset of HTML? Is Firefox that much more efficient than Chromium?
Competing with the Android/iOS duopoly was a war of attrition the Microsoft, Firefox, Canonical and Samsung (Tizen) all lost. If you don't have the resources that those companies do I have a hard time seeing how you survive, and I have no interest in investing in a platform that has an extremely high risk of being orphaned. I wish it was otherwise - earlier today I was lamenting that my Samsung Galaxy S7 is laggier and less responsive than the $100 unlocked Lumia I bought myself years ago was. But I don't see another platform succeeding here.
Nice: it looks like the system font — for the Alcatel Go Flip and Nokia 8110 4G at least — is Open Sans. I've been using Source Sans Pro for most things lately, but I did always like Open Sans.
I'd really like to see a truly open alternative on the mobile space. The biggest issue is the hardware. It's just not standardized and there's no incentive to do so. It's really preventing the way Linux took off on developers desktops back in the late 90s/early 2000s.<p>FirefoxOS and Ubuntu Touch looked promising, but they lacked good hardware to run on. I'd really like to try Plasma, but I don't like any of the devices it supports.<p>PostmarketOS is just a way to turn an old phone into a Raspberry Pi type device, but maybe that's the first step in a truly unified mainline kernel for all mobile devices.
I don't know. I really liked Microsoft's phones, but there was no Google Maps, no Google Inbox, and bunch of other apps that I use daily were missing.<p>Software is the problem for these OSes. The only way to be able to compete IMHO is to make it compatible with APKs, installable via a store.<p>Otherwise, it's a nice effort but you'll never reach the adoption necessary to make it worth continuing working on the project.