WebOS OSE 2.10
webosose.org
webosose.org
https://www.dropbox.com/s/5fy6wczeh5sugeg/palm_timeline.png?...
> On August 18, 2011, 49 days after the TouchPad was launched in the United States, HP announced that it would discontinue all current devices running webOS. Remaining TouchPad stock received substantial price reductions, and quickly sold out
To any company in trouble, and in need of innovation, this is the perfect strategy. Inevitable Wikipedia link...
The designs exist on GitHub somewhere. I wonder if anyone has ever attempted to implement them as a front end design language?
Jeffrey Hawkins, the inventor of the palm, has a bit of a cult following almost designers. Far more respected that Johny ‘Dieter Rams’ Ives. His prototyping process was unique. (Now widely copied). Check out his wooden (!) Palm prototypes...
https://www.computerhistory.org/revolution/mobile-computing/...
https://www.theverge.com/2012/6/5/3062611/palm-webos-hp-insi...
We'd all be much better off today if they hadn't had made those fatal errors
I also remember the really natural way that Palm let you ignore an phone call by placing the phone face down to silence a call you didn’t want to pick up.
Heck, even the notification screen and widgets screen is an evolution of the Today.prc from PalmOS days.
I need to play with my LifeDrive more. I miss that beast.
Also, Graffiti was the best on-screen ink implementation. Change my mind. :D
Fun fact: Palm's latest phone copies iWatch's user interface to a phone interface and makes it usable on a bigger device, it's both fun and awesome in so many levels if you ask me.
I loved my Palm Pre 3 gotten off eBay (though I had to hack it to enable Serbian 3G connection, and I put together a Serbian Cyrillic keyboard layout too :): cards and swiping on the home button when editing text (to go left or right by a character or two) were monumental for me. Along with the full keyboard, the first (and last) time I didn't hate typing on a phone :D
Edit: it was probably 3G and not LTE at the time :)
A shame the first Pre was just unusably slow. Innovator's curse, as usual.
It may have been... I can tell you that in current LG TVs usability is poor. I'm not sure about hack-ability in TVs, this may not apply
Android TV is always catching up with Android versions, for several times its future seemed to follow the same footsteps as Brillo, Android Things, ADK, Tango, Sphere, Daydream, Sceneform, wearOS,....
And then there is the whole update story which is even more catastrophic than on phones.
So if I had to buy a smart TV, at least one from the vendor that owns the OS.
Today, iOS and Android fundamentally use the same, inferior system with the app switcher being more like ctrl-alt-del on your windows machine (you can switch processes that way, but it’s not convenient).
The “revolution” of webOS is how it decided NOT to change everything. It worked just like OSX did.
Users tend to use the same half dozen programs constantly. They pin these to the dock. You’d open your app folder or start menu to see the rest. Same with webOS.
Once they’re open, the default is to switch between them either by clicking windows or using exposé. WebOS Home Screen was also the windows swapper rather than an afterthought visual task manager. WebOS even had card groups that came very close to OS X spaces or KDE Activities.
Your settings were a menu on the right. Just like OS X and you’re app menu was the upper left just like OS X.
If Steve Jobs had seen the webOS UI, I’m completely certain the iOS UI would never have existed.
The big issue that killed them was execution. The pre sucked. A phone without the physical keyboard would have done wonders at launch. Att our Verizon would have done wonders. Not having creepy ads would have sold units too.
On the software side, minor tweaks to Linux would reduce boot time from two minutes to 30 seconds (bigger tweaks could probably have gone even farther with only one piece of hardware). They apparently just didn’t have the experienced devs.
Likewise, at the point where the web was having its biggest growth spurt, they weren’t keeping up. They used a WebKit version and v8 version a year or two behind. Simply updating these two would have almost doubled performance while reducing memory problems.
Finally, they built the core UI on Qt, but didn’t make it available to developers. They had a great, cross platform kit that could have gotten a lot of companies on board, but they didn’t run with it.
I’d love for someone who was there at the time to explain what happened to cause so many simultaneous failures.
Regarding not making Qt available to developers on WebOS, that is still the way on LG TVs, store apps are only allowed to use the JS stack.
Wow I totally forgot about those creepy commercials. Those were really bad.
LG's webOS 6.0 Smart TV Platform Designed For How Viewers Consume Content Today. https://www.lgnewsroom.com/2021/01/lgs-webos-6-0-smart-tv-pl...
LG is #2 TV maker. Global TV market share is 30% Samsung, 15% LG, etc.
I honestly think the LG interface is excellent.
It's a complete disaster! The menu system is infinitely worse than even Sony's dumb TVs, which is saying something, becase Sony can't make software for shit.
A short list: - auto-brightnes does literally nothing - changing the brightness manually requires to you go 6 levels deep into the menu - the bottom quick settings bar thing has a bunch of stuff hidden in an invisible tile that shows up only after you try to navigate over the edge, which is the most undiscoberable crap ever - the quick settings contain exactly two settings anyone would care about, the rest are useless and obviously non-comfigurable - can't hide the giant cursor when screen mirroring - can't set a default app to launch into so it takes 4 clicks and half a minute to turn on the TV (we have an app instead of a cable box because wasn't the kind od the point of smart TVs??) - can't install apps without a Samsung account, can't remote control it from a phone without a samsung account - the phone remote control can't enter text!!!!! You have to use direction keys and a shitty on-screen keyboard - no always-on cast receiver - DLNA randomly disappeares, can play like 4 codecs. Half of those you can't even scrub in and the colors get weirdly hue-shifted when playing HDR video (despite the TV supposedly being HDR10, I believe)
This is as much as I care to type on my phone, but I'm sure if I asked someone in my family who actually still uses the thing, I'd get another 10 lines to add at least.
- Which platforms are supported? Is the only platform supported a Raspberry Pi 4?
- what about feature matrix with e.g. camera, gps, gyroscope, touchscreen, etc?
- where is the open source code for what? If I want to fix a driver error, what's the projects/repos relevant to it?
- why are there no official build images that are ready to tryout? (e.g. similar to lineageos's devices list)
- flashing guide is misleading. You cannot "flash" an sdcard. Flashing implies bootloader-like patching of the existing OS of a target device, not a copied image that I can run on the exact same host device.
It took me a while to find the the examples in the repo on github:
Is there an OSS alternate smart-TV firmware community?
There are custom firmwares, rooting methods, compatibility tables, etc.
https://forum.xda-developers.com/t/rootmy-tv-coming-soon-dev...
I made sure to turn off auto-updates on my C9, and when the warrenty expires there's hopefully some really cool things for me to try!
If only someone at LG thought, gee maybe we can make better phones and distinguish ourselves in the market and, oh yeah, we have that awesome WebOS we can use too.
Also the multiple Tizen SDK reboots did not help to gain confidence.
Finally, what use to me is an OS I can't buy in Europe?
I loved WebOS and had all the Palm WebOS phones, but things quickly became a two horse race. I only grudgingly switched after I came to work at Google and they gave us a free Nexus phone as a christmas present one year, and even then I missed my Palm. Android did at least improve once Google hired Mattias Duarte from Palm/HP and he took over UX on it.
I suspect for WebOS to have a decent crack at it they would have eventually had to roll out an Android emulation layer. Developers have a tough enough time supporting iOS and Android.
After HP wound it down, the main guy behind WebOS, Matias Duarte went on to Android and then implemented Material Design there.
One specific feature I miss is when switching apps, the app cards were live views of the app, rather than screenshots like in Android.
webOS multitasking, and gesture navigation were way ahead of their time.
Not to mention Maemo, Moblin, Mer, etc. - for whatever reason, that project somehow became a zombie Voltron of other failed Linux mobile OS's, and involved big names: the Linux Foundation, Intel, Nokia, and all of these other companies (https://en.wikipedia.org/wiki/MeeGo#Companies_supporting_the...).
It then got replaced by Tizen, which is a similar improbable survivor that was once backed by a bunch of big names and now lives on mostly in Samsung smartwatches.
Maybe it's proof that too many chefs spoil the broth. At least webOS now only has LG to look after it, rather than some sort of Linux-HP/Palm-LG consortium or whatever.
Keep in mind that HP did the same with webOS, Sun with OpenSolaris etc. So, its not exclusive to Samsung, but rather big enterprise not understanding the outside world.
On the other hand, I am not sure even stellar DevRel would have saved Tizen. Yes, Sun was terrible with OpenSolaris, but wasn't Joyent stellar with SmartOS (which is the same codebase)? That didn't make SmartOS very successful.
What part would be the most interesting one? I.e. the one that's actually proposing an OS based on a browser?
While this web site seems targeted at someone trying to build IoT products from WebOS, I wonder if anyone has already done some work to write down what steps are needed to get WebOS-the-environment running on any modern GNU/Linux base (eg. Ubuntu or Debian)?
Which seems to mean that current unpatched LG TVs should be rootable for modding.
Honestly, webOS is not a bad platform, and developing for it is not even a terrible experience (you basically build a website plus a thin shim to make it appear as an "app"); what holds it back is just the braindead commercial mismanagement from LG - I had massive flashbacks from the Nokia/Maemo years, when looking into webOS app development.
Simple example: you can enable "Dev mode" to install your own apps into a tv, but it disables itself after two weeks or so, deleting all such apps. Why? Because fuck you, that's why! You have to talk to LG to get a "proper" app done, and that means submitting a presentation (I kid you not) to prove the app is "important" enough to warrant inclusion in their distribution channels. Despite all this, 99% of the apps they include are low-quality - the discriminating factor ends up being the willingness to deal with bureaucracy.
If LG fixed their app-development practices, they could easily turn webOS into "the Linux tv", onboarding tons of developers for free.