As a former 3G owner that had an unusable phone with Apple's last update for that hardware, I welcome not being included in the updates for my iPhone 4.
Well, the iPhone 4 and iPad 2 don't support 4G like networks.
And this isn't fragmentation?
To have a proper answer please do:
1. Get a degree in the field of science, math and engineering
2. Become an expert in what you do
3. Apply for work at apple
4. Become a leading technical expert at apple
5. be part of the creative team that decides what is good and what is not for ios and apple hardware
Then you'll have the answer to the question that you posed above.
When Apple talks about fragmentation, they're referring to the fact that developers have to make multiple versions of their apps to support all the Android devices.
To have a proper answer please do:
1. Get a degree in the field of science, math and engineering
2. Become an expert in what you do
3. Apply for work at apple
4. Become a leading technical expert at apple
5. be part of the creative team that decides what is good and what is not for ios and apple hardware
Then you'll have the answer to the question that you posed above.
FaceTime over 3G........
Goodbye Tango.
Coming to the iPhone 3GS.....iOS 6 Lite
Coming to the iPhone 4.....iOS 6 Basic Edition
Coming to the iPhone 4S.....iOS 6
Coming to the iPhone 5.....iOS 6 Premium Edition
-Kevin
Welcome to having hardware dictate what you can do with your software. If it doesn't perform really well in testing, Apple won't let it out in the wild or else you'll have X million complainers. [Begin rants on "Apple updates its products too fast!"]
Yes, but developers already have to do that on iOS, and it is just going to get worse. Look at some universal games for example. I have a few games where there are separate files included for 3rd gen iOS devices, 4th generation mobile devices, extra iPad 1 files, 4S sgx545mp2 files, additional items for the iPad 2, and now, extra high res iPad 3 graphics.
As an Android user, I must say the fragmentation isn't nearly as bad or even as noticeable as Apple claims it to be. I've never come across an app that hasn't worked on either of my Android devices.
I know it sucks to miss out on new features but trust me, as a previous owner of an iPhone 3G, you're better to miss out on features than have a slow and buggy system. iOS 4 crippled the 3G, so I sold it and refused to get another iPhone once they announced they were providing no more updates. My advice to iPhone 3Gs owners would be to not upgrade to iOS 6 at all.
To have a proper answer please do:
1. Get a degree in the field of science, math and engineering
2. Become an expert in what you do
3. Apply for work at apple
4. Become a leading technical expert at apple
5. be part of the creative team that decides what is good and what is not for ios and apple hardware
Then you'll have the answer to the question that you posed above.
This lack of support on the iphone 4 really sucks eggs!
Total and complete Bulls**t.
I'd really like to see hardware justification as to why not. Please, someone prove to us the reasons.
![]()
Actually, no, it's not.
When people talk about fragmentation they're usually always talking about it from a developer standpoint. You know, when you make an app, how many versions to you have to make?
None of this has anything to do with that. Whether or not a user's iPhone can do FaceTime over 3G doesn't alter how you make your app.
Uses of API Level in Android
The API Level identifier serves a key role in ensuring the best possible experience for users and application developers:
It lets the Android platform describe the maximum framework API revision that it supports
It lets applications describe the framework API revision that they require
It lets the system negotiate the installation of applications on the user's device, such that version-incompatible applications are not installed.
Each Android platform version stores its API Level identifier internally, in the Android system itself.
Applications can use a manifest element provided by the framework API — <uses-sdk> — to describe the minimum and maximum API Levels under which they are able to run, as well as the preferred API Level that they are designed to support. The element offers three key attributes: