SlideSpeech: Introduction to Android

1 / 22

1

autoplay

At a recent Google Developer Group meeting we worked up a list of resources to help us learn about Android development.

autoplay

One resource was red dit. They have an android development list. This list has over nine thousand readers. <break time="1s"/>Red dit allows voting on posts. You see the top post has one hundred and twenty votes. <break time="1s"/>

autoplay

And here is this top post. It is a big block of text for you to read.

autoplay

It discusses the software development kit, and the native development kit. Then it provides a link to the official Android tutorial for setting up Eclipse. <break time="2s"/>

autoplay

I think all this reading is a barrier to entry. Given a tool which can explain things with pictures and spoken words, it becomes much easier to have a show and tell.

autoplay

So lets use this tool, slide speech, to give an introduction to android.

autoplay

The first thing to observe is that we do pretty much the same thing as the author of the red dit post. We just type the introduction.

autoplay

We can use screen shots to show things and words typed into the speaker notes of the slides to tell about them. <break time="2s"/>It comes out like this.

autoplay

Android has two development kits. The SDK or software development kit. And the NDK or Native Development kit. <break time="1s"/>

autoplay

With the SDK you develop using Java. The Java is then interpreted by the virtual machine to run native code.

autoplay

With the NDK you develop using C or C sharp. So you are writing native code. <break time="1s"/>

autoplay

So with Java, you work at a higher level and make use of libraries. With native code, you are writing libraries, such as the open graphics library, open GL. <break time="1s"/>

autoplay

Development speed is faster with Java. Native code does not require the virtual machine, so it can run faster. <break time="1s"/>

autoplay

The official site, developer dot android.com, has instructions for installing the SDK.

autoplay

The last thing the red dit introduction does, before launching into a line by line code review, is link to this image. <break time="1s"/>They do not bother to explain it. <break time="1s"/>They just say it is handy. <break time="1s"/>

autoplay

With Slide Speech, we can step through this flow chart. Explain how the on create function works to initialize an activity. <break time="1s"/>

autoplay

How the on start function contains code relevant to an activity which may have been idle and is now restarting. <break time="1s"/>

autoplay

How the on resume function is for an activity which paused when another application came to the foreground. For example, when the phone rings in the middle of a game. <break time="1s"/>

autoplay

And so on. <break time="1s"/>This provides a much more helpful explanation, don’t you think?

autoplay

You be the judge. Do we have a winner? Give your applause to the approach you like better. <break time="1s"/>

autoplay

Lets hear it for red dit? <break time="3s"/>

autoplay

OK, and now, let’s hear it for slide speech. <break time="3s"/> OK. Great. Thanks.

Help
Move Around	← →
Help	0

×