Boy iOS 7 sucks

[cerebus]

In my experience with iOS7:
iPhone 4 - barely usable
4s - pretty decent
iPad Mini - works fairly well but seems to get some memory issues
iPad3 - sluggish
iPad4 - no problems
iPad Mini 2 - butter smooth and beautiful.

It's really made for newer devices. There's some fairly sophisticated graphical stuff happening in iOS7. I'm not sure what you're on about with the whole can't find apps in the app store thing though...

 

[cerebus]

That doesn't seem right.

It seems pretty accurate to me. I went from iPad3 to iPad4 and there's a significant speed difference.

 

[biometrics]

Bull sh it

iPhone 4 fine
iPad 3 fine

 

[cerebus]

Bull sh it

iPhone 4 fine
iPad 3 fine

Only if you completely turn off motion effects. Even then they're both pretty herky.

 

[[)roi(]]

Obviously you haven't used iOS 7 before because if you did you would know that chrome is not the only app that crashes. The whole OS crashes occasionally. Funny how when an app crashes on Android then it's Android and if the same happens to iOS then the developer is the problem. Go figure

Whoa there!; you certainly don't know me well enough to parcel me into such a generalization.

Btw the choice of OS (Android, iOS or any other) has no bearing on oxymoronic statements.

Apps crash primarily because of crap coding; and whilst Android's Java VM is arguably better shielded against bad memory management re automatic garbage collection, even then its not bullet proof against badly tested code.

Apple's Objective-C: a lower level language, which arguably offers better performance with a lower memory footprint (vs Android) but that comes at a price re a greater degree of coding complexity i.e. Its far easier for developers to make mistakes. Apple FYI fairly recently introduced a few enhancements to objc to try to alleviate some of this complexity (e.g. ARC, literals. ...), but even with that; objc being a lower level language will always remain a far more complex environment vs. that of Android's Java.

On the OS bit; Obviously any OS update is always prone to a fair share of undiscovered bugs (but this is no different for Microsoft, Google or any other); hence with iOS7 we've already received more than 1 update to alleviate these issues -- but no update is a magic wand to fix all App issues (bad coding remains bad)

Anyway let's forgo the drama; 7.1 is due shortly -- whIch btw in the betas I've been testing is proven to be very stable.

 

[ngwe23]

Whoa there!; you certainly don't know me well enough to parcel me into such a generalization.

Btw the choice of OS (Android, iOS or any other) has no bearing on oxymoronic statements.

Apps crash primarily because of crap coding; and whilst Android's Java VM is arguably better shielded against bad memory management re automatic garbage collection, even then its not bullet proof against badly tested code.

Apple's Objective-C: a lower level language, which arguably offers better performance with a lower memory footprint (vs Android) but that comes at a price re a greater degree of coding complexity i.e. Its far easier for developers to make mistakes. Apple FYI fairly recently introduced a few enhancements to objc to try to alleviate some of this complexity (e.g. ARC, literals. ...), but even with that; objc being a lower level language will always remain a far more complex environment vs. that of Android's Java.

On the OS bit; Obviously any OS update is always prone to a fair share of undiscovered bugs (but this is no different for Microsoft, Google or any other); hence with iOS7 we've already received more than 1 update to alleviate these issues -- but no update is a magic wand to fix all App issues (bad coding remains bad)

Anyway let's forgo the drama; 7.1 is due shortly -- whIch btw in the betas I've been testing is proven to be very stable.

All of this stuff is way over my head. All i know is that my iPad Air is prone to crash vs my Nexus 5 for example. I just don't get why people like you are so keen on defending Apple. Frankly I am disappointed because I expected better from Apple. Maybe because I have always been told that iOS is rock solid and fluid etc. Don't get me wrong I love my iPad. It is a great piece of hardware that is let down by the software.

 

[[)roi(]]

Bull sh it

iPhone 4 fine
iPad 3 fine

I test on all them; and there certainly is a distinguishable performance variation which in many cases requires some rethinking re code optimization.

