I am new to game development. I am interested in developing 2D games for the Android platform. What is the best place to start with (i.e) What are the basics and how to proceed? I already have programming experience in Java but don't have any experience with graphics or animation.

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

8 Answers
8

Android might not be the best choice for starting game development because you would be learning several different things at the same time (Android SDK, making games, optimization, different phone models, etc.). Consider making some simple Java games on your computer to get familiar with making games in general; this tutorial looks like a good place to start.

Once you're comfortable with both Java and game development, start with the Android tutorials. The development guide is very useful, in particular you need to know Android fundamentals and activity life cycle, as well as graphics. Get the Android samples and check out the Lunar Lander and Snake game samples (there's also JetBoy, but that's focused on the JetPlayer).

The canvas class is actually good enough for most 2D games, but if you need better performance or want to move to 3D graphics later you will have to learn OpenGL ES. However, this is beyond the scope of getting started (unless you already know OpenGL).

Another good resource is the book Hello, Android which explores making a Sudoku game over several chapters, including drawing using canvas and handling user input. There's also a chapter on 3D graphics that builds a textured rotating cube.
–
Firas AssaadAug 31 '10 at 19:27

I have just moved from BlackBerry to Android game dev and I want to throw my hat in with Firas: the Canvas class offers more than enough performance for a 2D game. There is no need to add the extra complexity of OpenGL when you start.
–
ADBSep 4 '10 at 12:25

I agree with this answer, but Android isn't the worse place to get started! My very first programming project was a comic book viewer. Then, I made a puzzle game, and now I'm making a 2D game with OpenGL ES 2.0 graphics. I've learned on one heck of a curve, but in the last 9 months, Android has helped me get a good foundation in Java, SQLite, and OpenGL along with a great start with OOP and game development concepts. I could have done worse than learning how to program with Android.
–
Amplify91May 30 '11 at 19:51

Processing.org is another good place to start for (somewhat simplified) coding/development before diving into the Android SDK. It works on Max/Windows/Linux and has a version developed specifically for Android deployment. I highly recommend it - as long as you have an Android phone you can deploy games/apps to your phone that you make with that version of Processing. Hope it helps.

All of these are really good answer. But I am a little surprised that no one has mentioned jMonkeyEngine yet.

Its java, its shader based, its super easy to begin with, very good documentation, awesome community, fast bug fixes, comes with a game development enviroment(jMP based on NetBeans platform) & its evolving very very fast.

I would emphasis more on it because, game development and making a library that someone will be using to make a game is quite different. So, if you want to make a game not a game engine, just jump right in jMonkey Engine with your eyes closed. :)

I did a quick google search about jMonkeyEngine and Android. I presumed that as Android uses it's own Java interpreter that jMonkeyEngine wouldn't work on it. It's still Java though, so maybe they would have made a port. In any event, a minute of research implies that it's a work in progress.
–
xuincherguixeJul 28 '12 at 1:00

jME works on android, there are several projects on the store. I suggest you, posting in their forum for technical specifications.
–
iamcreasyJul 28 '12 at 1:22