iPhone Why is the iPhone better than Android phones?

[SlCKB0Y]

Only a minor correction, Dalvik doesn't run Java bytecode, Java bytecode is translated to Dalvik bytecode when the app is compiled

Correct. Cheers. The point I was trying to make was mainly with regards to pragmatous:

Now, can anyone see the contradiction in criticising Android for both running apps in a virtual machine AND for the software development issues caused by having many different hardware configurations?

Android is designed to run apps in a virtual machine because Google intended Android to run on numerous different hardware types. The VM allows for hardware abstraction.

The main issue between different Android handsets is screen resolution but, as it turns out, its not that big of a deal.

The exception to this is for applications such as video players with hardware decoding and some games. These types of apps are compiled for specific hardware and use the Android NDK.

 

[Oletros]

The exception to this is for applications such as video players with hardware decoding and some games. These types of apps are compiled for specific hardware and use the Android NDK.

Exactly, NDK apps like the ones you said or games are the ones that have the biggest "fragmentation" problems

 

[flameproof]

Q: Why is the iPhone better than Android phones?

A: It isn't.

 

[hot spare]

Q: Why is the iPhone better than Android phones?

A: It isn't.

Why compare Android to feature phones? iOS is an app launcher. The only thing apple tried to modify is Notification center (shamelessly copied from Android) and Maps.

 

[HappyJB]

Why compare Android to feature phones? iOS is an app launcher. The only thing apple tried to modify is Notification center (shamelessly copied from Android) and Maps.

I downloaded Fake iPhone Launcher on my Galaxy Nexus. It beats iPhone 4s in term of smoothness.

 

[roxxette]

I downloaded Fake iPhone Launcher on my Galaxy Nexus. It beats iPhone 4s in term of smoothness.

 

[HappyJB]

Image

One more buddy. You would get an avatar

 

[Markyboy81]

I've come from an iPhone 4s and have considered the iPhone 5 but one important factor that I don't think anyone has mentioned is price. I picked up a refurbished 16gig galaxy s3 for 350 pounds whereas a new iPhone 5 is 150 pounds more expensive. My s3 doesn't have a mark on it and is as new, yet I doubt there will ever be any refurbished iPhone 5's for sale.
I've now ordered a 64gig memory card for under 40 pounds. The equivalent spec on an iPhone would cost almost 800 pounds!
Don't get me wrong I love apple products, but you can't deny they are over priced, especially when you consider getting more memory.
Maybe the iPhone is a 'better' product. But it certainly ain't twice as good.

 

[blackhand1001]

Problem with android is fragmentation. That is indisputable. It is difficult for amateur developers and even companies to develop for android. Imagine how many devices with android oS there are, imagine the idea of having to test your app on every android device to see if it works, now imagine only the top 3 phones are chosen to develop for because it is infeasible to test the app on every phone. You run into issues where app works for phone x but not for phone y. The app will probably crash for phone z. Now imagine that phone X, Y, and Z all run on different hardware. Good luck debugging.

on iOS you have one hardware software platform to develop for similar to developing apps for windows. It's a lot more intuitive so that is why the apps for iOS are a lot better than android. Also runs faster because it's native coding. At least most apps are native. Some companies try to develop in HTML 5 and that is just a bad idea.

edit:
Also to note on android a lot of companies take shortcuts and develop using XML. XML is interpreted like HTML is. Android is a virtual machine that runs on top of JIT. Just in time compilation. In layman terms all you need to know is that it is slower. SO you have XML code that is interpreted on top of a virtual machine that uses JIT. It's double interpreted and that is why you need such high powered hardware to run android efficiently. In android 4.1 jelly bean they sped up the OS by over-clocking the processor in order to interpret all that garbage so it doesn't appear sluggish. Completely inefficient operating system that will eventually choke itself to death.

Wow, so much garbage thats not true in one post. I don't even know where to start. Jellybean does not overclock the processor, nor does it take the cpu out of the low power state like you say. Second of all, android has never had a problem running multiple resolutions ever. Its not like ios where everything uses absolute coordinates and if apple changes resolution they are forced to do scaling or add black bars. I develop for cm10 and compile builds/submit changes to aosp. All you are doing is spewing anti-android garbage and using buzzwords like java, jit compilation, and VM's to make your post sound informed.

 

