A solution to a problem that doesn't need to exist. Home button = complete absence of the problem.LG G2's double-tap to sleep/wake feature?
The camera specs are great if they actually produce better photos. If they're spec bumps for the sake of being spec bumps, and the photos they produce aren't all that great, then it's a useless feature.Xperia Z1's 20+ camera / waterproof-ness (how many stories have we heard of water damaged phones?)?
Nokia's 40+ camera?
A waterproof phone = hell yeah, I'm all for that. Sony knows how to get me interested in their products.
Always listening = useless as long as Google Now continues to suck in Australia. It's a good idea though, but a lot of reviews say it's flawed and often struggles to work. Given a few iterations, and quality services outside the US, this could be a great feature. At the moment though, it seems like it belongs in the "good idea, but flawed implementation" basket.Moto X's always listening feature and/or Active Notifications?
Active Notifications = great idea for AMOLED screens, terrible for LCD screens.
It's a compete pain in the arse needing to put in a passcode every time you want to unlock your phone. If my job didn't require it, I'd never use one. The fingerprint sensor allows you to have an incredibly secure solution without the constant, irritating need to continually re-enter your passcode.Exactly what "problem" did passwords and passcodes have prior to finger print scanner?
It solves a problem going forward- eventually, the switch to 64-bit processors would have needed to have been made. By doing it now, in a few years time, when we'll be regularly getting devices with >=4GB of RAM, Apple's entire product line will be 64-bit and such a transition will be seamless.Your other example in your post was 64-bit architecture. Groovy. But what "problem" did it create before that?
Does it solve an immediate problem? No, but it does solve a problem going forward.