iOS Apps Crash More Than Android

[[)roi(]]

I detect dangerously high levels of Apple's Reality Distortion Field. I think the point is very clear to every one "iOS Apps Crash More Than Android" based on data. Android is not as laggy and prone to crashes as popular sentiment suggests. BTW, where are you getting your data on the variance? Care to share, or are these thumb-sucks? Whats is the relevance of the crappy apps and variance :wtf: .

I thought it was obvious, guess not; so let me help you with a bit of maths.
From the article:

• Google's KitKat (4.4), Jelly Bean (4.3), and Ice Cream Sandwich (4.0) have a tendency to crash about 0.7 percent of the time.
• iOS 7 is at 2.1 percent.

Making the difference 1.4% -- For simplicity, I posited 1 million apps in the stores, i.e. variance of 14000.

This statement. :wtf:. Do you have data on "compiled & runtime languages"? How did you calculated the variance?

Again fairly obvious, it's based on a probability, causality to be specific
i.e. it's a well known fact that compiled languages (for example: C++, Objective-c, ...) whilst being faster and enjoying a small resource footprint (vs. runtime languages); come at a cost of extra complexity which in turn makes it far easier for developers to make mistakes; mistakes that lead to app crashes.

Ps. If you still don't believe me, then hear it from the lips of Google:

C++ is the main development language used by many of Google's open-source projects. As every C++ programmer knows, the language has many powerful features, but this power brings with it complexity, which in turn can make code more bug-prone and harder to read and maintain.

http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml

So in the end, it's more likely the only person being affected by some type of reality distortion field is probably you.

 

[johnnysims]

Yes I have to say, my android apps almost never crashes.

 

[johnnysims]

@alatheia Buy an Android phone!

 

[ngwe23]

I thought it was obvious, guess not; so let me help you with a bit of maths.
From the article:

• Google's KitKat (4.4), Jelly Bean (4.3), and Ice Cream Sandwich (4.0) have a tendency to crash about 0.7 percent of the time.
• iOS 7 is at 2.1 percent.

Making the difference 1.4% -- For simplicity, I posited 1 million apps in the stores, i.e. variance of 14000.

Again fairly obvious, it's based on a probability, causality to be specific
i.e. it's a well known fact that compiled languages (for example: C++, Objective-c, ...) whilst being faster and enjoying a small resource footprint (vs. runtime languages); come at a cost of extra complexity which in turn makes it far easier for developers to make mistakes; mistakes that lead to app crashes.

Ps. If you still don't believe me, then hear it from the lips of Google:

http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml

So in the end, it's more likely the only person being affected by some type of reality distortion field is probably you.

WOW. No dude. That is not how you calculated variance. Don't even know where to start...lol. You actually need the whole data set to do that because it is directly related to standard deviation. It used as a measure of the "accuracy" or "dependability" of the data. What you actually calculated is the difference as in (A-B) in percentages :wtf: Ohh boy. Funny I thought in IT you have to do basic Maths. Excuse my confusion then, because you have no idea what you are talking about.

 

[[)roi(]]

WOW. No dude. That is not how you calculated variance. Don't even know where to start...lol. You actually need the whole data set to do that because it is directly related to standard deviation. It used as a measure of the "accuracy" or "dependability" of the data. What you actually calculated is the difference as in (A-B) in percentages :wtf: Ohh boy. Funny I thought in IT you have to do basic Maths. Excuse my confusion then, because you have no idea what you are talking about.

Who said I was using stats; are your assumptions tripping you up?

 

[ngwe23]

Who said I was using stats; are your assumptions tripping you up?

Ha ha nice try. lol. Stop using statistical terms if you dint know what they mean. Simples

 

[[)roi(]]

Ha ha nice try. lol. Stop using statistical terms if you dint know what they mean. Simples

When did I use a statistical term or imply that I was? variance? probability?

Variance

difference, variation, discrepancy, dissimilarity, disagreement, conflict, divergence, deviation, contrast, contradiction, imbalance, incongruity.

Probability

likelihood, prospect, expectation, chance, chances, odds.

You do hopefully grasp that these are commonly used english words, and that there inclusion doesn't automatically imply statistical determinations. Hhhmmm but then maybe I was just giving you too much credit.

 

[Tacet]