That said I certainly agree that there's a fair bit of exaggeration re the iPad 3's sluggishness; for me there's no discernible issue.

The iPhone 4, however has clearly outlived its usefulness (and yes I its rather sluggish IMO), hence I've chosen to exclude it from App testing / certification.

 

[DrJohnZoidberg]

Bull sh it

iPhone 4 fine
iPad 3 fine

My iPad 3 is sluggish and I did a fresh install when iOS 7 came out.

 

[[)roi(]]

All of this stuff is way over my head. All i know is that my iPad Air is prone to crash vs my Nexus 5 for example. I just don't get why people like you are so keen on defending Apple. Frankly I am disappointed because I expected better from Apple. Maybe because I have always been told that iOS is rock solid and fluid etc. Don't get me wrong I love my iPad. It is a great piece of hardware that is let down by the software.

Strange, you seem to ignore the paragraphs about Android.

I certainly will choose to correct misunderstandings or flagrant over dramatization of issues (yes I imply you in this case), and this "defense" as you put it is irrespective of platform; both of which I actively develop on, and hence I find your statements to be trumped up in both cases.

Naturally the reasons underpinning every computing issue is going to be complex,...

 

[[)roi(]]

My iPad 3 is sluggish and I did a fresh install when iOS 7 came out.

And mine's not?

 

[ngwe23]

Strange, you seem to ignore the paragraphs about Android.

I certainly will choose to correct misunderstandings or flagrant over dramatization of issues (yes I imply you in this case), and this "defense" as you put it is irrespective of platform; both of which I actively develop on, and hence I find your statements to be trumped up in both cases.

Naturally the reasons underpinning every computing issue is going to be complex,...

I am not ignoring anything. All I know is that of the two devises I own, iPad and nexus 5, one of them crashes for no reason at all. That may be acceptable to you but not to me, esp if I am doing light tasks like browsing the net. But I get it Apple does no wrong it seems.

 

[[)roi(]]

I am not ignoring anything. All I know is that of the two devises I own, iPad and nexus 5, one of them crashes for no reason at all. That may be acceptable to you but not to me, esp if I am doing light tasks like browsing the net. But I get it Apple does no wrong it seems.

When I find an App that crashes I delete it, and look for another. So if Chrome is the problem, try something else.

It's not normal to experience a high level of crashes on iOS (including iOS7); I certainly don't experience this -- but then that's probably because I tend avoid any notoriously buggy ones, and/or ones where the developer is not known to release frequent updates.

For example: Whilst Google provides frequent updates, Chrome's forums are certainly not devoid of complaints about its stability -- hence as I said not all issues point to the OS.

 

[Keeper]

One thing I personally learned with Apple is to never upgrade the devices.
I prefer a smooth UI over a new feature or two.

They make their older gen devices slower with upgrades to get you to buy their new hardware.
Why do you think they designed it so you can't downgrade? (well, without hacking and SHSH blobs and whatnot)

just my 2c.

 

[[)roi(]]

One thing I personally learned with Apple is to never upgrade the devices.
I prefer a smooth UI over a new feature or two.

They make their older gen devices slower with upgrades to get you to buy their new hardware.
Why do you think they designed it so you can't downgrade easily?

just my 2c.

As with any OS; it's often a risk to immediately update to new releases.

With Windows the advice was always to wait for Service Pack 1; as iOS / Android increase in complexity, the advice is often much of the same; the difference is that mobile is evolving much faster including complete obsolescence.

 

[SauRoNZA]

It better improve. I bought my first Apple device 2 weeks ago (iPad Air) and I am not impressed. Setting aside annoyance like not knowing which keyboard an app will bring up, I find it crashes a lot. Open a few tabs on Chrome and bam, it crashes. I think Apple should have done more rather than release what seems like a Beta version.

Sounds like Google is to blame, not Apple.

Why not test drive Safari? You might just like it.

 

[SauRoNZA]

Bull sh it

iPhone 4 fine
iPad 3 fine

iPad 2 just fine as well.

