*sigh* Here we go again with the Android bashing. Quelle surprise, AppleInsider.
This article isn't a study; it's speculation. The author isn't investigating why something has happened; she's guessing that something might happen. I have to wonder if the author knows the first thing about software development. It is not a problem to support multiple devices on Android. The platform was designed to support that. [URL=https://developer.android.com/guide/topics/resources/index.html]You might want to have a look at the documentation on the subject[/URL]
(Btw, I have to keep making this point every few months. It's almost as if no one on here actually listens or does any fact-checking before they type out an angry anti-Android screed. It's really tedious).
There certainly are features in newer OS releases that can't be backported, like RenderScript or triple-buffering in the graphics layer. And there are security improvements in newer versions (which I was just discussing last night on here). But there's no evidence that any of this is impeding app development. Certainly none was presented in this article.
I don't blame you. How<span style="line-height:1.231;">ever, it's as good a "logic" as the ridiculous claims of shills around here.</span>
If there was any logic to your comments you'd make a fair and balanced comment every now and then but you don't, instead you claim that Apple's pixel doubling isn't good for developers and customers but some poor choice that only muddy's the graphics despite Apple specifically designing the Retina UIs to be idealized for their respective display.
Now there are certainly those on the opposite end as you that can't see anything negative about Apple but at least their presence here is logical as it's a pro-Apple site.
If there was any logic to your comments you'd make a fair and balanced comment every now and then but you don't,
Or rather, you don't see them.
Just recently, I've defended iOS from claims of malware, praised the iPad for its CSS3 abilities, and brought up iOS devices being used by the military (in non secure areas), among other things.
I don't create the topics. I react to mistaken ideas and internet myths.
And I sure don't engage in the vicious personal attacks that some do around here when they lack an intelligent response.
That's an uncalled for remark. You reveal your true colors.
I'm sorry to see it. You're usually better than that.
You're the one that made the comment. Would you rather I use "It's their fault for not paying close attention to their luggage?" EIther way your rationalization that's their fault for putting you in this position is weak.
Just recently, I've defended iOS from claims of malware, defended Apple programmers for bugs, praised the iPad for its CSS3 abilities, and brought up iOS devices being used by the military (in non secure areas), among other things.
Oh, I've read compliments from you but they comes across as "concern troll" posts with a lot of backhanded comments.
Oh, I've read compliments from you but they comes across as "concern troll" posts with a lot of backhanded comments.
I think that's just a result of the general atmosphere of distrust that dominates this place.
Also, where are you from? Having moved to NJ, I've found that Southern ways of being polite by being understated, are often mistaken by Northerners as some form of deceit ... sad but true
I think that's just a result of the general atmosphere of distrust that dominates this place.
Also, where are you from? Having moved to NJ, I've found that Southern ways of being polite by being understated, are often mistaken by Northerners as some form of deceit ... sad but true <img alt="1smile.gif" id="user_yui_3_7_3_1_1362542593554_1166" src="http://forums-files.appleinsider.com/images/smilies/1smile.gif" style="line-height:1.231;" name="user_yui_3_7_3_1_1362542593554_1166">
There is nothing polite about making mendacious comments but if you want to go on thinking that adding a smily emoticon to your post means you're a sweet Georgia peach you go right ahead and continue to lie to yourself. At least your as honest with us as you with yourself which is about the only fair and balanced thing I've seen from you.
I honestly believe that Google purchased Moto for 2 reasons: 1, to stave off Samsung's meteoric rise in the Android world to some degree, as has been rumored. And 2, to produce a line of phones (like Nexus) that will partially solve the fragmentation problem. The Nexus phones are the first to receive Android updates and the line isn't as fragmented as phones produced by other manufacturers.
Having said that, it's going to be very interesting to see how Android plays out over the next few years. There's no doubt that fragmentation is frustrating for developers. My money is on Google reining in Android, and Samsung/others either complying or forking the OS like Amazon has already done. Talk about fragmentation if that happens!
Generally true but the Samsung nexus Canadian telco one doesn't. The telco or Samsung prevents it. Go figure.
Yes Really to quote rovio themselves in a gigaohm article:
<strong style="line-height:24px;color:rgb(34,34,34);font-family:'Helvetica Neue', Helvetica, Helvetica, Arial, sans-serif;font-size:16px;">Android fragmentation is a serious issue for developers.</strong>
<span style="color:rgb(34,34,34);font-family:'Helvetica Neue', Helvetica, Helvetica, Arial, sans-serif;font-size:16px;line-height:24px;"> In its tweets, Rovio Mobile said it began working on the Android version of Angry Birds in the spring. But the company said it took a long time to test for all the different Android devices to ensure they worked well. “Main challenge with Android is the amount of different devices. They are all different. Takes forever to test,” the company said tweeted. In the end, there are still devices like the HTC Hero and Sony Ericsson X10 that appear to have problems running the game. By comparison, porting over Angry Birds to webOS earlier this year only took a “few hours.” This could be a growing problem for Android developers as the number and variety of devices proliferates.</span>
<span style="color:rgb(34,34,34);font-family:'Helvetica Neue', Helvetica, Helvetica, Arial, sans-serif;font-size:16px;line-height:24px;">Even rovio tells us that it is a huge pain in the arse to port to android and that there are still android phones that wont or have a difficult time running angry birds. Android is the problem with its horrible fragmentation. They also said in the same article that paid game models like on iOS dont work on android because of the mindset of the users. People want freemium games on android. A game they can download for free and just click the ads out of the way.</span>
Hang on you are using evidence, the ultimate troll KD will simply ignore it or spin it every which way he can.
Specially coded apps to support retina display iPads? Sounds like fragmentation to me.
By "specially coded apps" you mean creating artwork that fits exactly within the iPad's screen parameters? That's really not as oddball as you think.
But don't take my word for it.... look at all the apps made for the "difficult to design for" iPad.
And compare that to the apps made for the "just throw whatever you can onto the screen" Android tablets.
Look... I know what you're saying. But Apple creating a spec and developers following that spec down to the pixel isn't as bad as you're trying to make it.
If you want your apps to look good on a Retina screen... guess what... you're gonna have to build them that way!
*sigh* Here we go again with the Android bashing. Quelle surprise, AppleInsider.
This article isn't a study; it's speculation. The author isn't investigating why something has happened; she's guessing that something might happen. I have to wonder if the author knows the first thing about software development. It is not a problem to support multiple devices on Android. The platform was designed to support that. You might want to have a look at the documentation on the subject
Some developers are choosing to target only 4.x because they have more customers on it. Just yesterday, 500px announced that the next version of their app will drop Gingerbread support in the next version because so few of their users are on it. Other developers are having this discussion and generally coming to the same conclusion. Ultimately, backwards compatibility is something each developer has to decide for themselves, but the market is clearly moving in the 4.x direction.
...
(Btw, I have to keep making this point every few months. It's almost as if no one on here actually listens or does any fact-checking before they type out an angry anti-Android screed. It's really tedious).
Ignoring for the moment that the plural of anecdotal isn't data, what it shows more is that a large portion of Android devices are not being used as smartphones which is why some app developers are seeing a majority of 4.x sales despite a majority of the market running an OS older than ICS.
Folks are still making new Gingerbread phones in 2013 although typically for the developing market.
I assume because the hardware requirements are lighter.
Looking on AT&T I see them still selling 2.3 phones: Samsung Captivate, Exhilarate, Pantech Burst, Pocket. Heck the Sharp FX Plus is a 2.2 device.
I haven't bothered to look on Verizon but it makes sense that the free phones are the older models and gingerbread the majority.
The documentation on the subject still show more than half of android devices are pre-ICS. That should hopefully change by the time that Key Lime Pie gets released but 2.x will still be a large part of the pie when that happens.
Unless she's a medical doctor, one does not use titles, much less degrees with a person's name. I have informed the Associated Press style people and this will be noted in your permanent file.
Comments
You sound like the kind of guy that would also say, "If she didn't want it she shouldn't have been wearing that."
Quote:
Originally Posted by SolipsismX
You sound like the kind of guy that would also say, "If she didn't want it she shouldn't have been wearing that."
That's an uncalled for remark.
I'm sorry to see it. You're usually better than that.
This article isn't a study; it's speculation. The author isn't investigating why something has happened; she's guessing that something might happen. I have to wonder if the author knows the first thing about software development. It is not a problem to support multiple devices on Android. The platform was designed to support that. [URL=https://developer.android.com/guide/topics/resources/index.html]You might want to have a look at the documentation on the subject[/URL]
Some developers are choosing to target only 4.x because they have more customers on it. Just yesterday, 500px announced that the next version of their app will [URL=http://mobilesyrup.com/2013/03/04/500px-for-android-updated-with-push-notifications-and-comment-replies-plans-to-drop-support-for-gingerbread-devices/]drop Gingerbread support in the next version[/URL] because so few of their users are on it. [URL=
If you do choose to support older devices, the community has lots of tools to help you. And, no, you're not limited to the "the lowest common denominator." Google extracts the new APIs and packages them in [URL=https://developer.android.com/tools/extras/support-library.html]a support library[/URL] which supports older versions back to 1.6. There are a few missing pieces in the support library, but the Android dev community has stepped up to back port them. See [URL=http://actionbarsherlock.com/]ActionBarSherlock[/URL], [URL=https://github.com/saik0/UnifiedPreference]Unified Preferences[/URL], [URL=https://github.com/JakeWharton/NotificationCompat2]NotificationCompat2[/URL], and [URL=https://github.com/JakeWharton/NineOldAndroids]NineOldAndroids[/URL], for example. Further, Google provides documentation on writing code that works across versions (http://developer.android.com/training/basics/supporting-devices/platforms.html and http://developer.android.com/training/backward-compatible-ui/index.html).
(Btw, I have to keep making this point every few months. It's almost as if no one on here actually listens or does any fact-checking before they type out an angry anti-Android screed. It's really tedious).
There certainly are features in newer OS releases that can't be backported, like RenderScript or triple-buffering in the graphics layer. And there are security improvements in newer versions (which I was just discussing last night on here). But there's no evidence that any of this is impeding app development. Certainly none was presented in this article.
If there was any logic to your comments you'd make a fair and balanced comment every now and then but you don't, instead you claim that Apple's pixel doubling isn't good for developers and customers but some poor choice that only muddy's the graphics despite Apple specifically designing the Retina UIs to be idealized for their respective display.
Now there are certainly those on the opposite end as you that can't see anything negative about Apple but at least their presence here is logical as it's a pro-Apple site.
Quote:
Originally Posted by SolipsismX
If there was any logic to your comments you'd make a fair and balanced comment every now and then but you don't,
Or rather, you don't see them.
Just recently, I've defended iOS from claims of malware, praised the iPad for its CSS3 abilities, and brought up iOS devices being used by the military (in non secure areas), among other things.
I don't create the topics. I react to mistaken ideas and internet myths.
And I sure don't engage in the vicious personal attacks that some do around here when they lack an intelligent response.
You're the one that made the comment. Would you rather I use "It's their fault for not paying close attention to their luggage?" EIther way your rationalization that's their fault for putting you in this position is weak.
Oh, I've read compliments from you but they comes across as "concern troll" posts with a lot of backhanded comments.
Quote:
Originally Posted by SolipsismX
Oh, I've read compliments from you but they comes across as "concern troll" posts with a lot of backhanded comments.
I think that's just a result of the general atmosphere of distrust that dominates this place.
Also, where are you from? Having moved to NJ, I've found that Southern ways of being polite by being understated, are often mistaken by Northerners as some form of deceit ... sad but true
Do it. I double-dare you.
There is nothing polite about making mendacious comments but if you want to go on thinking that adding a smily emoticon to your post means you're a sweet Georgia peach you go right ahead and continue to lie to yourself. At least your as honest with us as you with yourself which is about the only fair and balanced thing I've seen from you.
LOL... that was just until developers got on-board with making beautiful iPad tablet apps that ran natively.
How did they do in that department?
Specially coded apps to support retina display iPads? Sounds like fragmentation to me.
He sickens me
Please can him immediately
By "specially coded apps" you mean creating artwork that fits exactly within the iPad's screen parameters? That's really not as oddball as you think.
But don't take my word for it.... look at all the apps made for the "difficult to design for" iPad.
And compare that to the apps made for the "just throw whatever you can onto the screen" Android tablets.
Look... I know what you're saying. But Apple creating a spec and developers following that spec down to the pixel isn't as bad as you're trying to make it.
If you want your apps to look good on a Retina screen... guess what... you're gonna have to build them that way!
That's not fragmentation.
.
Quote:
Originally Posted by KDarling
An article about app development, written by a major in Political Science. That makes sense.
In reality, there's only a handful of major display sizes and device types to target.
Same as with iOS, most Android apps work with even a fairly old OS version, since the APIs most apps need were already in there years ago.
Click bait.
That's the problem. You need to target a fairly old OS version to remain compatible with a larger majority of handsets. 54% is still 2.3 or older.
http://developer.android.com/about/dashboards/index.html
Quote:
Originally Posted by derekmorr
*sigh* Here we go again with the Android bashing. Quelle surprise, AppleInsider.
This article isn't a study; it's speculation. The author isn't investigating why something has happened; she's guessing that something might happen. I have to wonder if the author knows the first thing about software development. It is not a problem to support multiple devices on Android. The platform was designed to support that. You might want to have a look at the documentation on the subject
Some developers are choosing to target only 4.x because they have more customers on it. Just yesterday, 500px announced that the next version of their app will drop Gingerbread support in the next version because so few of their users are on it. Other developers are having this discussion and generally coming to the same conclusion. Ultimately, backwards compatibility is something each developer has to decide for themselves, but the market is clearly moving in the 4.x direction.
...
(Btw, I have to keep making this point every few months. It's almost as if no one on here actually listens or does any fact-checking before they type out an angry anti-Android screed. It's really tedious).
Ignoring for the moment that the plural of anecdotal isn't data, what it shows more is that a large portion of Android devices are not being used as smartphones which is why some app developers are seeing a majority of 4.x sales despite a majority of the market running an OS older than ICS.
Folks are still making new Gingerbread phones in 2013 although typically for the developing market.
http://www.hardwarezone.com.ph/tech-news-huawei-ascend-y210d-budget-dual-sim-smartphone-now-sells-ph
I assume because the hardware requirements are lighter.
Looking on AT&T I see them still selling 2.3 phones: Samsung Captivate, Exhilarate, Pantech Burst, Pocket. Heck the Sharp FX Plus is a 2.2 device.
I haven't bothered to look on Verizon but it makes sense that the free phones are the older models and gingerbread the majority.
The documentation on the subject still show more than half of android devices are pre-ICS. That should hopefully change by the time that Key Lime Pie gets released but 2.x will still be a large part of the pie when that happens.
"Dr. Mary Ellen Gordon, PhD..."
Unless she's a medical doctor, one does not use titles, much less degrees with a person's name. I have informed the Associated Press style people and this will be noted in your permanent file.