@ ngwe23 - if you are really so well versed in statistics, you should have realized from [)roi(]'s first post that he is not claiming to use proper stat terms. Variance will never have a unit of "14000 apps over 1 million". As I'm sure you might know, variance will have a square in the unit. The unit [)roi(] used tells you exactly in what context he used the word "variance".

He is merely interpreting the article itself, showing that the difference between the figures they quote is not extremely large.

 

[ngwe23]

When did I use a statistical term or imply that I was? variance? probability?

Variance


Probability


You do hopefully grasp that these are commonly used english words, and that there inclusion doesn't automatically imply statistical determinations. Hhhmmm but then maybe I was just giving you too much credit.

Please do me a favour and do your research before not after the fact. I have wasted enough of my time, moving along.

 

[[)roi(]]

Please do me a favour and do your research before not after the fact. I have wasted enough of my time, moving along.

Wow :wtf: ... You make assumptions coupled with some derogatory insinuations and now it's all my fault. FFS next time read the entire thread to avoid heckling from the balcony.

Ps. keep in mind what's goes on your head is not always a reflection of reality.

 

[[)roi(]]

@ ngwe23 - if you are really so well versed in statistics, you should have realized from [)roi(]'s first post that he is not claiming to use proper stat terms. Variance will never have a unit of "14000 apps over 1 million". As I'm sure you might know, variance will have a square in the unit. The unit [)roi(] used tells you exactly in what context he used the word "variance".

He is merely interpreting the article itself, showing that the difference between the figures they quote is not extremely large.

Whew reason prevails! Thank you.

 

[Azimuth]

Indeed. Tapatalk specifically dies on me at least once a week on the iPad.

I switched from the paid to a free version to fix this.

 

[Vegeta]

The only time my iPad crashes is when I try to view an unsupported movie on Good Player, otherwise it doesn't crash.

Can't remember the last time any video format was unsupported on any one of my android devices. Could very possibly be never

 

[[)roi(]]

Can't remember the last time any video format was unsupported on any one of my android devices. Could very possibly be never

...and that's applicable because?

Bearing in mind that the post you quoted refers to an App with equally wide media codec support; and btw it's not the only one of it's type.

 

[[)roi(]]

I switched from the paid to a free version to fix this.

Yip must admit to being equally pissed that the paid apps are so badly maintained; crashing far more frequently than the free ones.

 

[R13...]

Can't remember the last time any video format was unsupported on any one of my android devices. Could very possibly be never

I have a 3gp that's not supported on my android phone. Tried VLC and MX player and it will not play

 

[[)roi(]]

I have a 3gp that's not supported on my android phone. Tried VLC and MX player and it will not play

Strange as MX certainly has support for it? I take that it works on your PC? Also have you tried converting it with handbrake? If there's any format issues Handbrake will certainly report it in the logs, but also allow you to convert / repair to a new copy.

 

[R13...]

Strange as MX certainly has support for it? I take that it works on your PC? Also have you tried converting it with handbrake? If there's any format issues Handbrake will certainly report it in the logs, but also allow you to convert / repair to a new copy.

It plays in good player. It's an old Nokia 3gp I wonder if it may be a slightly different format.

 

[SeRpEnT]

What you should know is that Samsung would (if they could) prefer to ship it's devices with less RAM and smaller CPUs; for reasons like: financial, heat generation, battery, etc... Basically Android phones became larger not because of a latent user need, but primarily because of engineering challenges (more RAM & bigger CPUs require for example a larger battery); fortunately for them it was something the Android community was happy to receive.

What a load of toss.
Really? There used to be lots of high powered androids out there. But once bigger screens was introduced it was overs-skedover. The users loved it. Game over.

You mentioned in an earlier post that you own an S4? But from your posts you are extremely negative about android. Why dont you join the sheep and get yourself an iphone?

 

[[)roi(]]

Negative? Mmmhh any chance your reflection confusing you?
Ps. Don't have an S4; four Android tablets though, all used for development / testing.

Maybe you misunderstood I wasn't knocking larger screens, but rather covering Android transition; you need only look at the bridging Android devices i.e. The first devices introduced with more powerful CPUs and extra RAM to deal with lag issues; if you do some research you'll find that some of these were quite notorious for their poor battery life, which was subsequently fixed when larger Android devices were introduced. Samsung's approach was more gradual; yet as specs ramped up so did device size / battery capacity, and in tandem lag became a far lesser issue.