There's a few reasons why Apple has yet to see a penny out of me, and this is DEFINITELY one of them!
So no change there then. Lets face it it makes absolutely no difference to Apple what Android fanboys think... they aren't potential customers anyway. What matter is what the normal consumer with no team affiliation thinks.
5 million Android phones that are physically larger than iPhones will create tonnes of unnecessary plastic and precious metal waste. But I don't see you complaining about that.
Android tablet apps are typically crap, because the developers, like you, don't recognise that very much different sized screen requires a UI redesign, not simply a re-layout.
The classic example: A list view. Some elements are left aligned, some are right aligned. Looks fine on a phone. On a tablet, you have a little content on the left, then a huge great expanse of white space, then a bit of content on the right. It works, but it's ugly, and doesn't take advantage of all that extra width available.
If you wrote software for iOS you would understand that developers do have to write code that is specific to the different OS versions they want to support.
I am an iOS developer, and mostly you don't. For the screen size. you code for points and it works for both old style screens and retina. You have to include 2 sets of bitmaps for graphics, but that's graphics work, not coding. And for the new longer screen, mostly apps are tableviews, and they'll just work without the programmer doing anything. In some cases you might need an alternate storyboard, if you chose a different layout when you have the longer screen.
This is forward and backward compatibility work, not fragmentation issues.
This differs from the case of the iPhone/iPad distinction, which IS fragmentation, and DOES require coding work.
Again, the distinction is that fragmentation is PARALLEL development of different branches of a product. Development of a single product through successive version is not fragmentation. Never has been.
Think of it as SCM - a single branch with successive versions is not fragmented. Multiple parallel branches are fragmentation.
I guess it all depends on what you mean by "fragmentation".... But probably some people think "Two models is not fragmentation, because that is easy to handle. Its not fragmentation until it becomes a real burden".
No, my definition is not quantiative, it's objective. And it's what is meant by fragmentation in the industry. Fragmentation is parallel branches, it isn't successive versions.
The iPhone 1 and iPhone 3G are no longer supported by older versions of the OS. And there are also people who have used jailbreak and ultraSn0w or something like that to unlock their device to use on other carriers who will always be behind the general population until the latest OS version is exploited.. There are also people that just don't choose to upgrade their OS for a myriad of reasons. So yes, there is fragmentation on iOS and as a developer you have to choose which devices you want to support via the API that you use. And I know dozens of people who are still using a 3G or an iPod Touch 1st Gen. There are millions of those old devices out there. The question is, how many are still in use and which ones do you feel required to support as a developer?
None of that is fragmentation. Fragmentation is multiple parallel developments. It's not new devices having new or improved features not present on devices that are no longer sold. Fragmentation is when there are PARALLEL incompatible models, not SERIAL changes in a single product line. What you are describing is forward and backward compatibility, not fragmentation.
I can tell you now that Amazon just released a new version of their Amazon Instant Video app to fix bugs in iOS 4.0 and I see plenty of people writing negative reviews because an app doesn't support iOS 3 or 4 properly.
So it lacks backward compatibility. It's not fragmented. These are different issues.
Parallel products does not mean "on sale at the same time", it means "in use at the same time". Just because they stop selling the old Iphone model it does not mean all the people who bought those will stop downloading apps.
No that's not it. Think of it like SCM. Successive versions isn't fragmentation. Multiple live branches is fragmentation.
Models following one after another IN SERIES do not cause difficult problems. It's perfectly ordinary backward and forward compatibility work. For each feature, it either stays the same or improves in each model. It's easy enough to factor in a change in behaviour at a certain model number. e.g. All models before X do this... else do that...
The problem is products IN PARALLEL. From different manufacturers or different lines. iPhone vs iPad is fragmentation. iPhone 5 vs iPhone 4s isn't.
There will be apps that are for the original screen size, the new screen size and the ipad. That seems somewhat fragmented to me.
Apps for the original screen size work on the new devices. You're hypothesising that there will be apps that work on the new screen size that don't work on the old, but it's unlikely - there's no benefit to the app developer to do that, and it's easy enough to support both.
There are no iPhone apps that don't run on the iPad... Support for iPhone apps is built in to the iPad.
For sure there are some apps that are iPad only, but that's always been true. They are very different devices - it's not sensible to flag "fragmentation" up as an issue there.
Fragmentation isn't an issue for Apple mobile devices, however much some people wish it was.
The bigger point he's missing is that he doesn't even understand what fragmentation means. Fragmentation is multiple parallel products that have incompatibilities. It's NOT current devices currently being on sale being different from older models in the same series let along devices that are no longer on sale. You can argue that there's iOS device fragmentation as far as iPhone vs iPod Touch vs iPad. But the iPhone 3GS and the iPad 1 aren't even on sale any more.
Android is horribly fragmented because there is a huge number of current products with many hardware incompatibilities AND many don't even ship with a recent version of the OS. However much Android fanboys wish iOS devices had the same problem, they just don't.
1) That isn't something you "run". OP was talking about one or more apps.
2) Your complaint is one of someone looking at a spec sheet, not looking at a device. This is a mobile phone with pixels smaller than the eye can differentiate. No one is looking at an actual movie playing on that and complaining it's not 720p.
... to every organization with staff: tablets are for consumption, not production.
No, that's not where the cut-off is.
Tablets are not good at text entry and editing. They're great for lots of other things, both consumption and production. Better than a laptop for a lot of them. For example sketching, filling out forms that are mostly checkboxes or multiple choice, grabbing a photograph to go with data, creating music.
I agree. If the list came from the developers they would have matched 100% of the list in their database.
Good grief. Slashdot really ought to do an IQ check before they allow people on here. One second of thought for an averagely intelligent person would give them at least one reason what that's not true.
Your explanation is easily falsified by the fact that the list contains user info from around the world, not just Americans. So that isn't the explanation for the relatively small number of records.
The next question should be, "Why did Blue Toad have 11 miilion UDIDs from Apple and where did they get it from?"
Because Blue Toad like many other Apple App developers used to have their iOS app send their servers the UUID and some personal information. It became against the rules some time ago, but this list dates from when it was still a common practice.
The UUIDs and the info did not come from Apple.
Several people pointed this out in the original story comments, but looney-tunes conspiracy nuts chose not to believe it.
All we know now is where the data likely originated -- which is precisely where everyone assumed it originated anyway (a single developer list).
How quickly people forget. The original slashdot story a comments were only a few days ago, and there were many people who were assuming that Apple willingly gave (or sold) it to the FBI.
For sure they were idiots that like to seize any opportunity to call Apple evil. But no, everybody didn't assume this came from a 3rd party developer. Only the more intelligent people realised that.
Slashdot Mirror
And yet if it was Apple it would sound like a lose/lose to you.
There's a few reasons why Apple has yet to see a penny out of me, and this is DEFINITELY one of them!
So no change there then. Lets face it it makes absolutely no difference to Apple what Android fanboys think... they aren't potential customers anyway. What matter is what the normal consumer with no team affiliation thinks.
5 million Android phones that are physically larger than iPhones will create tonnes of unnecessary plastic and precious metal waste. But I don't see you complaining about that.
As I said: "Android fanboys wish iOS devices had the same problem, they just don't."
Android tablet apps are typically crap, because the developers, like you, don't recognise that very much different sized screen requires a UI redesign, not simply a re-layout.
The classic example: A list view. Some elements are left aligned, some are right aligned. Looks fine on a phone. On a tablet, you have a little content on the left, then a huge great expanse of white space, then a bit of content on the right. It works, but it's ugly, and doesn't take advantage of all that extra width available.
If you wrote software for iOS you would understand that developers do have to write code that is specific to the different OS versions they want to support.
I am an iOS developer, and mostly you don't. For the screen size. you code for points and it works for both old style screens and retina. You have to include 2 sets of bitmaps for graphics, but that's graphics work, not coding. And for the new longer screen, mostly apps are tableviews, and they'll just work without the programmer doing anything. In some cases you might need an alternate storyboard, if you chose a different layout when you have the longer screen.
This is forward and backward compatibility work, not fragmentation issues.
This differs from the case of the iPhone/iPad distinction, which IS fragmentation, and DOES require coding work.
Again, the distinction is that fragmentation is PARALLEL development of different branches of a product. Development of a single product through successive version is not fragmentation. Never has been.
Think of it as SCM - a single branch with successive versions is not fragmented. Multiple parallel branches are fragmentation.
I guess it all depends on what you mean by "fragmentation"....
But probably some people think "Two models is not fragmentation, because that is easy to handle. Its not fragmentation until it becomes a real burden".
No, my definition is not quantiative, it's objective. And it's what is meant by fragmentation in the industry. Fragmentation is parallel branches, it isn't successive versions.
The iPhone 1 and iPhone 3G are no longer supported by older versions of the OS. And there are also people who have used jailbreak and ultraSn0w or something like that to unlock their device to use on other carriers who will always be behind the general population until the latest OS version is exploited.. There are also people that just don't choose to upgrade their OS for a myriad of reasons. So yes, there is fragmentation on iOS and as a developer you have to choose which devices you want to support via the API that you use. And I know dozens of people who are still using a 3G or an iPod Touch 1st Gen. There are millions of those old devices out there. The question is, how many are still in use and which ones do you feel required to support as a developer?
None of that is fragmentation. Fragmentation is multiple parallel developments. It's not new devices having new or improved features not present on devices that are no longer sold. Fragmentation is when there are PARALLEL incompatible models, not SERIAL changes in a single product line. What you are describing is forward and backward compatibility, not fragmentation.
I can tell you now that Amazon just released a new version of their Amazon Instant Video app to fix bugs in iOS 4.0 and I see plenty of people writing negative reviews because an app doesn't support iOS 3 or 4 properly.
So it lacks backward compatibility. It's not fragmented. These are different issues.
Parallel products does not mean "on sale at the same time", it means "in use at the same time".
Just because they stop selling the old Iphone model it does not mean all the people who bought those will stop downloading apps.
No that's not it. Think of it like SCM. Successive versions isn't fragmentation. Multiple live branches is fragmentation.
Models following one after another IN SERIES do not cause difficult problems. It's perfectly ordinary backward and forward compatibility work. For each feature, it either stays the same or improves in each model. It's easy enough to factor in a change in behaviour at a certain model number. e.g. All models before X do this ... else do that...
The problem is products IN PARALLEL. From different manufacturers or different lines. iPhone vs iPad is fragmentation. iPhone 5 vs iPhone 4s isn't.
There will be apps that are for the original screen size, the new screen size and the ipad. That seems somewhat fragmented to me.
Apps for the original screen size work on the new devices. You're hypothesising that there will be apps that work on the new screen size that don't work on the old, but it's unlikely - there's no benefit to the app developer to do that, and it's easy enough to support both.
There are no iPhone apps that don't run on the iPad... Support for iPhone apps is built in to the iPad.
For sure there are some apps that are iPad only, but that's always been true. They are very different devices - it's not sensible to flag "fragmentation" up as an issue there.
Fragmentation isn't an issue for Apple mobile devices, however much some people wish it was.
The bigger point he's missing is that he doesn't even understand what fragmentation means. Fragmentation is multiple parallel products that have incompatibilities. It's NOT current devices currently being on sale being different from older models in the same series let along devices that are no longer on sale. You can argue that there's iOS device fragmentation as far as iPhone vs iPod Touch vs iPad. But the iPhone 3GS and the iPad 1 aren't even on sale any more.
Android is horribly fragmented because there is a huge number of current products with many hardware incompatibilities AND many don't even ship with a recent version of the OS. However much Android fanboys wish iOS devices had the same problem, they just don't.
1) That isn't something you "run". OP was talking about one or more apps.
2) Your complaint is one of someone looking at a spec sheet, not looking at a device. This is a mobile phone with pixels smaller than the eye can differentiate. No one is looking at an actual movie playing on that and complaining it's not 720p.
You'll give a shit, when you go spend $50 for your replacement proprietary connector. While everyone else is only spending $6.
Why say something that is so easily falsified? Even from Apple the cable is $19.
Third party, it's less than $1.
http://www.amazon.com/s/ref=nb_sb_noss_1?url=search-alias%3Daps&field-keywords=iphone+cable
You think post-modernism only came along after there wasn't any modernism any more?
Laptops are the better choice for people who need to do actual typing.
FTFY.
There's plenty of work that can be done on a tablet. But if it involves a lot of typing or editing of text, then you're better off with a laptop.
Actually most 'average' people I know end up asking "why can't I run something like that?"
Like what?
About the screen, they mentioned that older software will be letterboxed, but what about new software for older devices?
Being compatible with 2 screen sizes isn't difficult, and no doubt will be a requirement for getting the app past the app store reviewers.
... to every organization with staff: tablets are for consumption, not production.
No, that's not where the cut-off is.
Tablets are not good at text entry and editing. They're great for lots of other things, both consumption and production. Better than a laptop for a lot of them. For example sketching, filling out forms that are mostly checkboxes or multiple choice, grabbing a photograph to go with data, creating music.
I agree. If the list came from the developers they would have matched 100% of the list in their database.
Good grief. Slashdot really ought to do an IQ check before they allow people on here. One second of thought for an averagely intelligent person would give them at least one reason what that's not true.
Your explanation is easily falsified by the fact that the list contains user info from around the world, not just Americans. So that isn't the explanation for the relatively small number of records.
It was never the simplest explanation.
The /. crowd would rather believe the FBI is lying.
And that Apple is evil, don't forget that bit of confirmation bias.
The next question should be, "Why did Blue Toad have 11 miilion UDIDs from Apple and where did they get it from?"
Because Blue Toad like many other Apple App developers used to have their iOS app send their servers the UUID and some personal information. It became against the rules some time ago, but this list dates from when it was still a common practice.
The UUIDs and the info did not come from Apple.
Several people pointed this out in the original story comments, but looney-tunes conspiracy nuts chose not to believe it.
All we know now is where the data likely originated -- which is precisely where everyone assumed it originated anyway (a single developer list).
How quickly people forget. The original slashdot story a comments were only a few days ago, and there were many people who were assuming that Apple willingly gave (or sold) it to the FBI.
For sure they were idiots that like to seize any opportunity to call Apple evil. But no, everybody didn't assume this came from a 3rd party developer. Only the more intelligent people realised that.
Depends what nationality he is. His is spelt correctly for British English, yours is spelled correctly for American.