How is the G1 going to run all these apps? =\

[Libralah]

Don't get me wrong, I love the idea of all these apps that run in the background utilizing the GPS and the always connected feature of the phone, but wouldn't running a multitude of these apps slow down the phone tremendously? I mean, what if I have my wifi army app running with my weather app, with my tune wiki app, and all my other apps etc. etc.

I don't know, I guess we'll have to see until the 22nd.

[drewmatic305]

yeah i was curious about that myself ,like u said only one way to find out

[GreenLeaf]

it will not slow down your phone. It has separate dedicated processors for phone functions & applications. I read somewhere that someone tested running 35 apps at one time & it didn't slow down a bit. But your battery will take a battering!

[Libralah]

Yeah, I'm sure the battery would get spanked but we could always upgrade to a much better battery ^_^. However, I wonder how Tmobile's 3G network is gonna be able to hand all these G1 phones raping their connections. I have a feeling we're all going to get capped with these apps =\

[ggreeenwood33]

Battery shouldn't be a problem. if you use your gps. just have it plugged into your car... just keep it plugged in... i don't think it will be worse then any other phone!when you are not using it. lock it and turn off the screen. don't let it keep lit up. simple!

[RegGuheert]

This OS is *very* clever! I've started learning development for Android and I am amazed at how things function. Specifically, processes in Android do NOT control their own destiny as they do in other OSes. Specifically, any process that is not in the foreground or active in the background can be unloaded from memory and then reloaded later if/when needed. This is accomplished by APIs that all programs must access that allow for the state of a program to be saved and recovered at the instruction of the OS.

The following three videos explain the Android architecture in some detail:

Androidology - Part 1 of 3 - Architecture Overview
[ame]http://www.youtube.com/watch?v=Mm6Ju0xhUW8[/ame]

Androidology - Part 2 of 3 - Application Lifecycle
[ame]http://www.youtube.com/watch?v=fL6gSd4ugSI[/ame]

Androidology - Part 3 of 3 - APIs
[ame]http://www.youtube.com/watch?v=MPukbH6D-lY[/ame]

Part 2 is the video that addresses your question most directly.

Pretty cool!

Reg

[defaultuser]

Between the 2 core processor running @ 500+ MHz, being able to scale down to a lower speed to save battery, and the OS running apps in the background and able to juggle multiple apps at the same time it will be great.

I wont edit video on it, but the small footprint of the apps running on it will be fine.

[RussianSolja]

you can multi-task your a** off with out any lag! or freezeing! its great!

[snoslicer8]

I hate to continue comparing the G1 to other phones, but it's the best way to achieve a visual of how things are going to work.

Android is an OS with a core written in Linux, and all apps written for the core are compiled in Java. Java has the ability to have very robust applications with extremely small footprints.

An example (again) is the Sidekick family running the Danger OS. The Danger OS is written in their own proprietary extension of Java, with NO apps ever being 'Quit' (it is expressly forbidden in their SDK guidelines to EVER tell an application to quit). They simply suspend themselves into a lower level of function while not in focus, but continue to do their jobs.

I suspect we will see very similar (yet more complete) functionality from Android and the G1.

[hoobashoot]

Also all the apps developed for android are not huge apps they are small in information although they dont seem like it.