[onthecouchagain]

I'm guessing it's hard for dedicated iOS users to accept that Android has caught up and surpassed iOS.

There may be fanboys from both sides in this thread but it seems only one side is willing to talk honestly about both platforms. The other side seems to debating against an Android of yesteryear to prove that iOS is better. Pure obscurantism.

Very revealing.

 

[craftytony]

Wow, a Google search where all the pro Apple links were hand picked out. Quite a few of those have links for opposite findings. Regardless, if your mind is set on something that's all you can see....

He had a question and I provided some answers. If you are in love with Android so much then you should provide those links that show opposite findings. I guess it's just easier for you to troll...

 

[pragmatous]

Yes it does. It's called CPU input boost.

Wow, so much garbage thats not true in one post. I don't even know where to start. Jellybean does not overclock the processor, nor does it take the cpu out of the low power state like you say. Second of all, android has never had a problem running multiple resolutions ever. Its not like ios where everything uses absolute coordinates and if apple changes resolution they are forced to do scaling or add black bars. I develop for cm10 and compile builds/submit changes to aosp. All you are doing is spewing anti-android garbage and using buzzwords like java, jit compilation, and VM's to make your post sound informed.

 

[cynics]

He had a question and I provided some answers. If you are in love with Android so much then you should provide those links that show opposite findings. I guess it's just easier for you to troll...

No I was just pointing out the obvious. I don't need to own an Android device to see what you did there.

Links are fine as a source but you didn't have any input. Why not just say, it's better because you were able to find someone else that says so.

 

[Oletros]

Yes it does. It's called CPU input boost.

Please, stop embarrassing yourself with your lack of knowledge.

There is no overclocking, boosting the cpu to care for the touch input from its actual state is not overclocking, the cpu never exceed its maximum nominal frequency

 

[blackhand1001]

Yes it does. It's called CPU input boost.

Its not why it makes programs run faster. You can set the governor to ondemand and it is still smooth. Also cpu input boost has nothing to do with what goes on when your finger is not touching the screen nor does it overclock the cpu.

 

[pragmatous]

"the OS will apply a CPU “input boost” at the next touch event, to make sure the CPU is ramped up to speed so there’s no latency." - http://pocketnow.com/2012/06/27/what-is-googles-project-butter-and-why-its-so-awesome/

Perhaps "overclock" is the wrong term but it does boost the clock of the CPU to max.

While that seems like an awesome addition I question why it's needed.

Its not why it makes programs run faster. You can set the governor to ondemand and it is still smooth. Also cpu input boost has nothing to do with what goes on when your finger is not touching the screen nor does it overclock the cpu.

 

[blackhand1001]

"the OS will apply a CPU “input boost” at the next touch event, to make sure the CPU is ramped up to speed so there’s no latency." - http://pocketnow.com/2012/06/27/what-is-googles-project-butter-and-why-its-so-awesome/

Perhaps "overclock" is the wrong term but it does boost the clock of the CPU to max.

While that seems like an awesome addition I question why it's needed.

Its really not needed. Using the ondemand governor works fine which doesn't have CPU input boost. It also doesn't always get used even on interactive.

 

[Rodimus Prime]

"the OS will apply a CPU “input boost” at the next touch event, to make sure the CPU is ramped up to speed so there’s no latency." - http://pocketnow.com/2012/06/27/what-is-googles-project-butter-and-why-its-so-awesome/

Perhaps "overclock" is the wrong term but it does boost the clock of the CPU to max.

While that seems like an awesome addition I question why it's needed.

and the kicker is more than likely iOS does a trick like that as well. Big time considering how important Apple makes everything not lagging at all. For the most part project butter was optimization to how the UI code works.

 

[cynics]

"the OS will apply a CPU “input boost” at the next touch event, to make sure the CPU is ramped up to speed so there’s no latency." - http://pocketnow.com/2012/06/27/what-is-googles-project-butter-and-why-its-so-awesome/

Perhaps "overclock" is the wrong term but it does boost the clock of the CPU to max.

While that seems like an awesome addition I question why it's needed.

Android has a lot going on. iOS freezes pretty much everything to prioritize user input. Easiest example is a web browser, if you catch it before it done loading and start scrolling it will stop downloading and loading until you stop scrolling. The alternative is the opposite, the app will lock out user input completely until its done. Tapatalk is the easiest example, when its loading you are waiting.

