Eh not a very strong response when only a small minority of iOS devices have 3d touch. Also not sure what you mean about inconvenient since I can always thumb the back button on my Note 5. Most android phones have it on the left which is even closer.I'll take those bonus points thanks since you can 3D touch swipe from left to right to go back to the previous app. Back buttons on Android devices tend to be very inconveniently placed as they are often very low on the device. The Galaxy S6+ is a good example of a very badly placed back button (and multitasking button).
Plus there's the guesswork required to know where your Android device will actually take you back to; will it go back to the previous screen in the app you are currently in, or back to the previous app, or even just make the keyboard vanish from the screen? Who knows. Very poor and inconsistent user experience.
Also, the Moto X Pure does not have a fingerprint sensor, which immediately makes it a non-option for me. It also does not even have Marshmallow and still runs on Lollipop.
Eh not a very strong response when only a small minority of iOS devices have 3d touch. Also not sure what you mean about inconvenient since I can always thumb the back button on my Note 5. Most android phones have it on the left which is even closer.
Back behavior has gotten a lot better in android. I'll give you that a couple years ago it was quite random but these days it seems quite consistent in being -1 step. Keyboard up? Closes keyboard but keeps you where you are. Page or app up? Takes you back one screen. Last page was a different app? Takes you to that app. Finally takes you to home. It took several years to get there but it all works well these days.
Frankly I'm not even trying to say one is greatly superior to the other like you, simply that I think in thus one particular area Android works better for me.
It shouldn't do different things like that.
The keyboard, although boring design, is 100% solid and stable and typos are not a very common thing.
.
I'm using a somewhat ancient LG G2 and have no desire to upgrade. The only disappointment really is the speaker volume. This is basically from the same exact era as a 5S, but I cant imagine a 5S feeling "slower" or aging worse, but it is possible given the RAM. The problem that makes the 5S seem outdated is probably the display.
Ok, it sounds like the 2014 iPhone 6 is still good and modern.
I would steer you to the iphone 6s and not the one released in 2014.
You could get by on 1 gig of ram but imho that is a shameful amount for a flagship phone. the 16 GB storage on a base model is rather bad as well.
Some may say that the bendgate in 2014 was a non issue but why did Apple upgrade the material to something 2 times as strong for the new 6s if it was really a non-issue?
the S models of iPhones fix issues with the original model of a new iPhone generation. If I somehow decided that iOS was better and started using Apple phones I personally wouldn't get a 6 or 6 plus, I'd get the 6s or 6s plus
You wrote this:
As a generalisation it's clearly incorrect. My phone gives me 4-6 days battery life as it always has done. The smartphone that I upgraded from is a year older than my N5 and my mother gets about 8 days of battery life out of it.
Li-ion does suffer from decreased battery life over a long-enough period of usage / charging cycles, but it's a clear case of YMMV. Stop making silly generalisations; I'm sure there are plenty of other people on this forum with two-year-old phones that aren't in desperate need of battery replacement.
Also, in case you misunderstood, my "what do you mean" comment was directed at someone else, beneath the quote I was responding to.
Goodness gracious, 4 days of battery life? Please share your secrets.
Why not? "3D Touch" or whatever Apple calls Force touch does different things depending on the app as well.
LOL WHAT
autocorrect is fing HORRID on the iphones
it pretty horrid on Android as well but its worse on apple
Personally I think iOS' keyboard is far better in terms of auto-correct. It wasn't until recently that Android's own keyboard could auto-correct efficiently when you misspell something with a different # of characters.I wouldn't call it horrid, but it's not bad. It's better than stock android. Windows phone dominates all for KB. And MS bought Swiftkey. Hahaha.
From my experience it's always very logical.
Personally I think iOS' keyboard is far better in terms of auto-correct. It wasn't until recently that Android's own keyboard could auto-correct efficiently when you misspell something with a different # of characters.
I posted a year back about how auto-correct of "accomodate" would fail to correct to "accommodate" because the # of letters didn't match up. I could type with my eyes closed on an iOS keyboard for instance; no such luck on Android. For the record I own both devices.
Also, what's more frustrating recently is with larger devices, Google Keyboard wasn't designed with that in mind. The scaling of the vertical keys makes it harder and harder to tap. I posted about this a while ago too.
I felt the same way about my LG G2 before it started giving me problems.
Now with the iPhone 6s Plus I like it and the speaker volume is loud enough but the vibration is to low.
And your description of what Android does when you press the back button is precisely what is wrong with the back button. It shouldn't do different things like that. The back button should take you one step back in the app you are currently in. The multitasking button should take you to the task switcher to switch back to a previous app and the home button should take you to the home screen. There's no need for the back button to do anything more than go a step back in the current app but they've complicated it by making it do different things depending on context, which you then have to remember. It's a user experience design flaw as it currently stands.
Have you tried changing the vibration pattern of your notifications? By default, the vibration feedback is set to synchronize with the notification sound that's made. I think it's totes amazeballs, but as a result it makes some of the notification tones have a really short and soft vibration (such as the default text tone).