6 ms·
When I had to go from my Palm Pre to an android phone it was a giant leap backwards in functionality and usability. They got so many things right from the get-
by aidenn0 9y ago
When I had to go from my Palm Pre to an android phone it was a giant leap backwards in functionality and usability. They got so many things right from the get-go with WebOS, but it would have had to have been perfect to break into the already existent duopoly.
The ship has long since sailed and android now is almost certainly better than WebOS ever was, but this does make me nostalgic.
- snuxoll 9y agoI still miss my Pre+ every day, the hardware and software worked together like magic - the slide-out portrait keyboard was by far my favorite feature, one that I miss with the current trend of all-screen slates. Ironically the small screen didn't feel super-cramped BECAUSE of the keyboard, I'm really upset that I never got to experience the Pre 3 which should have hit a nice middle-ground. I don't know if there's room in the market for WebOS to make any kind of significant resurgence, but considering how many people show interest in tools like React Native and Xamarin for mobile apps these days it might stand a better chance than 2-3 years ago.
- j45 9y agoGiven the overall vector of web apps towards progressive web apps... one can hope there may be a re-discovery.
- bsharitt 9y agoI had the original Pre. While the software still had a string beta feel to it, I could deal with it as the good out weighed the made for me for the most part. The problem for me ended up being the hardware, especially that terrible jelly keyboard which on phone without an onscreen keyboard(that would come in a future webOS update I believe) ended up being the deal breaker and I think I returned it in favor of a Blackberry because I was still all about the keyboard(which I still miss).
- aidenn0 9y agoThat's interesting because I loved the hardware, with the keyboard being a big highlight; I liked it better than any RIM keyboard I had previously used.
- _ix 9y agoThat jelly keyboard was incredible. If there were a competitive Pre on the market today, I'd buy. My brother purchased the Pixie. It was kind of neat, too, but... that rubberized backing started pealing off and it started to get pretty gross.
- masklinn 9y ago> When I had to go from my Palm Pre to an android phone it was a giant leap backwards in functionality and usability. They got so many things right from the get-go with WebOS, but it would have had to have been perfect to break into the already existent duopoly. It wasn't a duopoly at the time though the first public release of webOS followed Android's by just a few months, Symbian and LiMo/Tizen were still players in potentia, …. And between the innovative yet intuitive interface and web-based tech[0], many people were super excited by webOS. The issue is the Spring exclusivity (distant third) hurt, Palm flubbed the original hardware quality-wise, and they didn't have the breadth (or balls?) to build a consumer-oriented version (purely software interface) and leave the hardware keyboard behind. [0] though that also caused real issues wrt performances.
- vanadium 9y agoActually, a webOS phone with a software-keyboard was in fact coming down the pipeline. https://www.webosnation.com/windsornot-webos-slate-smartphone-never-was https://www.webosnation.com/windsornot-webos-slate-smartphon... One could also (as was tradition) infinitely hack around most of the Palm Pre line to enable it in the end. Just before HP gave up the webOS ghost, it was a popular homebrew thing to do for a certain contingent. As for the original hardware, it could have really used time when there really wasn't any time to spare in the competitive landscape. I also had a (Developer) Pre 2 which was incrementally better, and while that was a nice piece of kit, the Palm Pixi was a horrible misstep (with its minuscule size and--gasp--magnetic headphone jack) I first witnessed at their unveiling in San Francisco. The Pre 3 was the only webOS phone that had a genuine shot left, but the HP Touchpad debacle pretty much sealed it. There was even a smaller HP Touchpad in the works at the time (fully working prototypes are found now and then) to diversify the line.
- eli 9y agoI really like the pixi and thought it was the perfect size. I also think virtually every smartphone sold today is too big, so maybe I'm the outlier.
- 9y ago
- sjs382 9y agoEven beyond smartphones (I never used WebOS on a smartphone), it was amazing on the HP TouchPad. I acquired one after the fire sale and used it waaay past it's EOL. Sad that it just stopped booting one day. :-/
- xeromal 9y agoI had one too. I loved that thing.
- rlonstein 9y agoI still have one of the 32GB developer units from when HP was trying to entice people to write for it. I ran Cyanogen and Evervolv on it for a while. It will, with a bit of fiddling, run Nougat (see https://forum.xda-developers.com/hp-touchpad https://forum.xda-developers.com/hp-touchpad) but the various pieces of the support tools, ex. novacomm, are decrepit and compiling them on current Linux and toolchain didn't result in a working tool so you have to bodge around with old binary releases. Given how slow the device feels with Marshmallow and then Nougat, I will probably save my pennies for a newer tablet. As to not booting, they're really hard to brick. They can however run down so that even the battery icon won't show. Try charging it using the original charger or other that can do 2A for a day or two then attempt a hard reset.
- agumonkey 9y agoI'm reading this on one. With Android KitKat (lineageos). It's stable and fast enough to browse and read pdf. Funky, someone actually built Android 7 ans even 8 Roms. V7 is OK but a bit slower. V8 runs but since they started on february, there were large issues with play store, the os boots and runs fine, which is amazing in itself, but most apps fail. I still have the webos partition and booted it after trying v8 and god how Swift it was(sic). Would love to see the LG version run here too.
- jsjohnst 9y agoI’ve got 3-4 of the developer units and still marvel over how responsive and easy to use it is. I think it was better than on phone honestly. Haven’t used the phones in years though, so maybe memory is jaded. Will need to pull one out of my drawer and see if they still charge (mixture of Palm Pre versions and one other I forgot it’s model name).
- j45 9y agoI miss every Palm device I've ever owned. PalmOS was far more of a productivity platform than much that came after it. The headstart the Palm folks had in Mobile OS/vision went into WebOS. If I had the ability to run WebOS on a Pixel or Google device I would seriously consider it.
- hajile 9y agoWe're a decade past the webOS launch and it's still a better UI for everything. Android widgets like Vista widgets, OSX widgets, or KDE widgets failed at their vision because it's usually easier to open an application when you want one. The webOS card interface scales to tablet beautifully (I think it was actually better on tablet) and with some additions would scale to desktop as well. The UI was successful (IMO) because it wasn't actually different. Someone (at Nokia IIRC) once compared iOS navigation to having a house where every door faced outside and you have to go outside to go around to the room you want. Android made the same mistake. Both have taken step after step to deal with the effects without really addressing the cause. On a desktop, opening apps is secondary. You have a few favorites in your dock for quick access. After that, you either open your start menu or launchpad and go hunting else you Cmd-SPC and type the name. Once you have everything open, switching and managing applications is the name of the game with lots of tools to make this happen. The default paradigm in webOS is the same. A dock of favorites with an app drawer plus JustType to find less-used apps. Aside from that, managing apps is front-and-center. Compare groups of cards to OSX horizontal spaces. You go from group to group and managing apps is the default. Once again comparing to OSX, webOS has a consistent menu in the upper-left and a settings menu in the upper-right. Android and iOS now try to mimic this, but it's always a secondary feature. Home is default with app switching being someplace you go to to see your list of 100 "open" apps. Both have decided that users who are perfectly capable of using a menu on their desktop are incapable of doing so on a phone. Another not really mimicked feature of webOS was its service integration. Having all your different accounts working together in one central place seamlessly is an experience nothing comes close to. Even comparing to the web they were ahead. EnyoJS was/is a component-based framework. You could compare it to React with manual view updating (which is actually more powerful if less easy on the developer). This was in the backbone, knockout, early angular days. The flaws of webOS were blatant and fairly fixable. They used Qt for the GUI, but didn't allow native apps to be built using it (and didn't have a native SDK until way after they should have). They use Qt's version of v8 and webkit which were terribly out of date and (as a result) much slower than they should have been. The underlying Linux OS never had even basic optimizations put in place. The hardware was sub-par and memory was too restricted at the time. There were also rough edges in the UI, but nothing worse than iOS or Android at the time. Today, loads of phones have more than enough memory. The processors are fast. Web standards now have things like wasm or webworkers that make apps much more powerful. This is the time when webOS really could shine. In a day of 4+GB phones running the fast processors of today, much better web standards w a web phone really is more relevant than ever.
- on_and_off 9y agoAnecdotally, WebOS survives on TVs. I love my LG webos TV, overall I find the experience better than on my previous TV powered by Android.. Except that WebOS can't read mkv files and VLC is not available either :/ It is sad how app support can kill the usefulness of an US
- Diederich 9y agoMy LGTV definitely can play .mkv files (much to my surprise). We bought it last Christmas, and it's running WebOS 4. It's model OLED55B7A
- on_and_off 9y agoMine is OLED65C7P, which should be pretty much the same software wise. So : - maybe I am doing it wrong ? I doubt it since it should be pretty straightforward to plugin a HDD, click on video / watch. - IIRC mkv is just a container, it might be that we are just playing different formats.
- mikeryan 9y agoVideo codec support isn't WebOS's job. Different TVs have different hardware profiles, different rendering pipelines and can support different codecs. That being said according to this https://www.displayspecifications.com/en/model/f32a955 https://www.displayspecifications.com/en/model/f32a955 MKV should be supported. I've got a similar TV and MKV works on mine.
- fragmede 9y agoGiven TVs these days, it's also possible the firmware version you have is missing mkv support.
- sbalea 9y agoMy LG OLED65B7P can definitely play .mkv files, at least ones encoded with H264 and H265. Not sure about other codecs though.
- yincrash 9y agoGoogle hired webOS's lead UI designer who led the creation of Material Design at Google: Matías Duarte[1] [1] https://en.wikipedia.org/wiki/Mat%C3%ADas_Duarte https://en.wikipedia.org/wiki/Mat%C3%ADas_Duarte
- hayksaakian 9y agoI just watched a 7 year old demo of the HP touchpad and it's astounding how many of the UI/UX elements later showed up in Android https://youtu.be/DTLRCF1-fYg https://youtu.be/DTLRCF1-fYg
- hajile 9y agoI think I prefer the old Mochi project (a refresh for webOS UI) he was undoubtedly involved in. [overview image](http://enyojs.com/mochi/Mochi%20panels%20with%20email.png http://enyojs.com/mochi/Mochi%20panels%20with%20email.png) [design specs](https://github.com/enyojs/mochi/wiki/Mochi-Designs https://github.com/enyojs/mochi/wiki/Mochi-Designs) [repo](https://github.com/enyojs/mochi https://github.com/enyojs/mochi)