Earlier quoted context omitted.
> no undo It works fine, you just need a keyboard what would allow you to send Ctrl+Z. Yes, there should be a menu item (at least in a pop-up) too... BTW, there is a API to add your things to that pop-up (like for searching providers etc) so there is a chance you can make it.
iOS has "shake to undo", which isn't perfect, but at least it's something.
Text editing on mobile: the invisible problem
281–290 of 693 posts
Re: Text editing on mobile: the invisible problem
#282I typed 55wpm on my blackberry without looking. The fact that you have to constantly look at the screen keyboard and correct it is a huge attention suck and kills my input speed On blackberry, a mistake was one wrong character. On screen keyboards with swipe and autocorrect, a mistake can be inserting 1 or 2 random words Screen keyboard doesn't work in the rain while we're griping: - on an older android device the bu…
Typing is a separate problem. And if you want a physical keyboard on a mobile device you can actually have one. But that still won’t solve editing . Editing on your blackberry was even clunkier than the touch affordances that this post is about - just cursor keys, right? Now, you might argue that if you can type fluently you won’t need to edit as much - but the point here is about enabling mobile devices to be much m…
you could scroll vertically and horizontally
I don't remember if you could highlight, but there was a shift key so I'm assuming yes, and I vaguely recall double-tapping backspace for whole-world deletion
Re: Text editing on mobile: the invisible problem
#2831000% agree with this post, wow. I can’t believe this is controversial.. it’s a disaster. I dread opening the mobile version of google docs, sheets, or even Notes for anything more than a grocery list. The problem is the target audience for this is business customers, and particularly those in management, so it’s a small market. ICs aren’t up and down as much between meetings and can largely stick to their desktop se…
> I dread opening the mobile version of google docs, sheets, or even Notes for anything more than a grocery list. I dread it even for grocery lists. For one the apps (Notion, Google Docs, you name it) all give me a stupid splash screen when I tap them, and I have to wait 5-10 seconds to see content. We're in 2023. Splash screens should be unnecessary. Opening a piece of text should take no more than 50ms after the ta…
Re: Text editing on mobile: the invisible problem
#284Earlier quoted context omitted.
Typing is a separate problem. And if you want a physical keyboard on a mobile device you can actually have one. But that still won’t solve editing . Editing on your blackberry was even clunkier than the touch affordances that this post is about - just cursor keys, right? Now, you might argue that if you can type fluently you won’t need to edit as much - but the point here is about enabling mobile devices to be much m…
Though in fairness to awinter-py, given that text entry is a simpler task than text editing , if typing support is already insufficient, editing won't be any better. I'm typing this at a hardware keyboard on a desktop computer. I've had to make multiple short edits, mostly backspace/retype, as I enter this short comment. The fact that I can look at the screen rather than have my attention focused on the keyboard is i…
in my experience all screen input has high cognitive workload
(even taps, because modern touch UX has small targets and unpredictable animation timing when you open a menu)
US navy blamed touch input for a boat collision and swapped out some touchscreens for physical controls
Re: Text editing on mobile: the invisible problem
#285Earlier quoted context omitted.
Raw photographs are tens of megabytes each, and it's not unusual to take hundreds per session.
Agreeing and amplifying: Taking a random search result, the Canon EOS R5 has a 45 MP sensor: https://www.usa.canon.com/shop/p/eos-r5?color=Black&type=New > Assuming 24 bits per pixel, that's 1 Giga bit (128 MB) per image , or ~1,000 images on 128 GB storage. Dedicated cameras have removable storage and professional photographers will carry multiple 500 GB -- 1 TB+ storage cards, swapping them out through a shoot. I'l…
1Gb, not GB. And in practice it's not that high. Most digital cameras use a Bayer filter, with the pixel count specified as the number of grayscale pixels behind the individual filter elements. Raws are most often 12 or 14 bits per pixel, so about 68MB or 79MB for a 45MP sensor. This can be further reduced with lossless compression. Still a lot for a 128GiB phone, though.
Re: Text editing on mobile: the invisible problem
#286Earlier quoted context omitted.
The moment I opened the article and started reading an idea came to me before reaching the authors solution. Imagine if you could just double tap a word and suddenly it becomes focused and enlargened while slightly blurring the rest of the text. The word in question now has easily targetable tap targets that you can modify quickly, swipe up to delete, rearrange, select etc like a sliding puzzle game. Like everyone I'…
An especially sucky part of editing text is changing tense or plurality. Changing "run" or "ran" or "running" is a exercise in frustration because the editor could easily change it for you by reading what you're typing. Eg I have "bottles are falling" typed out, but I go back and edit it to say "bottle are falling", and then the editor offers to update "are" to "is" for me.
Gboard has a similar edit keyboard, although I find it's a tad harder to get to than Swype's
Re: Text editing on mobile: the invisible problem
#2871000% agree with this post, wow. I can’t believe this is controversial.. it’s a disaster. I dread opening the mobile version of google docs, sheets, or even Notes for anything more than a grocery list. The problem is the target audience for this is business customers, and particularly those in management, so it’s a small market. ICs aren’t up and down as much between meetings and can largely stick to their desktop se…
Re: Text editing on mobile: the invisible problem
#288> While we should always take care of novice users first, we shouldn’t ignore proficient users. I believe that the relation should be reversed : Make the best system possible, usable by well-trained users, and only then add easy modes, tutorials, child safe modes, etc. with paths for improvement at every level. But when using modern systems, I often feel like I’m reduced to using Fisher-Price toys with one (inoperati…
In your proposal, we're expected to start from the top magically creating the best experience, and then jumping back down to novice users, and then scaling up back towards expert level to cover the gaps. It sounds quite jarring, and in practice it winds up leading to lackluster tutorials made by experts who overestimate everyone else's levels (see: "How to draw an owl: draw a circle, now draw the rest of the owl").
Re: Text editing on mobile: the invisible problem
#289I completely agree with author's view of the issue. Text editing on iOS and android have always been an afterthought. I mean, how much time did it take for the iPhone to get Copy/Paste ? The weirder part to me was that the iPad didn't bring much improvement on that front. Even with a bigger screen and "desktop class" application, text editing only barely works with a keyboard/touchpad attached. The only improvement h…
I have an iPad that’s about to go out of support and is starting to get some small cracks in a screen corner. Seriously wondering if I should replace it or just take an older, albeit heavier, MacBook for extended travel. I don’t find myself using it at home much and media consumption on planes isn’t that important to me any longer.
- reading is subpar
Having the ipad in portrait helped a lot for reading A4 size documents, where I'd be much more scrolling on the macbook.
The the form factor plays a lot when you're checking documents at an airport counter, reviewing your hotel reservation in a taxi, or looking at a map with others.
- I had to baby it a lot more
iPads and tablets in general can fit in cases and be lugged around without damage. The screen is also tough enough, where a macbook will be out of order if anything goes between the keyboard and the screen when you close it. That's fine at home, but that means it doesn't get out in any situation where it could be risky. In contrast I bring my tablet in the bathtub in a waterproof sleeve.
None of those are absolute deal breakers, I mean we used laptops anywhere we could for decades before tablet areived. But I definitely couldn't go back (disclaimer, I ended up with a Surface Pro. It's nice but as Panos is out of Microsoft now, I have no idea of the future of the lineup...)
Re: Text editing on mobile: the invisible problem
#2901000% agree with this post, wow. I can’t believe this is controversial.. it’s a disaster. I dread opening the mobile version of google docs, sheets, or even Notes for anything more than a grocery list. The problem is the target audience for this is business customers, and particularly those in management, so it’s a small market. ICs aren’t up and down as much between meetings and can largely stick to their desktop se…
> I dread opening the mobile version of google docs, sheets, or even Notes for anything more than a grocery list. I dread it even for grocery lists. For one the apps (Notion, Google Docs, you name it) all give me a stupid splash screen when I tap them, and I have to wait 5-10 seconds to see content. We're in 2023. Splash screens should be unnecessary. Opening a piece of text should take no more than 50ms after the ta…