since people are talking about it, here's PocketToot, a Mastodon API client (tested with 2.3.3, Pleroma untested but likely compatible) for Windows Mobile 5 in the Pocket PC form factor. (2003/Smartphone unsupported; see README)

@nev @staticsafe

* a joke (what if I ported this C# code I had for talking to masto APIs to .NET CF?)

* then I got too into it (wait, it works; it seemed to come together; and working in the IDE is easy)

* I also love PDAs (even if I prefer the Palms)

@calvin @nev @staticsafe I wasn't around ; would you say that they do/did anything different than modern smartphones? Is there anything about them that you think e-Ink devices could learn from?

@bthall @nev @staticsafe mmmmmmm

the iPhone changed everything; it allowed access to the "normal" web, radically altered app distribution, and radically altered UX metaphors and interaction; popularizing the category

PDAs and smartphones built like them were more desktop like UI-wise. of them, winmo tried to do everything and felt like using desktop windows; palm os was much simpler but aged badly into the smartphone era

not sure what eink devices could learn

@calvin @bthall @nev @staticsafe I'd also say that the iPhone learned pretty heavily from Palm OS, even if it didn't have the same goals.

Basically, Palm OS was trying to bridge the gap between fixed function organizers, and the early 1990s PDAs (that tried to do too much for their hardware, and were too bulky). Emphasis there was on quick access to the data you needed, and part of the philosophy was that it shouldn't do too much - if you wanted to do heavy tasks, bring your laptop.

@calvin @bthall @nev @staticsafe The iPhone definitely didn't exactly follow that - Safari supporting the full web seamlessly was seen as revolutionary (there were attempts with Opera Mobile, primarily on Windows Mobile, but it was clunkier).

But, especially early on, Apple did follow some parts of the philosophy - don't multitask, make programs launch fast. Don't do too much (I mean, early on, they didn't even have copy and paste), just do what's needed for a phone.

@bthall @nev @staticsafe The UI changes that @calvin talked about, quite frankly, were largely because of a technology shift from resistive touch (which measured pressure) to capacitive touch (which measured skin contact).

Resistive displays were often used with a stylus (which could produce a very small point of pressure on the display), so UI element spacing tended to be similar to desktop UIs at the time.

@bthall @nev @staticsafe @calvin The trend towards more whitespace in UIs (not just mobile, but you're seeing it in web and desktop UIs) is a manifestation of what mobile devices nowadays require, though.

Capacitive displays are used with relatively large fingertips, and therefore require wide spacing between UI elements, to be able to easily select one.

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!