71–80 of 135 posts
IMO iOS 7 is a textbook case of fixing something that's not broken.
The unlikely day that Apple takes the approach that "you don't fix what ain't broke" would be a sad sad day indeed.
TLDR: iOS7 allows for background fetching when the app is closed. Allowing for smaller wait times when users open up an app. Is there any way for users to manage this behavior? If not it seems ripe for abuse or just plain laziness.
From other comments it sounds like iOS might figure out I like to listen to podcasts en route to work and learn to pre-fetch. But I don't want to rely on it noticing this or wait for it to learn.
I have a mix of Android and iOS and it's for this use case that Android handles all my podcasts.
It's funny how all these things that have been in Android forever and were criticized for their battery draining powers are suddenly the latest and greatest reason why Apple phones are the best. It's just the way it goes, remember 7 inch tablets? Worst thing ever and everyone lists reasons why. Until Apple made one. Marketshare means everything! Until Android stole that, now market share is a false signal. King of pr…
You forget a few things. On Android can't the app just run forever and decide on its own how often to poll the servers? This is a different thing. The OS decides when to schedule things if the app supports it. Also battery life has improved a great deal since the first Android or iPhone device came out. What may have been true years ago isn't necessarily an issue anymore.
It's funny how all these things that have been in Android forever and were criticized for their battery draining powers are suddenly the latest and greatest reason why Apple phones are the best. It's just the way it goes, remember 7 inch tablets? Worst thing ever and everyone lists reasons why. Until Apple made one. Marketshare means everything! Until Android stole that, now market share is a false signal. King of pr…
What's really funny is how right you are, and all the comments made in response to you are proving that the reality distortion field is still in effect post-Jobs. When a competitor does it and Apple says they won't, it's the worst thing in the world. Once the competitor proves its worth and Apple does it, it's now the best thing ever (see xutopia). If you're right but with one hint of an arguable point, there's alway…
The mechanisms are wildly different:
On Android the app developer chooses if he is a good citizen or not and can if he puts the effort to use the SyncAdapter (Bobz mentions this in the thread). The SyncAdapter afaik provide the same benefits as the iOS method.
On iOS the app developer can only provide the hooks for the OS to call and the OS decides when to call them. This is similar to how SyncAdapter works from what I can tell.
So Android provides developers with the capability to shoot the proverbial foot. We can argue that it's a good or a bad thing based on that but calling people fanboys isn't conducive to a good discussion.
Earlier quoted context omitted.
What's really funny is how right you are, and all the comments made in response to you are proving that the reality distortion field is still in effect post-Jobs. When a competitor does it and Apple says they won't, it's the worst thing in the world. Once the competitor proves its worth and Apple does it, it's now the best thing ever (see xutopia). If you're right but with one hint of an arguable point, there's alway…
As I understand it, it's not the same as Android though. The app requests to wake up at intervals, and if the OS decides it's OK (based upon battery, network activity and how often you use the app) the app is granted that access.
Earlier quoted context omitted.
You forget a few things. On Android can't the app just run forever and decide on its own how often to poll the servers? This is a different thing. The OS decides when to schedule things if the app supports it. Also battery life has improved a great deal since the first Android or iPhone device came out. What may have been true years ago isn't necessarily an issue anymore.
You mean like using Android's SyncAdapter and setting inInexactRepeating()? Android has supported this basic type of background scheduling since the start of time. The main difference is that Android you can do more - which can be abused. And their solution for abuse is a battery monitor that allows you to see which app is using the most battery. In a way you can say Android is more superior/powerful or you can say t…
Earlier quoted context omitted.
What do you call the iPad mini? ciel(7.9) inch tablet?
A 7.9 inch tablet, which is much larger than a 7 inch tablet.
Similar to how the iPhone 5 has a 4" screen, but it's much smaller than a normal 4" screen in width. That's the product category. "7 inch tablet" as a market segment doesn't mean exactly 7 inches. Just because Apple said they'd never make a 7" tablet doesn't mean their product doesn't compete in the 7 inch tablet market.
Do you realize how ridiculous you sound?
The background behavior in iOS 7 is a great improvement but can't really be described by those of us who are still under non disclosure agreement. Beyond that there are lots of goodies for developers that have been added to iOS APIs.
Earlier quoted context omitted.
What's really funny is how right you are, and all the comments made in response to you are proving that the reality distortion field is still in effect post-Jobs. When a competitor does it and Apple says they won't, it's the worst thing in the world. Once the competitor proves its worth and Apple does it, it's now the best thing ever (see xutopia). If you're right but with one hint of an arguable point, there's alway…
I'm going to call you out on this one. You're dismissing perfectly viable criticism as "fanboyism". The mechanisms are wildly different: On Android the app developer chooses if he is a good citizen or not and can if he puts the effort to use the SyncAdapter (Bobz mentions this in the thread). The SyncAdapter afaik provide the same benefits as the iOS method. On iOS the app developer can only provide the hooks for the…
Apple has a great method of taking existing ideas, refining them until they shine, and putting them into a beautiful product. I have nothing against that, it's helped the industry immensely. I hope Apple keeps making improvements year over year and pushing the market along. What I take offense with is Apple's audience pretending these features never existed before, or that they were bad ideas then but great ideas now. That's exactly what I'm seeing you and others in this thread doing.