101–107 of 107 posts
Earlier quoted context omitted.
Unfortunately it doesn't react to horizontal scroll events...
The fact that Chrome maps left/right touchpad swipe gestures to Back/Forward basically makes proper horizontal scrolling unviable. :(
Earlier quoted context omitted.
Damn, I didn't think of your use case. I'm on an iMac/MBP and use the Magic Mouse as my primary input device. I should add a button and/or keyboard shortcut to disable the horizontal scrolling.
I don't have a disability but plenty of people do. Not everyone can use a mouse, and that's a fairly important thing to remember in UX design. Thanks for adding other options for scrolling!
Earlier quoted context omitted.
The fact that Chrome maps left/right touchpad swipe gestures to Back/Forward basically makes proper horizontal scrolling unviable. :(
I'm using Chrome right now, and it doesn't seem to do that? I can't confirm that horizontal scrolling works at all, admittedly; I'm having trouble finding a website that lets me force it to not fit horizontally.
So I love the ambition - especially as a way to decouple services and encourage interop. But in the end, isn’t this kind of thing typically a lowest common denominator approach? For example, Spotify or iTunes specific features/integrations either get lost or get added as an extension, to the point where you’re only worse off the main service’s APIs (which will be always up to date and are still required to be up, and…
That's an interesting idea but unfortunately we're limited by the walled gardens of the devices and platforms we use. We'd need sufficiently strong outside sources to entice companies to give us raw access to our health and things like that. Until then, this personal API concept is the best thing I could think of.
Earlier quoted context omitted.
That's an interesting idea but unfortunately we're limited by the walled gardens of the devices and platforms we use. We'd need sufficiently strong outside sources to entice companies to give us raw access to our health and things like that. Until then, this personal API concept is the best thing I could think of.
But this personal API is still calling out to the same services, with the same restrictions.
I've thought about this on and off for a long time. Urbit, Solid, Mastodon (anything ActivityPub), SecureScuttleButt, Matrix servers, etc. The biggest problem as I see it is cost. While I might want to have this for $60/year (or own my own hardware for a little more), the vast majority of people (whose adoption you need), don't want to pay for this. There are countless other UX and technical challenges, all interesti…
Everyone wants free but "free" costs more than money. It's quite the pickle.