561–570 of 733 posts
Earlier quoted context omitted.
Start using the keyboard trackpad for moving the cursor, selecting and deleting words, paragraphs or the whole text input. It's the killer app.
It's not the killer app. Blackberry devices (e.g. Passport) have had this for ages. (Not a problem that Apple's copying tech, it's just not unique)
Earlier quoted context omitted.
Start using the keyboard trackpad for moving the cursor, selecting and deleting words, paragraphs or the whole text input. It's the killer app.
Unfortunately the keyboard force touch only works about ~70% of the time, which is too unpredictable for me to start incorporating into regular use as a user. It's odd that after ten years of development, Apple still hasn't made their keyboard just work . Selecting and manipulating text is still buggy and unpredictable.
I have the same problem with the dictation icon. Sometimes I'll start typing a message and then realize that I'd rather dictate it. Once you start typing, the keyboard goes into "typing" mode. If you try to tap the dictation icon, it thinks you're aiming for the space bar.
I think that the keyboard is trying to be "smart" by altering its behavior based on what it thinks you'll do next. The problem is that those changes aren't reflected in the UI, so there's no way for me to know about them. I'm sure I benefit from that intelligence some of the time, but I only notice it when it when the keyboard stubbornly refuses to do what I want.
Earlier quoted context omitted.
I don't understand this. I have such an easy time with Force Touch but yet you're definitely not the first person I've heard say this. I can hit the Force Touch menus everywhere with 99% accuracy. Most people that I've seen do this seem to press really hard to try and activate it but it's much more subtle than that. It's even hard to describe but the activation isn't because of a harder touch, it's because of a "deep…
I see two problems: 1. Speed. The delay between a force touch and the haptic feedback is often measured in seconds rather than milliseconds, particularly when the watch has been inactive for a period of time. That kind of delay is frankly outrageous. The haptic feedback needs to be instantaneous to be effective, even if it takes the actual software longer to wake up and respond. 2. Tap vs. Scroll. Unlike the iPhone,…
Earlier quoted context omitted.
Your failure to research the feelings behind this statement is obvious. Fingerprints on an iOS device are stored in the Secure Enclave, a hardware module on the device itself, used for checking fingerprints, answering yes or no to the question "is this the user's fingerprint?" As for Apple Pay, your card details are used once -- exactly once -- to generate an obfuscated alias card identifier, again, only useable by t…
It seems dangerous to have the scanner on the device and I don't trust it to be safe. It's the print I'm concerned with not the hashes and crypto that connect you to payment. This is something enticing to authorities and I'm sure they'll want to figure out how to get it.
So they can want all day, at the end, entropy wins (by design in this case).
Earlier quoted context omitted.
A right-click equivalent already existed: a long press. 3D Touch is the long press controlled by finger pressure instead of time pressed. It took an already hard-to-discover feature and made it more nuanced (that is, more complicated).
It also doubles the bandwidth of that interaction. You had one slow and one fast interaction, and there now are two of each. Big question seems to be what the best mapping between those interactions and commands is. You want to map the most frequently used interactions to the fast interactions, but you also want the mapping to be learnable (consistency across applications likely is needed there), and 'intuitive' in t…
Please no wave-at-me interfaces.
No 3D touch is a very odd fragmentation. You'd think they'd want to shore up their devices to be completely compatible with this across the spectrum to motivate developers to use it as a key part of their UX. Now when only X So your apps have to optionally use 3D Touch, Pencil, adaptive layout, fingerprint, and several other interactions that only cover fractions of their hardware line.
> No 3D touch is a very odd fragmentation. You'd think they'd want to shore up their devices to be completely compatible with this across the spectrum to motivate developers to use it as a key part of their UX. 1) 3D Touch is not that important a part of the UI anyway, as devices are fully functional without it. 2) Developers will add it to their apps anyway, to entice high end users -- it's a very competitive landsc…
App developer here. Patently false. I actually haven't implemented 3D touch in any app. Want to guess how many support requests I've received for it? Zero.
Here's hoping that they'll include something like this in the Google Nexus lineup. They keep growing the phones, but my pocket is the same size.
In Europe, I noticed that the cell phone shops carry many more small (4 inches and below) Android phones than you see in the US. Unfortunately, these models seemed to have very sub-par specs.
It's junk. Didn't last one year. I'm getting used to the N5X now.
More info: http://www.iphone.se/till-salu (Swedish)