![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Entry tags:
Native apps, applications, and web apps
Marco Zehe writes "Apps, the web, and productivity" about his experience with improved accessibility/usability of native apps over web apps on mobile. My experience in many ways mirrors his, although I would go further and say I have found the same thing on desktop.
For example, I honestly did assume that once I was forced by a job to use Gmail, that I would discover features of Gmail that outweigh the power and accessibility of a mail application. I understand that I am a change-averse Luddite, and suspected that using Alpine my primary mail reader in this day and age was indicative of a slight flaw in my character.
But now that I have been using Gmail with some regularity, it has become abundantly clear to me that no webmail client I've used (Gmail, roundcube, web Outlook in accessibility mode or in rich mode) has the speed, power, and accessibility for me of using the dedicated mail application.
Marco boils his reasons for switching to native apps down to less clutter and latency . I'd say both of those are issues for me as well, just as much as simply saying "accessibility" -- although they are both inextricably tied to accessibility for me.
A cluttered screen -- especially a screen with one of those damn non-scrolling JS banners taking up screen real estate -- is one that requires more scrolling, which is inherently difficult to do without a mouse. Even on desktop, my monitors are smaller and my fonts larger than they used to be, and the design of web apps has gotten less streamlined, substantially, over the last few years.
Meanwhile, the annoying wait-till-it-loads aspect of the web app is a lot more annoying when I am waiting for mouseless browsing to see all of the page elements so it can put actionable links next to them. It's a lot more annoying when I can't start interacting with the page until it is fully loaded, unlike a mouse user who can start to move the mouse towards the expected area of the page.
Ultimately, it comes down to a combination of both spoons and basic UX. Like a lot of computer users with disabilities, the extra cost of using the computer is high enough for me that every aggravation that gets thrown in my way is one more blocker that possibly prevents me from being able to work at all. And as for basic UX, well. Like a lot of techies, I'm used to the power and speed of the keyboard-based environment. I honestly have no idea how people used to a powerful, lightning-fast, terminal-based mail application become comfortable with the clunky latency of webmail.
For example, I honestly did assume that once I was forced by a job to use Gmail, that I would discover features of Gmail that outweigh the power and accessibility of a mail application. I understand that I am a change-averse Luddite, and suspected that using Alpine my primary mail reader in this day and age was indicative of a slight flaw in my character.
But now that I have been using Gmail with some regularity, it has become abundantly clear to me that no webmail client I've used (Gmail, roundcube, web Outlook in accessibility mode or in rich mode) has the speed, power, and accessibility for me of using the dedicated mail application.
Marco boils his reasons for switching to native apps down to less clutter and latency . I'd say both of those are issues for me as well, just as much as simply saying "accessibility" -- although they are both inextricably tied to accessibility for me.
A cluttered screen -- especially a screen with one of those damn non-scrolling JS banners taking up screen real estate -- is one that requires more scrolling, which is inherently difficult to do without a mouse. Even on desktop, my monitors are smaller and my fonts larger than they used to be, and the design of web apps has gotten less streamlined, substantially, over the last few years.
Meanwhile, the annoying wait-till-it-loads aspect of the web app is a lot more annoying when I am waiting for mouseless browsing to see all of the page elements so it can put actionable links next to them. It's a lot more annoying when I can't start interacting with the page until it is fully loaded, unlike a mouse user who can start to move the mouse towards the expected area of the page.
Ultimately, it comes down to a combination of both spoons and basic UX. Like a lot of computer users with disabilities, the extra cost of using the computer is high enough for me that every aggravation that gets thrown in my way is one more blocker that possibly prevents me from being able to work at all. And as for basic UX, well. Like a lot of techies, I'm used to the power and speed of the keyboard-based environment. I honestly have no idea how people used to a powerful, lightning-fast, terminal-based mail application become comfortable with the clunky latency of webmail.
no subject
no subject
no subject
Same with me, but with Pine, not Alpine.
Yes, clutter and latency. With the addition that my condition makes animations and noises stressful for me. Only a minor stress for minor animations and noise, but that little cognitive load can add up, particularly if I'm already stressed. I tend to flinch at swooping navigation or moving banners. There's a fear reaction, even if it's just a small one. It'd be really nice if I could check which local supermarket has the thing I like on special this week without a big, bright, rotating banner in my face.
And I don't have your physical disability, but the scrolling thing is a problem even for a person with normally functioning hands, on a laptop, when the designers assume you'll be able to view their damn mouseover dropdown menu without scrolling, and you can't scroll down to see all the options without losing the menu.
no subject
Along with what I think are called "hero images." Gah. SMH.