Live data from Hacker News

Palm OS User Interface Guidelines (2003) [pdf]

cs.uml.edu

41–50 of 109 posts

Re: Palm OS User Interface Guidelines (2003) [pdf]

#41
post #35

Earlier quoted context omitted.

I'll be keeping an eye out for your DE. For a long time now, the Linux desktop space as a whole has been rather uninspired in my opinion. A few interesting ideas have surfaced within it but failed to become popular for one reason or another, making for a rather stale environment. That's not to say that it needs to be in constant flux or to be full of radical ideas. If anything, it'd be nice to see more DEs settle int…

Please can we just have Windows 98 again. Not the kernel, kernels are better now, but UIs have only gone downhill from there. Win9x was peak "it just works" (as long as it doesn't crash so please, no win9x kernels)

Well, this will be on a unix and it will be libre so its already better than windows, but I am heavily inspired by the 9x design language in multiple ways. Of course, things have changed and current tastes must be accommodated but there are important ideas that can be pulled from it

Re: Palm OS User Interface Guidelines (2003) [pdf]

#42

I'm adding this to my repertoire of HIGs to study for a new desktop environment project I'm working on. I'm trying to synthesize the best parts of every computer interaction method, primarily focusing on desktops but looking at mobile designs as well. There are 2 principle reasons for this project: 1. UNIX desktops objectively suck compared to their Mac and Windows cousins, either being too complex to learn and bomba…

I'll be keeping an eye out for your DE. For a long time now, the Linux desktop space as a whole has been rather uninspired in my opinion. A few interesting ideas have surfaced within it but failed to become popular for one reason or another, making for a rather stale environment. That's not to say that it needs to be in constant flux or to be full of radical ideas. If anything, it'd be nice to see more DEs settle int…

The real problem is you can’t have a DE separate from the programs that run therein, so everything just apes windows ;or sometimes macOS; badly.

To really break free you have build all the programs too, with the new UI paradigm.

Re: Palm OS User Interface Guidelines (2003) [pdf]

#43
post #7

To me the best thing about Palm OS was the rule that you’re never more than two taps or a button press away from where you want to be. (I think that’s how I remember it). The beloved early GUIs were all on machines that didn’t do much, comparatively speaking. The problem with modern GUIs is that there’s just too much to learn and remember if it’s presented as symbols rather than text.

This is one of the reasons I hung onto my Treo for so long. It was so much faster to do... well, basically anything that the device was capable of. With the physical keyboard, you actually didn't need to take the stylus out very often, either. Calling Mark: (power on) (phone key) M-A (send) - hitting the phone key automatically brought up the dialer, which did double duty as contact search. Adding a new event to the…

Even better, IIRC on the Treo the phone key would turn it on?

I had a Treo 600 and and then 650 from around 2003 until 2007 when the iPhone came out. The 600 was among the best devices I've ever had. Rock solid, did exactly what it said it did. The 650 would crash randomly just sitting there. Not quite as bad as a Windows phone of the era, but a substantial regression.

Re: Palm OS User Interface Guidelines (2003) [pdf]

#44
post #42

Earlier quoted context omitted.

I'll be keeping an eye out for your DE. For a long time now, the Linux desktop space as a whole has been rather uninspired in my opinion. A few interesting ideas have surfaced within it but failed to become popular for one reason or another, making for a rather stale environment. That's not to say that it needs to be in constant flux or to be full of radical ideas. If anything, it'd be nice to see more DEs settle int…

The real problem is you can’t have a DE separate from the programs that run therein, so everything just apes windows ;or sometimes macOS; badly. To really break free you have build all the programs too, with the new UI paradigm.

Kinda what I'm trying to do. It will have a sort of "native feel" but will try to accommodate other UI paradigms and incorporate some of their ideas

Re: Palm OS User Interface Guidelines (2003) [pdf]

#45

I'm adding this to my repertoire of HIGs to study for a new desktop environment project I'm working on. I'm trying to synthesize the best parts of every computer interaction method, primarily focusing on desktops but looking at mobile designs as well. There are 2 principle reasons for this project: 1. UNIX desktops objectively suck compared to their Mac and Windows cousins, either being too complex to learn and bomba…

If you want a photocopy of the Go Corp. PenPoint UI guidelines let me know and I'll see if I can dig out a copy from a binder which I got w/ an SDK I purchased years ago --- I really miss PenPoint, and always thought it was one of the better UI environments. contact info is my user name here at aol.com

1) I'll be sure to reach out

