Androidology - Part 1 of 3 - Architecture Overview

This video was very useful... yes... useful... thank you Google...

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.

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 ;)

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.

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.

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.

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.

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.