iOS 6 for iPhone 4s and iPad to include free satnav powered by TomTom

mrochester

buscape wrote: »

Read the link I posted, you'll understand what I mean. Certain types of apps CAN run in the background indefinitely, most can't.

As I've said, iOS can multitask, but not fully.

I know how multitasking works in iOS. You're the one telling me my apps are suspended when in fact they are operating in the background!

buscape

mrochester wrote: »

I know how multitasking works in iOS. You're the one telling me my apps are suspended when in fact they are operating in the background!

I've edited the post above to make it clearer. Suspended and running aren't the same thing are they?

mrochester

Could be and is are two different things. The video is obviously not in response to apple, the video is inviting people to develop for android and showing some features.

The video shown to you to prove the first android wasn't a blackberry device which is where you were going.

Actually the point I'm making is that Android only became a touch enabled OS in response to Apple announcing the iPhone.

Limited demo yes, exactly. To show a few keys points to would-be developers and thats it.

How do you know? It could also be a limited demo because they had only very recently thrown it all together.

Yep 22 months to come to market with a finished product that looks nothing like the iphone.

How it looked is irrelevant. What's relevant is that it took them so much longer after the iPhone was announced and released to release a product themselves. If Android was so fully developed for touch long before the January 2007 event, why did it take them so long to release a product?

I find it highly amusing you keep asking for evidence to prove your conclusions wrong having provided no evidence at all in your favour.

I'm looking for evidence that Android was touch enabled prior to January 2007. A video released in November 2007 is obviously not evidence of this. In the absence of such evidence, we can only draw conclusions from what we do know.

I've edited the post above to make it clearer. Suspended and running aren't the same thing are they?

No one said they were...? All I said was I have apps running in the background all the time on my phone, which I do. As I type this I have a podcasting app playing a podcast in the background as I reply to a text. This multitasking sorcery is marvellous!

buscape

mrochester wrote: »

No one said they were...? All I said was I have apps running in the background all the time on my phone, which I do. As I type this I have a podcasting app playing a podcast in the background as I reply to a text. This multitasking sorcery is marvellous!

Are you going to read that link? Apps that play audio in the background are alllowed to run in the background indefinately. Most apps aren't allowed to run in the background, they get suspended.

From the link;

So all apps get five seconds of Background running, to clean things up, and some apps (such as Instacast) can request a ten-minute extension. There are, however, a small number of apps that genuinely need to run indefinitely in the background, and iOS allows this.

There are exactly five kinds of apps allowed to run indefinitely in the Background state in iOS 5:

Apps that play audio while in the Background state. A good example is Instacast while it’s playing a podcast.

Apps that track your location in the background. For example, you still want voice prompts from your turn-by-turn GPS navigation app, even if another app is Active.

Apps that listen for incoming voice-over-IP (VOIP) calls. If you use Skype on iOS, you can receive incoming Skype calls while the app is in the background.

Newsstand apps that are downloading new content.

Apps that receive continuous updates from an external accessory in the background.

All well-written apps in the above categories should become Suspended when they are no longer performing the task in hand. When Instacast finishes playing a podcast, it should be Suspended.

There are some built-in apps that also run continuously in the background on iOS—the most-used one is probably Mail.

mrochester

Are you going to read that link? Apps that play audio in the background are alllowed to run in the background indefinately. Most apps aren't allowed to run in the background, they get suspended.

I know that. Like I said, I know how multitasking works in iOS. I've never said to the contrary!

mrochester

Complete speculation.

Which is exactly what you're doing.

You suggest the google was ready to release a device apple then released the iphone and google then delayed until they'd copied the iphone. Rubbish.

That sounds like the most probable conclusion to me.

Well look for it then. Android is runs on linux, linux supports touch in the kernel.

That doesn't prove that Google was actually developing a touch based UI prior to the iPhone being announced. That just proves the capability was there.

That isn't multi-tasking.

Yes it is. Multiple tasks happening at the same time is called multitasking.

http://en.wikipedia.org/wiki/Computer_multitasking

In computing, multitasking is a method where multiple tasks, also known as processes, are performed during the same period of time

[Deleted User]

mrochester wrote: »

Actually the point I'm making is that Android only became a touch enabled OS in response to Apple announcing the iPhone.

Straw man.

What would be the logic in designing a mobile phone operating system that was far behind what had been widely available on the market for years previously?

How do you know? It could also be a limited demo because they had only very recently thrown it all together.

Prototype devices are extremely expensive. Even more so when you are intending to use a device with advanced technology that is still expensive when you are buying millions of units, let alone less than 50.

How it looked is irrelevant. What's relevant is that it took them so much longer after the iPhone was announced and released to release a product themselves. If Android was so fully developed for touch long before the January 2007 event, why did it take them so long to release a product?

Google do not manufacture hardware. Supply chains needed to established with hardware manufacturers around the same time you have established any interest in buying the product.

Testing and certification for hundreds - if not thousands - of mobile phone networks throughout the world adds also adds significant lead to production.

No one said they were...? All I said was I have apps running in the background all the time on my phone, which I do. As I type this I have a podcasting app playing a podcast in the background as I reply to a text. This multitasking sorcery is marvellous!

Apple's iOS developer documentation makes clear the exact limitations of third-party application multitasking. It is not done in the same manner as Android.

buscape

cubegame wrote:

One would imagine that on an S3, one can start an app get it doing something, then switch to another app, do something else and then switch back to the first app which (and this is the clever multi-tasking bit) will have carried on doing what it was doing before......

mrochester wrote: »

Yeah you can do the same on iOS.

owen1978 wrote:

IOS multitasking involves IOS pausing an app, If you are loading a web page and you decide to open up another app. IOS will suspend the browser so the page will not load.

mrochester wrote: »

iOS will continue to load the page in the background.

Does this not give the impression that you think (or thought) that iOS multitasks fully?

mrochester wrote:

I know that. Like I said, I know how multitasking works in iOS. I've never said to the contrary!

mrochester

What would be the logic in designing a mobile phone operating system that was far behind what had been widely available on the market for years previously?

They weren't. They were designing a mobile OS that competed with the most popular smartphone OS of the time, Symbian. As far as Google were concerned prior to January 2007, this was what they were competing with.

Prototype devices are extremely expensive. Even more so when you are intending to use a device with advanced technology that is still expensive when you are buying millions of units, let alone less than 50.

What's the cost of a prototype device got to do with how quickly they put together a touch based UI?

Apple's iOS developer documentation makes clear the exact limitations of third-party application multitasking. It is not done in the same manner as Android.

I think you need to tell that to the people who think iOS doesn't multitask. You're not telling me anything I don't already know here.

mrochester

No I'm pointing out you don't know and the opposite of what you are saying is equally valid.

Lack of evidence to prove you wrong doesn't make you right.

Of course the opposite of what I say is equally valid, I just think it sounds a lot less likely than my own conclusion.

Yep your speaking rubbish is the most probable conclusion. At least you admit it.

What you say doesn't prove they weren't. Its just some apple fanboy conspiracy. Wide speculation based on nothing.

Aren't insults the typical kneejerk response from someone who doesn't like being called into question over their assertions? Personally, I never stoop to that level.

Multiple things paused in memory isn't multitasking.

You're only showing that you lack an understanding of how multitasking works in iOS.