Phones Apple's problems with iOS mirror Microsoft's issues with Windows

[epicrayban]

Keep in mind Apple has allowed third party defaults in the form of the keyboard. And yet it's not perfect. For example, when the App Store forces me to input my password (an annoying "security" feature because Apple once again thinks we're all children), it brings up the iOS keyboard instead of the keyboard default I set (Swype). This is also a security feature because of risk of keystroke logging.

So even if Apple allows defaults for other things, who knows how it'll be hampered by what Apple calls security. Or what I call Apple babying its users.

 

[gotluck]

the stock keyboard pin thing is not a problem in my book. it really does offer extra security. perhaps they should allow the user to override it for password entry, but not a huge complaint there IMO. I use swiftkey 100% the time (other than passwords of course) and have the stock keyboard deleted in settings

 

[epicrayban]

the stock keyboard pin thing is not a problem in my book. it really does offer extra security. perhaps they should allow the user to override it for password entry, but not a huge complaint there IMO. I use swiftkey 100% the time (other than passwords of course) and have the stock keyboard deleted in settings

Yeah, it's not a big deal. Just an annoying inconsistency with iOS in the name of security. Lots of inconsistency with iOS in general.

 

[gotluck]

Yeah, it's not a big deal. Just an annoying inconsistency with iOS in the name of security. Lots of inconsistency with iOS in general.

if it really does make it more secure I am generally for it, I guess is what I am trying to say

except when it comes to giving users the ability to downgrade iOS... then F security give me freedom

 

[epicrayban]

if it really does make it more secure I am generally for it, I guess is what I am trying to say

except when it comes to giving users the ability to downgrade iOS... then F security

I hear ya. In theory, it sounds great. But in practice, I find it unnecessary and insulting. Again, this is not just the third party keyboard thing. There are lots of other inconsistencies that I think are unnecessary throughout the iOS experience. I mean, when was the last time Swiftkey or Swype got caught for logging keystrokes?

My main point is, even if Apple finally allows more third party defaults, who knows how truly default it'll be, as evidenced by third party keyboards.

I mean I still hope it happens! I think over time it will, but I wouldn't hold my breath.

 

[gotluck]

I hear ya. In theory, it sounds great. But in practice, I find it unnecessary and insulting. Again, this is not just the third party keyboard thing. There are lots of other inconsistencies that I think are unnecessary throughout the iOS experience. I mean, when was the last time Swiftkey or Swype got caught for logging keystrokes?

My main point is, even if Apple finally allows more third party defaults, who knows how truly default it'll be, as evidenced by third party keyboards.

I mean I still hope it happens! I think over time it will, but I wouldn't hold my breath.

yep, fortunately I'm happy enough with the experience as it is.

android's kinks annoy me more than apple's at the moment

cell standby bug still around, google play services dont like to behave, apps run rampant in the background without greenify & doze isnt aggressive enough IMO,... I could go on Sure it gives you the freedom, but you lose out on the efficiency/standby performance. non-nexus update structure sucks, carrier involvement and lockdown sucks

pick your poison my friend!

 

[spinedoc77]

Keep in mind Apple has allowed third party defaults in the form of the keyboard. And yet it's not perfect. For example, when the App Store forces me to input my password (an annoying "security" feature because Apple once again thinks we're all children), it brings up the iOS keyboard instead of the keyboard default I set (Swype). This is also a security feature because of risk of keystroke logging.

So even if Apple allows defaults for other things, who knows how it'll be hampered by what Apple calls security. Or what I call Apple babying its users.

That's a great point, but it also illustrates part of the reason Apple is hesitant to do this, and yes I'm playing devil's advocate to myself. A good example Swype on iOS, it's horrible, slow, laggy, crashes, doesn't even pop up half the time.

 

[epicrayban]

That's a great point, but it also illustrates part of the reason Apple is hesitant to do this, and yes I'm playing devil's advocate to myself. A good example Swype on iOS, it's horrible, slow, laggy, crashes, doesn't even pop up half the time.

I guess this touches upon the topic of this thread: does Apple need to overhaul iOS?

Maybe something more towards Apple Watch OS? Who knows. I wouldn't hold my breath though!

This is why my interest in iPhones depends mostly on how iOS grows. No matter the hardware advantage, Android OEMs will catch on, then do it better and sell it for less. All the while having the better software. In my opinion, there's almost no need to be on an iPhone if iOS isn't for you.

 

[tbayrgs]

I guess this touches upon the topic of this thread: does Apple need to overhaul iOS?

Maybe something more towards Apple Watch OS? Who knows. I wouldn't hold my breath though!

This is why my interest in iPhones depends mostly on how iOS grows. No matter the hardware advantage, Android OEMs will catch on, then do it better and sell it for less. All the while having the better software. In my opinion, there's almost no need to be on an iPhone if iOS isn't for you.

God I hope not...Watch OS is an inconsistent mess.

 

[AustinIllini]

God I hope not...Watch OS is an consistent mess.

Seconded. The Apple Watch hardware is solid, but the software setup is a complete and total disaster. The "home screen" is completely useless.

 

[tbayrgs]

Seconded. The Apple Watch hardware is solid, but the software setup is a complete and total disaster. The "home screen" is completely useless.

I wouldn't go so far as to call it completely useless but it is less than ideal. My issues relate to the busy nature of just about everything else. For instance, it has two buttons, each tasked with 3-4 unrelated functions. The digital crown is a scroll wheel, a home button (1-click), a last app selector (2-clicks), and used to activate Siri (long press). The secondary button accesses the quick communication hub (1-click), activates Apple Pay (2-clicks), and is a power/lock button (long press). Many functions take far too many touches to accomplish anything--for example, if I get a Message and want to reply, I have to click reply, then select from predetermined canned response or can select a button for animated emoji or a mic button. If I choose voice reply, I dictate my message, hope Siri get's it right (she's actually pretty good on the watch), then click 'Done', at which point I'm give the choice of sending as a voice dictation or actually text message, requiring yet another click.

Thankfully, as mentioned, I find Siri quite good and significantly quicker to complete the same tasks. I usually just use her to complete any required actions, generally because using touches in just too cumbersome. But sometimes, voice actions just aren't ideal or convenient.

I'm not sure how they could clean it up and simplify it but I'm hoping something significant is done for Watch OS 3.0.

 

[cube]

The definition of junk: IO1_INITIALIZATION_FAILED

 

[cube]

The definition of half-baked:Crash in AppleHFS.sys

 

[Michael Goff]

Is it bad that part of the reason I even like iOS is because of said control?

 

[macrem]

I mainly use iOS and also Android. I recently started using an internet radio app instead of iTunes because Apple took away radio channels but thats a very rare exception. Apple apps are the best imo. Apple tends to alternate between adding new features and polishing those features to be very effient which is why everything runs so smoothly even on less powerful hardware offering great battery life while being very feature rich. Another bs article trying to be controversial. Development techniques have improved dramatically eliminating a lot of the problems that led to Windows spaghetti code issues from trying to develop something too big with waterfall processes.