Live data from Hacker News

Palm OS User Interface Guidelines (2003) [pdf]

cs.uml.edu

71–80 of 109 posts

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

#71

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…

Not sure if you have experimented with it yet but COSMIC is a DE made by System76 (creators of Pop!_OS) and manages to get pretty close to what I have been seeking, which is essentially MacOS with tiling. They basically gave up on GNOME and built it in Rust from scratch. Still a few major things like HDR missing but overall it's solid. You get the tiling without the config that comes with Hyprland, with the added opt…

Yeah, but it has the same issue I have with elementary: it uses a toolkit nobody uses or would use for anything else

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

#72

Earlier quoted context omitted.

How is KDE like that? If you don't go out of your way to change options, you aren't "bombarded" with anything, it just works.

It's quality issue from my experience. Nobody ever bothered with polishing the defaults and the "option bombardment" is really bad incoherent design instead of having too many things. I remember spending hours customising the KDE 5 task bar clock, trying to correct the padding. Eventually I gave up customising it and switched to GNOME. KDE app customisation is also a mess compared to something like foobar2000.

The defaults have been polished more times than I can count and virtually every KDE release changes some defaults to be more user friendly. It's been getting better for a long time.

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

#73
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 adore Tog on Interface by Bruce Tognazzini, who led the earliest editions of Apple's HIG. He explores ideas that have been lost to time, like tailoring an interface to a user's personality.

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

#74

I miss the whole Palm ecosystem. I have noted many times that I had a slab phone with full screen color icon grid general purpose os with internet and countless 3rd party apps for every conceivable purpose,... 7 full years before the iphone. 8 years before the iphone had 3rd party apps. And it wasn't Android it was a Samsung SPH-i300 running PalmOS. It was great that there was not really much of an app store, you got…

> I think even the development system wasn't free either.

Metrowerks CodeWarrior was the original development system for PalmOS and was indeed not free (in either sense).

However a bunch of enthusiasts cobbled together some free development tools: the main parts were adapting the GCC and binutils m68k targets to PalmOS's constrained PIC runtime environment (it was constrained even by m68k standards); a tool to convert the resulting COFF or ELF executable to PalmOS's .prc database format; and a text-based resource compiler for generating UI elements using its own home-grown description language to express what CodeWarrior users were using a graphical UI editor to make.

That mostly still exists as it was back in the PalmOS days at https://prc-tools.sourceforge.net>. And if you hunt around on GitHub you'll find a few people who've kept the code compiling with stricter more modern compilers.

(And see also https://pilrc.sourceforge.net> for the resource compiler.)

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

#75

I can’t recommend another excellent free ebook enough: Zen of Palm. It accurately describes the key differences between designing for desktop and mobile, which explains why PalmOS was so much easier to use than the various Windows-based mobile formats from Microsoft at the time. I even wrote a whole blog series about this book two decades ago ( https://dingyu.me/blog/zen-of-palm-1 ). I switched from a Dell Pocket PC…

My wife still misses her Centro. She held onto it until Google Maps removed the API that the maps app on it used.

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

#77
post #55

Earlier quoted context omitted.

As they should. There are fundamental differences in hardware and capability between 1992 and 2026. The most immediate are pull-down menus at the top of the screen. They work good on a 9 inch screen, they are awful with 27 inch displays. Another related change are modal dialog boxes. When you have a 9 inch screen you're fundamentally looking at one document in one app at a time. When you got 2 27's that's not true an…

I'm assuming/hoping those original guidelines would have prevented the window resizing frustration we have now, along with the other usability downgrades in the support of eyecandy. https://noheger.at/blog/2026/01/11/the-struggle-of-resizing-...

I love the example of trying to grab the plate - it really makes the point hit home.

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

#78
Palm OS does not get enough credit as the progenitor of modern handheld experience, including especially iOS.

iOS shares many similarities with Palm OS, such as the home screen layout of app icons, the use of full-screen apps without windowing, the absence of an explicit "quit" action, no exposed file system (obvious today, but bold back in those days), a single hardware button to return "home", and so on.

What iOS added is true preemptive multitasking, memory protection, multitouch gestures, physics-based scrolling and so on.

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

#79

Palm OS does not get enough credit as the progenitor of modern handheld experience, including especially iOS. iOS shares many similarities with Palm OS, such as the home screen layout of app icons, the use of full-screen apps without windowing, the absence of an explicit "quit" action, no exposed file system (obvious today, but bold back in those days), a single hardware button to return "home", and so on. What iOS a…

The first three are presumably just hardware advancements? Apple certainly deserves credit for refining the concept and making it into a neat package.

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

#80
I wrote some teaching material on the rise and fall off Palm for which I produced a graphic showing how the palm split and merged over the years. Quite honestly it's one of the most complex and insane graphics i have ever made.

https://www.dropbox.com/scl/fi/7hh5uzoaj2x7zq60yv9vz/palm_ti...

Post reply on HN