Change Player Size
Watch this video in a new window

Androidology - Part 1 of 3 - Architecture Overview

Part 1 of 3 in an overview series on the Android platform. In this segment, Mike gives an overview of the system architecture.  
 
Customize

More From: Google

Google Calendar Connectors Demo6:32
25,199 views
Android Demo6:24
163,130 views
Google Earth API1:01
1,658,987 views
Why Google Apps for Education?10:38
88,742 views
A first hand look at building an Android application7:57
6,555 views
Google Creative Sandbox '08 SF1:33
16,041 views
Full Web Experience: Web Browser on Android-Powered Phones2:06
125,108 views
Create cool stuff with Google SketchUp1:29
155,582 views
How to create a "My Map" in Google Maps3:28
1,456,161 views
Google D.C. Talks:  "National Security and Web 2.0"1:09:12
5,992 views
Google Mobile Products on Android3:23
652,315 views
Google Maps API and Tripadvisor3:35
245,774 views
The Tour de France in Google Maps Street View1:17
412,991 views
Google Maps for mobile transit directions1:53
248,327 views
Google Calendar Connectors Implementation Guide48:19
18,886 views
Watershed School sixth graders talk about using Google Apps1:35
11,366 views
A day in the life of webmaster support6:27
24,951 views
Google 101 para pequeñas empresas1:23:50
23,873 views
Kai-Fu Lee - Google Keynote, WWW 2008 Beijing52:43
9,138 views
Androidology - Part 3 of 3 - APIs7:04
17,831 views

QuickList(0)

Featured Videos

Upgrade to Flash Player 10 for improved playback performance. Upgrade Now or get more info.
184 ratings
Sign in to rate
196,968 views
Want to add to Favorites? Sign In or Sign Up now!
Want to add to Playlists? Sign In or Sign Up now!
Want to flag a video? Sign In or Sign Up now!

Statistics & Data

Loading...

Video Responses (0)

This video has no Responses. Be the first to Post a Video Response.
Sign in to post a Comment

Text Comments (77)   Options

Loading...
OneEyedParrot (8 months ago) Show Hide
 0
Marked as spam
This video was very useful... yes... useful... thank you Google...
Comment(s) marked as spam Show
babylon2233 (1 year ago) Show Hide
 0
Marked as spam
I think you mean writing a native linux application. So, you're wrong because Android is Linux + Dalvik + ... ~ Dalvik itself is a linux software and not an android apps.Every sing Android apps will always written in java unless Google modify the architecture of Android. I know how Android works. And I wonder if you even know what Android is all about.
therrydicule (1 year ago) Show Hide
 0
Marked as spam
I take android as a full operating system that include a kernel and some abi and api. Not just a kernel, with is linux anyways...

Since we could write native application for linux, we could for android with some modification...
I said we could write some native application for the OS, but I did not specified the level of abstraction and neither if we should add some API and libraries... For me, that technicalities. Because if I talk about this, a lot of 2guy" will not understand what I mean ;)
babylon2233 (1 year ago) Show Hide
 0
Marked as spam
Basically, when you want to write a linux software what you need is libc. But you can't use that java classes to use with your native application. Let say you want to write an openGL apps, you will need the related library. That library is not available with android. What android have is just a libc. That's clear. Because android is jvm on top of linux which mean if you write native apps that somehow run on android it is not an android apps but instead a linux apps.
babylon2233 (1 year ago) Show Hide
 0
Marked as spam
Then you might want to tell me the technicalities that you mean. If you don't mind just explain about those API and abstraction level. I hope you get it right.
therrydicule (1 year ago) Show Hide
 0
Marked as spam
Ok: For short, I been specific to android.

Over the hardware and "bios" you have a monolithic kernel call linux. Alone, the kernel only some management, drive the hardware, work some file system.

To work, they add some libraries, then api and over all this you run application.

You could add extra-libraries&api&applicatio n in this order.

It's a kind of hacking ;) You need a cross-compiler,a debuger, to modified the G.U.I.
But little portabilities for this "new" specific application.
babylon2233 (1 year ago) Show Hide
 0
Marked as spam
So, the conclusion:

Android apps will always Java/JVM-based. That's clear because all android apps run on the Dalvik(which is a JVM). Unless you want to modify the system. For your info, libary isn't necessary as you can simply write a linux/BSD/blabla application by only using system calls. Library just making your work easier.
therrydicule (1 year ago) Show Hide
 0
Marked as spam
I know that, I just feel is hard for nothing to use system calls... Specially when portabilities need. But is possible, you are right.
What I just mean it is possible, with some modification. But it don't mean programmer have to: Java is great when goodly use.

Would you like to comment?

Join YouTube for a free account, or sign in if you are already a member.