Is setting up Touch ID to be able to use Apple Pay considered a workaround? How about having to load a document from pages one by one to Google docs because the OS won't let Docs look for .doc files in the system memory? Or Android not having a physical mute switch?
Edit: Just to add one more... is making Touch ID more responsive a flaw because now it's too fast to wake the lock screen to access the camera shortcut, forcing you to use the power button to wake the device first so you can then access the shortcut?
Having a trusted device or place is no different from setting up a security pin, password or Touch ID as you're prompted to set it up during installation/setup. In the end, it's not a flaw just because you have to change the way you do something, it's just a matter of utilizing the tools benefits to get maximum efficiency out of what you're using
First, classic knee jerk response in this forum to criticisms of anything not Apple or iPhone related--unable to successfully defend something's deficiencies so lets try to pick apart flaws of the iPhone in response to deflect. Where did I once mention the iPhone or Touch ID?
And second, your just simply incorrect in your latter comment. If you have to change the way you do something to accommodate functionality that cannot be done because of the hardware's implementation, then yes, it's a poor, inefficient design. When putting the fingerprint sensor in a different location on the phone allows it to be used without having to implement other workarounds, the yes, it's a poor, inefficient design. If it was on the front as Apple and Samsung do (or even the side like the Xperia Z5) I would not need to always pick it up or use a secondary unlock method when it's on a table or in a car dock. Security PIN, password, or front facing fingerprint sensor can always be used in these scenarios without implementing a secondary work around--this implementation cannot. That's the definition of inefficient.
I still think on the back will be just as natural and efficient. My finger goes to that spot on the back when I pick up my phone, just as much as my thumb usually goes around the bottom part of the front.
I am not sure why I wouldn't use smart lock when at home, at work, or in a dock, even if it was on the front.
I think you've been conditioned to believe all responses are defensive in nature in these forums. If you look at my points I also mentioned the lack of a mute switch as it is missing on Android, yet no one sees it as a design flaw but adjustment.First, classic knee jerk response in this forum to criticisms of anything not Apple or iPhone related--unable to successfully defend something's deficiencies so lets try to pick apart flaws of the iPhone in response to deflect. Where did I once mention the iPhone or Touch ID?
And second, your just simply incorrect in your latter comment. If you have to change the way you do something to accommodate functionality that cannot be done because of the hardware's implementation, then yes, it's a poor, inefficient design. When putting the fingerprint sensor in a different location on the phone allows it to be used without having to implement other workarounds, the yes, it's a poor, inefficient design. If it was on the front as Apple and Samsung do (or even the side like the Xperia Z5) I would not need to always pick it up or use a secondary unlock method when it's on a table or in a car dock. Security PIN, password, or front facing fingerprint sensor can always be used in these scenarios without implementing a secondary work around--this implementation cannot. That's the definition of inefficient.
I'm not saying it will work poorly when used, just that it's not an optimal design--it's subject to limitations that placing it on the front or side is not.
And yes, smart lock/trusted device functionality is great (wish the iPhone had it) but I'd wager the vast majority of consumer's don't use it and you have to use it if you want to avoid the aforementioned limits.