2) You still use AOL? Is it just you've had it long enough to not want to switch or do you actively choose to use it for some reason I might've missed?

Re: Palm OS User Interface Guidelines (2003) [pdf]

#46
post #3

I still miss my palm treo, the stylus, and physical keyboard. 20 plus years later and I still cannot use an apple pencil on my iphone... >:(

It puzzles me why there is no proper stylus for an iPhone considering how big some versions are.

You can buy styluses for iPhone (or any smartphone) but they have round squishy tips for the capacitive touch screen. They aren't any better than a finger, probably cause the display is tuned for a finger. I only use mine when phone or tablet is on stand.

Apple could put the technology for Apple Pencil in iPhone, but probably not worth the cost for number of people who would use it.

Re: Palm OS User Interface Guidelines (2003) [pdf]

#47
post #43

Earlier quoted context omitted.

This is one of the reasons I hung onto my Treo for so long. It was so much faster to do... well, basically anything that the device was capable of. With the physical keyboard, you actually didn't need to take the stylus out very often, either. Calling Mark: (power on) (phone key) M-A (send) - hitting the phone key automatically brought up the dialer, which did double duty as contact search. Adding a new event to the…

Even better, IIRC on the Treo the phone key would turn it on? I had a Treo 600 and and then 650 from around 2003 until 2007 when the iPhone came out. The 600 was among the best devices I've ever had. Rock solid, did exactly what it said it did. The 650 would crash randomly just sitting there. Not quite as bad as a Windows phone of the era, but a substantial regression.

I had the Treo until 2012; the Android headwinds were blowing full speed at that point.

Before the Treo, I had a VisorPhone. Wonderful device, and fit a specific need (no phones allowed in school - great, I can slide the phone out of the back, and continue to use it as a PDA). The thing that killed the VisorPhone for me was PalmOS 3.5's lack of memory protection, combined with a bug in the SMS app. Anybody sending me an MMS message instantly crashed it, requiring me to pull the batteries. Sometimes I hadn't realized it happened for hours, and missed phone calls. MMS messages (group texts, etc) only became more and more common, and when this became a multiple-times-weekly occurrence, I made a move.

Re: Palm OS User Interface Guidelines (2003) [pdf]

#48
post #22

I'm adding this to my repertoire of HIGs to study for a new desktop environment project I'm working on. I'm trying to synthesize the best parts of every computer interaction method, primarily focusing on desktops but looking at mobile designs as well. There are 2 principle reasons for this project: 1. UNIX desktops objectively suck compared to their Mac and Windows cousins, either being too complex to learn and bomba…

The best book I've ever read on the topic was the classic Mac OS Human Interface Guidelines. I still recommend them even though some of the specifics are out-of-date. https://dev.os9.ca/techpubs/mac/pdf/HIGuidelines.pdf

I'd want to add "Designing Interactions" by Bill Moggridge (IDEO, designer of the first 'laptop' computer):

https://www.amazon.com/-/en/Designing-Interactions-Press-Bil...

Re: Palm OS User Interface Guidelines (2003) [pdf]

#49
post #22

I'm adding this to my repertoire of HIGs to study for a new desktop environment project I'm working on. I'm trying to synthesize the best parts of every computer interaction method, primarily focusing on desktops but looking at mobile designs as well. There are 2 principle reasons for this project: 1. UNIX desktops objectively suck compared to their Mac and Windows cousins, either being too complex to learn and bomba…

The best book I've ever read on the topic was the classic Mac OS Human Interface Guidelines. I still recommend them even though some of the specifics are out-of-date. https://dev.os9.ca/techpubs/mac/pdf/HIGuidelines.pdf

I wonder how much of their own guidelines they violated with MacOS Tahoe.

Re: Palm OS User Interface Guidelines (2003) [pdf]

#50

Earlier quoted context omitted.

If you want a photocopy of the Go Corp. PenPoint UI guidelines let me know and I'll see if I can dig out a copy from a binder which I got w/ an SDK I purchased years ago --- I really miss PenPoint, and always thought it was one of the better UI environments. contact info is my user name here at aol.com

1) I'll be sure to reach out 2) You still use AOL? Is it just you've had it long enough to not want to switch or do you actively choose to use it for some reason I might've missed?

1. I'll start looking

2. Yes, I was a charter member (who unfortunately, was broke when they offered the chance to buy stock), and it's easy to remember, and everything online account-wise is tied to it, and if I could still be paying for it and having my member FTP/webspace, I would.

Post reply on HN