Android can/will do both load and allow user input.

I don't mind the way either do it. I like Android on a tablet because I try to use it like a laptop. I prefer iOS on a phone because I'm rarely trying to do multiple task and have things running in the background.

 

[batting1000]

It doesn't have the best CPU and GPU in the market. There are different benchmarks out there that show different results. In one benchmark Galaxy S3 got 1800 with geekbench, and the others got 1600-1700, so it's quite the same.

What matters is real world performance, not benchmarks that spew out numbers which don't translate to how the device actually performs in everyday use.

No, it's not. Android 4.1 (Jelly Bean) works as good as iOS.

That's subjective.

Samsung's S3 battery is better. It has super compact and light feel because you have tiny screen. Yes, Samsung has plastic cover on the back, but you can change your battery if you need too. In iPhone you can't.

Subjective as well. Sure the GS3 battery may have more mAh, but again, that doesn't automatically translate to better real world battery performance. Depends on how you use it. As a side note, I've never encountered a situation with my iPad, old iPod touch 4 and 2G, or iPhone 4S/5 where I had to remove the battery or felt the need to.

23% difference. All major apps are available on both platforms.

Ok. Find me apps like Tweetbot, OmniFocus, Clear, Reeder, etc, on the Play Store. The app quality just doesn't compare to iOS. Look at the Chrome app for iOS. It supports more devices / OS versions through iOS than it does on it's native platform (Android)...

After a week with a 4.5+ inch screen, you would never want to comeback to 4 inch and below screens. It would even look funny to you.

Also subjective. I went from the iPhone 4S to the Epic 4G Touch (Sprint's GS2) and back to the 4S (and now the 5) with no issue.

^

----------

Why compare Android to feature phones? iOS is an app launcher. The only thing apple tried to modify is Notification center (shamelessly copied from Android) and Maps.

So I guess that means Android / Google "shamelessly" copied slide to unlock? Of course not, Google would never do that!

Your arguments are invalid.

 

[pragmatous]

They're putting a bandaid on it with tripple buffering and forcing a CPU clock increase.

I would argue that iOS doesn't have to do that because it does things smarter than android.

Android may never be as smooth as iOS, says ex-Googler

and the kicker is more than likely iOS does a trick like that as well. Big time considering how important Apple makes everything not lagging at all. For the most part project butter was optimization to how the UI code works.

 

[Vetvito]

Some of you are acting like you're debating for your life. It's just mobile OS's people, get a grip.

Some like one over another, neither is better. No one is wrong for their choice.

 

[roxxette]

Some of you are acting like you're debating for your life. It's just mobile OS's people, get a grip.

Some like one over another, neither is better. No one is wrong for their choice.

Beat me to it ! Get a G R I P people

 

[ixodes]

Problem with android is fragmentation. That is indisputable. .

While I respect your personal choice to believe this, it's completely irrelevant.

Yet it is true that hoards of iPhone lovers have propagated this as a problem, I've had great Android experiences with every rev of the OS since ver 2.2.

Only the obsessed "have to have the latest" update. Heck my brother is still enjoying iOS 4.3.x. And how could that be? Simple really. It does everything he wants it to do, so there's no reason to upgrade.

I've given him demo's of every rev of iOS to date so he can see what's new. Nothing he's seen is of interest.

I can relate. All my 2010 MBP's & MBA's are on Snow Leopard 10.6.8 by my choice.

The 2012 ver of Mountain Lion I'm running is only there because it was preloaded on the MBA as shipped by Apple.

So you see, it's no different than anything else. It's all a matter of preferences.

Android vs iPhone in general ?

I like the both equally, that's my truth. Each has their Pro's & Cons, which makes it fun to have both. Why Compare?

I have no reason to.

If you're only going to buy one, get what you want. It's as easy as that.

 

[SlCKB0Y]

Android may never be as smooth as iOS, says ex-Googler

You're quoting an article which was written in December last year just after the release of Ice Cream Sandwich and over 6 months before Jelly Bean which resolves the issues discussed in the article.

Furthermore, the article is based on opinion, not from a person who was ever a Google employee, but from a student who was doing an internship at Google.