I'm sure in a situation like Droid's where you have them all side by side you'll notice, but for actual usability I have zero issues.

It's a bit like two fancy TV's in the shop. Next to each other the more expensive one is better, but at home by itself the cheaper one you bought is the best TV in the world.

 

[cerebus]

One thing I personally learned with Apple is to never upgrade the devices.
I prefer a smooth UI over a new feature or two.

They make their older gen devices slower with upgrades to get you to buy their new hardware.
Why do you think they designed it so you can't downgrade? (well, without hacking and SHSH blobs and whatnot)

just my 2c.

There's two possible approaches they could take:
1. Design iOS to support devices that are 10-20x slower than current gen models
2. Design iOS to take advantage of the capabilities of current gen devices, which are 10-20x faster than old models.

There isn't another, no-compromise option. Obviously Android has been taking the first approach but at the cost that the UI isn't advancing at all: animations and rendering of objects are timid at best. There's no great conspiracy at work though; it's a design decision to favour progress.

 

[[)roi(]]

There's no great conspiracy at work though; it's a design decision to favour progress.

Unfortunately Apple by their own actions, almost immediately stop certifying prior builds when releasing a new update, gives an impression that their approach is more stick than carrot.

Obviously Apple has taken this approach to try to curb the illegalities of the jailbreaking fraternity; or more specifically: cracked apps that avoid payment to both Apple and its developers. Apple knows to well that the success of its stores depend quite a bit on the developer's belief that payment for use is assured.

Arguably this and other mechanisms against jailbreaking have proven quite effective, unfortunately it came at a cost to all Apple's customers.

 

[cerebus]

Unfortunately Apple by their own actions, almost immediately stop certifying prior builds when releasing a new update, gives an impression that their approach is more stick than carrot.

Obviously Apple has taken this approach to try to curb the illegalities of the jailbreaking fraternity; or more specifically: cracked apps that avoid payment to both Apple and its developers. Apple knows to well that the success of its stores depend quite a bit on the developer's belief that payment for use is assured.

Arguably this and other mechanisms against jailbreaking have proven quite effective, unfortunately it came at a cost to all Apple's customers.

It's not just cracked apps. From the developer standpoint they want to be able to ensure that as many customers as possible are using the latest version of their app. There's security and feature concerns when they have to deal with multiple versions across the spread of handsets. That's the core of the fragmentation problem Android is battling with atm. So.. Apple take a pro-developer stance; again it's either/or. You have to make a decision one way or the other.

 

[[)roi(]]

It's not just cracked apps. From the developer standpoint they want to be able to ensure that as many customers as possible are using the latest version of their app. There's security and feature concerns when they have to deal with multiple versions across the spread of handsets. That's the core of the fragmentation problem Android is battling with atm. So.. Apple take a pro-developer stance; again it's either/or. You have to make a decision one way or the other.

As a developer it honestly doesn't concern me that much, I took the decision a long time back to not support anything but the latest SDK for obvious reasons: new feature support + because it indirectly stems the tide of usage from JBs (JBs are usually a version or 2 behind)
Also given the option to upgrade at no cost, most customers automatically apply upgrades anyway, encouraged along by Apple's fairly consistent reminders.

Android's problem is more endemic to the complexity behind the scenes of the Android update process i.e. Split of responsibilities between Google, the OEMs, the network provider testing, the huge array of devices, ...

Apple's upgrade path works better, simply because there's less devices and they've assumed full responsibility for everything.

So theoretically if Samsung chose to branch off its own version of Android, incl. replacing the Google extension framework & apps, its feasible to believe they could similarly replicate Apple's up to date model.
The problem however in practice is not so easy to achieve as Google has recently started to incorporate more of Android's new core SDK functionality only under its proprietary licensed extensions framework as opposed to including this in the open source part of Android, essentially making future breakaways unfeasible. I.e. Their recent moves are a clear indication that they don't want more Amazons, hence Android today is far more locked in for OEMs than of yesteryears. Also to note is that the terms & conditions for use of their proprietary extensions, specifically restricts branching off.