What you fail to realize in your stupidity is that Apple uses a different type of NAND ( PCIe and NVMe ) which is much more efficient vs the UFS or eMMC NAND standard utilized by Android smart phones. So in summary, (or in other words NAND for dummies) all NAND drives aren't created equal which reflects the superiority of Apple's NAND drives.
"At this point is almost goes without saying that storage performance is important, but in a lot of ways the testing here is still in its early days. In the case of the iPhone 6s we’ve discussed what distinguishes its storage solution from others in this industry, but for those that are unaware the iPhone 6s uses PCIe and NVMe instead of a UFS or eMMC storage solution. In a lot of ways, this makes the storage on board closer to the SSD that you might find in a more expensive PC but due to PCB limitations you won’t necessarily see the enormous parallelism that you might expect from a true SSD. In the time since the initial results we've found that all of our review units use Hynix-supplied NAND. In order to test how this storage solution performs, we use Eric Patno’s storage test which allows for a simple storage test comparable to AndroBench 3.6."
The Apple iPhone 6s and iPhone 6s Plus Review
To further elaborate:
"The first, and probably biggest change that I haven’t seen addressed anywhere else yet is the storage solution of the iPhone 6s. Previous writers on the site have often spoken of Apple’s custom NAND controllers for storage in the iPhone, but I didn’t really understand what this really meant. In the case of the iPhone 6s, it seems that this means Apple has effectively taken their Macbook SSD controller and adapted it for use in a smartphone. Doing some digging through system files reveals that the storage solution identifies itself as APPLE SSD AP0128K, while the Macbook we reviewed had an SSD that identified itself as AP0256H."
While the name alone isn’t all that interesting, what is interesting is how this SSD enumerated. One notable difference is that this storage solution uses PCI-E rather than SDIO, so it’s unlikely that this is eMMC. Given the power requirements, it’s likely that this isn’t the same PCI-E as what you’d see in a laptop or desktop, but PCI-E over a MIPI M-PHY physical layer. By comparison, UFS's physical layer is MIPI M-PHY as well, while the protocol is SCSI. In essence, MIPI M-PHY is just a standard that defines the physical characteristics for transmitting signal, but SCSI and PCI-E are ways of determining what to do with that channel.
The iPhone 6s in turn appears to use NVMe, which rules out both UFS and traditional eMMC. To my knowledge, there’s no publicly available mobile storage solution that uses PCI-E and NVMe, so this controller seems to have more in common with the Macbook SSD controller than anything in the mobile space. It doesn’t seem this is an uncommon idea though, as SanDisk detailed the potential advantages of PCIE and NVMe in mobile storage at the Flash Memory Summit a month ago.
Overall, NAND performance is impressive, especially in sequential cases. Apple has integrated a mobile storage solution that I haven’t seen in any other device yet, and the results suggest that they’re ahead of just about every other OEM in the industry here by a significant amount.

iPhone 6s and iPhone 6s Plus Preliminary Results
iPhones have always had better write speeds than the rest, but the NVMe NAND has only been used during this generation. The wording used makes it seem as if the iPhone is the only one whom uses NAND drives, which it isnt. The argument that the NAND that apple sources is superior is not one that was brought forth. Be precise with your words, son
Well, please explain to The Coli what specific hardware does Apple themselves produce/manufacturer for it's iPhones?
I'll be waiting for your response ..........................
Apple owns no fabs, but they design most of the chips used in the phone...this is common knowledge.
Apple mobile application processors - Wikipedia, the free encyclopedia
Whether a phone uses OLED vs LCD, the cpu usage does not change. Please support this idiocy with a link, since you seem to like to do that.
Breh,

This ludicrous stupidity you've written above doesn't even deserve a legitimate reply!
Likewise.
Your point is simply irrelevant because no matter how Dalvik performance declines under the Android platform, it's still a process virtual machine running Java that's less efficient & slower than the iPhone's Objective- C which is again one of the main reasons the iPhone can perform better with less powerful hardware.
And Dalvik hasn't been used by Google for Android since 2013 (Kit Kat)
I dont follow Android much, but I do remember reading that they dont use that translator anymore. No problem admitting i was wrong with that, but ultimately it does not matter, as the point was that Java is not inherently slower than ObjC. The distinction is native app vs non native apps, and all the benchmarking apps, which show the iPhone winning most the competitions, are written to run natively instead of being translated.
In other words, your virtual machine reasoning for Android being slower in a lot of cases, is bullshyt.
Let me know when you've developed even some rudimentary application in Java or ObjC
No, you're
absolutely wrong. Again, since you're a self proclaimed expert on cellular phones & their inner workings

this should be common knowledge that disabling a app on Android OS doesn't always prevent it from running again on the system. In fact this is a common behavior &
issue from Android phones/platforms (especially older Android phones) which has been discussed ad nauseum & can be verified though out the Internet.
As I said, its a bug. In normal cases, the app is not simply "temporarily disabled".
Both of your premises are also completely flawed. It should be common sense that any additional unneeded bloatware apps on your OS effects the ram, cpu & battery life, particularly as a lot of the rouge carrier bloatware apps steadily decline the performance over time & eat up the smart phones processing power.
Again simple computer tech 101.
The bloat from T-Mobile which was installed on my S7 Edge has had minimal effect as opposed to the unlocked version a friend loaned to me (dev phone). The performance degradation, if any, is
negligible.
And the performance aspect along with the OS running efficiently without issues over a extended period of time is exactly why Apple doesn't allow the carriers to add additional bloatware on the iPhone.
You're not schooling anyone breh with this defective, faulty garbage you presented.
Performance is no longer the main reason for preventing bloatware. Its money and power. Apple exerts complete control over its platform. Even if apps did come preinstalled, iOS environment prevents apps from being active in the background without some sort of user interaction first.
Go learn technology and not shyt you read in tech forums, smart dummy