Thank you very much for your feedback!
Yes, I understand, that Android isn't really so divided. I try to
categorize it my self. I hope it helps to perception and
understanding. In map of Linux kernel http://www.makelinux.co.il/kernel_map
it works better, but is still sometimes questionable.
Any way, there will be a lot crossing connections even without
columns. I've aggregated some connections to reduce number of lines.
I've renamed Human Interface to Human Oriented. May be it is possible
to find more proper name. In this column I place not just GUI objects,
but anything what's primary goal is to serve human (users and
Thank you for your ways to organize the chart. It looks interesting.
I'll think latter about it.
On Jun 21, 2:41 am, Dianne Hackborn <hack...@android.com> wrote:
> Hi, that is an impressive amount of work.
> One thing I would suggest -- Android isn't really so divided into the areas
> you use (human interface, system, multimedia, etc) and I think trying to
> shove the pieces of it into those categories make this diagram a lot more
> confusing than it needs to be, with a lot of lines crossing over other parts
> of the diagram.
> For example why is AccountManagerService under "human interface"? It
> doesn't do any UI, it just keeps track of the accounts the user has added to
> their device. Likewise LocationManagerService.
> I can think of a couple different ways to organize the chart:
> - As layers, with lower-level parts building on top of higher-level ones.
> For example, at the bottom is the hardware, next the Linux kernel, then
> core user space pieces like init and the services it starts such as zygote,
> installd, etc., then the system_process and things that run in it
> (PackageManagerService, WindowManagerService, ActivityManagerService,
> ClipboardManagerService, LocationManagerService, and on and on), and then
> the client-side frameworks built on that (the view hierarchy, app package,
> - Build a spine of the central part of Android: linux, zygote,
> PackageManagerService, WindowManagerService, ActivityManagerService and
> related items. This is somewhat like your system category, but really the
> core parts of the system (for example Launcher2 and Settings have nothing to
> do with this). Then you can have separate topical sections for sub-systems
> that build out from this: the audo system, content providers, telephony,
> On Mon, Jun 13, 2011 at 8:05 AM, Constantine <conan...@gmail.com> wrote:
> > Hi Android developers,
> > I am designing detailed diagram of Android internals. You can find it
> > here:http://www.makelinux.net/android/internals/
> > What do you think about it?
> > Have you any ideas how to improve it?
> > Thank you in advance.
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Android Developers" group.
> > To post to this group, send email to firstname.lastname@example.org
> > To unsubscribe from this group, send email to
> > email@example.com
> > For more options, visit this group at
> Dianne Hackborn
> Android framework engineer
> Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails. All such
> questions should be posted on public forums, where I and others can see and
> answer them.
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to
For more options, visit this group at