Learning Android embedded development - Android Software Development

Hi all,
I have a BSIT with emphasis in software engineering, and I'd like to break into the mobile devices embedded development field (specifically Android). I've never done anything with embedded engineering before. From what I can gather, it's best to learn first Linux embedded engineering and then apply that to Eclipse with a C/C++ CDT understanding, am I correct? As a new grad, I obviously feel that my education hasn't trained me for the real world, but that's not unheard of. The important thing is that I'm a quick learner with a knack for software and I.T.
What would you recommend I start with to self learn embedded engineering for Android mobile devices?
Huge thanks in advance.

Head first is probably the best way to learn. Go to android.com click on the developers link and read the step by step on setting up eclipse/sdk. Start writing apps and improve. anddev.org is a great place for tutorials and general help getting you started. Best of luck!
Sent from my Nexus S using Tapatalk

k4str0 said:
Head first is probably the best way to learn. Go to android.com click on the developers link and read the step by step on setting up eclipse/sdk. Start writing apps and improve. anddev.org is a great place for tutorials and general help getting you started. Best of luck!
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip, however it's not "regular" apps that I want to create. My goal is to equip myself with the knowledge needed to gain an entry or higher type position developing embedded software for microchips at a local company (who happens to be one of the largest developers of mobile processors, etc). I'm currently reading O'Reily's Building Embedded Linux Systems to gain a better understanding of the kernel, etc, but wanted to know if anybody knew of a book or resource that was more catered for Android.

howetechnical said:
Thanks for the tip, however it's not "regular" apps that I want to create. My goal is to equip myself with the knowledge needed to gain an entry or higher type position developing embedded software for microchips at a local company (who happens to be one of the largest developers of mobile processors, etc). I'm currently reading O'Reily's Building Embedded Linux Systems to gain a better understanding of the kernel, etc, but wanted to know if anybody knew of a book or resource that was more catered for Android.
Click to expand...
Click to collapse
You are talking about embedded software development. What is your definition of 'embedded software'? If it is about small microcontrollers learning android might not useful. You should be able to read and interpret printed circuit board drawings and hardware datasheets to be able to understand how to access the hardware from software. You must also be able to write device drivers to interface with that hardware. If you want to create applications for embedded system you must be able to program using relatively sparse resources. Learning all this from scratch is not easy.

doctormetal said:
You are talking about embedded software development. What is your definition of 'embedded software'? If it is about small microcontrollers learning android might not useful. You should be able to read and interpret printed circuit board drawings and hardware datasheets to be able to understand how to access the hardware from software. You must also be able to write device drivers to interface with that hardware. If you want to create applications for embedded system you must be able to program using relatively sparse resources. Learning all this from scratch is not easy.
Click to expand...
Click to collapse
I believe that is what I'm trying to do. The position(s) I'm going for are developing software for mobile chipsets (CDMA, etc) to improve power performance, add functionality, etc. I do understand that it will not be an easy task, which is part of the reason I want to do it. There won't be a dime a dozen going for the position, like there are in typical software engineering jobs. Plus, I could really see myself enjoying it since I'm passionate about mobile technology and am an extremely quick learner.
I think I'm on the right track at least with reading a couple of books, one being the highest recommended embedded linux systems book out there (by O'Reily), and the other being catered for embedded linux engineering using Eclipse and the C/C++CDT.

Related

Developing Debate

Hello there, I've already posted this into another forum but I've been told that this is the place to put this question so here we go
Okay, so I'm starting to develop apps for my XDA2 and having come from a standard PC development background I was always told that software should uphold the basic principles of software quality IE reliability, reusability, maintenance and so on
I thought it would be an idea to here from people that develop for the mobile platform weather they feel it is possible to develop apps with these software engineering fundamentals.
Do we have to abandon object orientated programming, and go back to the procedures in order to develop?
Sorry if this is a, a silly debate, or b, been talked about before
lets have ya
And here is an excert from a reply from on off the board members
Rudegar:
Some people use gcc some people use win stk
where you have to make oo from the buttom if you want being that both are c++ it's by far impossible
and some program mfc and .net where oo is very much a part of the way things are don of cause using these tech's you can still program without following the guidelines of oo
Click to expand...
Click to collapse
Why would you abandon OOP?
In my opinion, OO makes the development of any application easier, not to mention the inevitable maintenance/bug fixing/etc. It allows for reusable code, which is a good thing.
I believe one should develop applications in a way independent of the target platform. The main difference is the GUI design, but I believe the GUI is not to be designed by the person who wrote the code.
I.e., the programmer designs and develops the code and functionality, and someone with good understanding of (G)UI/man-machine-interfacing should design the UI (which the programmer subsequently translates into the application)

Materials For Learning Android Development?

Hey guys, I'd like to learn how to develop for the Android OS.
What materials would to recommend that start from a beginner level that fully explain every step? Examples and learning tasks would be excellent too.
Was shown Professional Android 2 Application Development by Reto Meier which I'm considering buying, but will it be too advanced to start with?
Thanks for any help.
Im looking for exactly the same thing, although i do know a bit of java, it would be nice too have some comprehensive guides.
video learnings
xtensivearts.com have posted 11 series on how to do development on android
and
follow this link for an hour tutorial on android development http://www.youtube.com/watch?v=j8XseabG5j0&feature=player_embedded
and u can find many more videos on related section
First you need to learn java
Here:
http://java.sun.com/docs/books/tutorial/getStarted/index.html
http://java.sun.com/docs/books/tutorial/java/index.html
http://java.sun.com/docs/books/tutorial/essential/index.html
http://java.sun.com/docs/books/tutorial/collections/index.html
http://java.sun.com/docs/books/tutorial/ui/index.html
http://java.sun.com/docs/books/tutorial/deployment/index.html
Depends on how beginner you are
What sort of programming experience do you have? Are you familiar with Java?
It's probably worth taking a look at some of the examples at the Dev Guide section of the Android Developer site (developer dot android dot com). If you're comfortable with that you should be fine to use Professional Android 2.
The book assumes you're a fairly experienced developer who is comfortable with Java (or at least experienced with similar OO languages), but that you have little to know knowledge of Android or mobile development.
houseonfire said:
First you need to learn java
Here:
http://java.sun.com/docs/books/tutorial/getStarted/index.html
http://java.sun.com/docs/books/tutorial/java/index.html
http://java.sun.com/docs/books/tutorial/essential/index.html
http://java.sun.com/docs/books/tutorial/collections/index.html
http://java.sun.com/docs/books/tutorial/ui/index.html
http://java.sun.com/docs/books/tutorial/deployment/index.html
Click to expand...
Click to collapse
You shouldn't include that first link in my opinion
About the Java Technology
Java technology is both a programming language and a platform.
The Java Programming Language
The Java programming language is a high-level language that can be characterized by all of the following buzzwords:
# Simple
# Architecture neutral
# Object oriented
# Portable
# Distributed
# High performance
# Multithreaded
# Robust
# Dynamic
# Secure
Click to expand...
Click to collapse
It's just sounds like marketing and someone stroking themselves.
[Second link]
http://java.sun.com/docs/books/tutorial/java/concepts/object.htm
I'm so ****ed... does anyone any where ever teach things in a manner that shows how things work, besides the bull****???
I'm never going to learn at this rate. Seems like their are peices of the puzzle people don't understand, which i fully understand and have no patience for.. and the stuff every one grabs onto easily is that stuff i can't find taught
[Next page]
http://java.sun.com/docs/books/tutorial/java/concepts/class.html
For some reason I doubt if I plug that code in its just going to flat out work...
Any tutorials that teach in a fashion that says... hey this is what you need to know..
There are variables, classes and this is what needs to go into place for them to work.
In the real world, you'll often find many individual objects all of the same kind. There may be thousands of other bicycles in existence, all of the same make and model. Each bicycle was built from the same set of blueprints and therefore contains the same components. In object-oriented terms, we say that your bicycle is an instance of the class of objects known as bicycles. A class is the blueprint from which individual objects are created.
Click to expand...
Click to collapse
Who CARES??
I want to see the tools and see what needs to be in place for them to work and how to work them.
This turtorial isn't for me
I need a no bull**** tutorial for newbies that flat out says these are the things you needto know how to utilize and this is how you utilize them, in explainable code that works, that isn't missing code someone assumes ill know to put there.
I'm coming to the conclusio that the most difficult part about developing is finding out where you need tolearn from and a good resource to teach you in your own learning style.
I'm a genius in an area everyone is retarded in and a retard in an area that makes the rest of the world seem to have genius about something im missing..
I'd recommend the book called Hello, Android.
I was thinking the same thing... i just can't afford to spend any more money on something that isn't going to teach me in my style...
I'm afraid something might be wrong with the area of my brain that handles communication, language and the english language because there seems to be something about specific things that i just can never grasp unless shown piece by piece a couple of times.
nobody seems serious about showing me anything eer.. they just want to tell me :/
[edit\
Starting here.. ill just tough through what I can but im certain ill be asking some basic stupid questions because there will be something ill be having trouble wraping my head around
2.1 The Big Picture
Let’s start by taking a look at the overall system architecture—the key
layers and components that make up the Android open source software
stack. In Figure 2.1, on the next page, you can see the “20,000-foot”
view of Android. Study it closely—there will be a test tomorrow.
Each layer uses the services provided by the layers below it. Starting
from the bottom, the following sections highlight the layers provided by
Android.
Click to expand...
Click to collapse
**** it, i just skipped to the creating menus section.... who in the world has time for people wanting to jolly themselves by talking a bunch of bull****?
I need to know "how" not "why"...damn it,
Bunnnyman said:
I'd recommend the book called Hello, Android.
Click to expand...
Click to collapse
The example code for enabling the menu button to pop up a menu appears to be incomplete.
I might be stupid but im not that stupid...

I want to be an Android developer when I grow up.

I want to focus on developing GUIs but I'm not sure where to start. I just read through a few pages of http://source.android.com/ to get more information and it was helpful but I'm still not sure what my skill set should be. I also went through Google's new App inventor and finished all the tutorials but it still seems like a toy.
I can: design interfaces, code javascript, implement XML (weak on C and Java but I get it), create anything using photoshop or any graphic application, color-coordinate, test and implement and write--I can write technical instructions fairly well.
So... that said, what's a typical Android designer's skill-set?
Thanks.
Patience, mellowness and a strong constitution!
The Android development platforms so far available are pretty poor if you're used to something like Visual Studio. The best option seems to be Eclipse running the Android ADT plugin. There is plenty of documentation about how to get it all up and running and it is quite easy to install and configure. The app inventor is a toy for non-developers to create simple applications and it works well for what it is but as soon as you want more complex UIs or more complex code, especially when it comes to using external libraries, you will need to get into Eclipse.
You have the right skills, in fact I would say UI and graphics design is the weakest area for many developers. It is for me. I can write beautiful functional code that does amazing things but my UIs suck unless they are simple. I always need to find someone who can help me with that. In my experience, and I have a lot of commercial code development experience, good UI design is a widely missing skill. It therefore pays well and is highly sought after. You might consider specialising in it?
Be careful going from C to Java. Java is still a pig of a language, do a little googling for "problems with Java" and be especially careful of the fact that Java passes everything by reference unless you use cloning. If you don't always write very loosely coupled methods and are good with encapsulation, this will bite you and often in very difficult to understand ways. I recommend running through each method with only this in mind before you consider the first version of the method complete.
My advice to you is to get Visual Studio Express (they're free), either VB or C#, it really doesn't matter, and become proficient with object oriented programming, proper error handling and scope of objects and variables. Do these things, and assuming that you have the right mindset to create good code, and you'll protect yourself from all the usual bugs that amateur developers introduce.
Then move back to Java. Java is a lot easier to be proficient in when moving from something like VB or C# because whilst frustrating, due to the things you'll miss, you will at least know rather than "not know what you don't know", if that makes sense.
If you are serious about doing this for a living, buy some books by Steve MacGuire.
"Writing Solid Code"
"Debugging the development process"
If every develope could do what these books teach, we would have a much more capable software world.
Good luck!
I have the same question? What do you think will be future programming? Developing web apps like Facebook or Android apps?
How is with work today?
I did banchelors from computer science, and want to try masters now, but I need to choose developing Androids apps or Webapps. I am pretty good at C#, JavaScript, XML.
There's a lot of milage in mobile apps, will be good for many years but there is no doubt that the future is web apps.
Excellent! What a great response. Source.android has a lot of information on what a developer should know but I still can't find information on Android GUI design--specifically. Any advice on this?
Thanks.
I think everyone should learn some c/c++ or other native language. Most will say im crazy for saying this but to appreciate what comes with the languages u mentioned above(which are all managed code) I think you should learn power and use behind native code.
c#, java, .net are all good places to start, i would not go with vb. If you choose to start with c/c++ you will be able to do any of the above easily. Tho others think its harder to learn...I say others bc i have always preferred c/c++ to the above.
Simonta... You rock!
Many Thanks.

[Q] future android developer

hi guys
I am an 16years old guy android lover.eddicted to Android
after using android from an year I have decided my future to be an Android devoleper
my aim is to work in Google android project or to become an devoleper like cynagon
can u(the best devolepers of xda) say me what languages to learn and all that I need to be a best android developer.
I also have the question that which operating system is good for learning languages and for Android devolepment is it
1 windows
2 mac os x
3 ubuntu
please my life is in ur answers
Really nice to see other ambitious persons wanting to develop in Android I myself have kind of the same question but I will open my own thread about that later.
Now for you.
I would say you should learn Java as I often read. and when you got a good basic of Java ( or any programming language for that matter) about variables and loops.
Also google provides several usefull starting points for android development but I wouldn't start with that before you have a good basic knowledge of programming itself.
http://developer.android.com/sdk/index.html
This link I find very usefull you learn how an android app works. Where is the data stored, what does it do when you click an app away( instead of exiting the problem)
http://developer.android.com/guide/topics/fundamentals.html
That is my 2 cents about Android Development.
For OS I myself use Mac OSX I find it alot easier to connect with adb than Windows but I can't say what is better.
Goodluck! hope to see alot of programs from you!
You need to become proficient in C/C++ and all the rest will fall into place. I recommend the linux platform (you mention ubuntu, but there are several) as the android platform is linux based. I use Gentoo myself.
Gene Poole said:
You need to become proficient in C/C++ and all the rest will fall into place. I recommend the linux platform (you mention ubuntu, but there are several) as the android platform is linux based. I use Gentoo myself.
Click to expand...
Click to collapse
agreed about c/c++, if you are proficient in c/c++ most if not all other languages will fall into place. its not about the language though but rather the theory and principles behind the languages. I suggest c/c++ because imo if you get c/c++ you get all the others.
Gene Poole said:
You need to become proficient in C/C++ and all the rest will fall into place. I recommend the linux platform (you mention ubuntu, but there are several) as the android platform is linux based. I use Gentoo myself.
Click to expand...
Click to collapse
Oh yeah, I agree here as well. In general, Linux is definitely good for learning programming on. All the tools are *free* (most of my college classes dealt with the Linux platform for this reason). Also, at least on Linux, I have not had problems getting ADB to recognize my device. On Windows, I did get my system to recognize my device, but it definitely took longer.
(Using OpenSuSE for my Android development).
Actually, unlike these spectacular developers, I recommend you learn Java. Android IS coded in JAVA and it is an object oriented programming language, which is in many ways VERY different from C/C++.... Then start going through demos of other Android applications till you can read the code and understand what it is doing.
It finally makes sense why Android developers are so far behind the rest in app development....... college degrees would help.
what happens if I learn java, c/c++
mynameisvineeth said:
what happens if I learn java, c/c++
Click to expand...
Click to collapse
I'm not sure what the question is here... Are you asking what you should do after learning those, or for more opinions about which you should start with?
Anyway, the best thing would be to take a computer science course. That way you'd learn all the fundamentals of computer programming as well as specific languages. If you can't do that, you can always just teach yourself. For example, I took a few basic programming classes (e.g. a few hours a week for 10 weeks "Introduction to C") but after that, everything I learnt was self-taught in Java using the Android SDK. I've been working at it for about a year now, and published my first app 6 months ago which has been selling slowly but steadily, so it can be done.
There are many many resources online you can find, as long as you have the patience and time to read everything. The two best places to learn things from are the official developer's guide and Stack Overflow; Stack Overflow is a question and answer site for programmers.
if I learn the three languages in the collage can i devolep apps.
my aim is to become an good android software engineer so please anyone suggest which course should I take in the university such that my future will be bright with google.
mynameisvineeth said:
if I learn the three languages in the collage can i devolep apps.
my aim is to become an good android software engineer so please anyone suggest which course should I take in the university such that my future will be bright with google.
Click to expand...
Click to collapse
You don't need to learn all three languages. I would personally learn Java first since it's excellent to learn basic programming concepts in and techniques and it is the main language used for developing Android apps. C/C++ should definitely be learned at some point if you want to work for Google, but you'll need at the very least a bachelor's degree before you get to that point. If you get to that point, I am sure you will have learned C/C++.
I do OK under Windows, but I recommend Linux if you can. USB drivers and I was good to go. Java is great, seems dauting at first. I would get java first. But once you know, you like it. At least I did. Makes it more difficult to make a mistake, IMO.
Of course, I'm just starting. Listen first to the extremely advanced people that post here.
Good luck!
is computer science good for me?
Depends I know a few Computer science schools where they teach PASCAL I don't think 4 years of PASCAL will be usefull so it kinda depends what classes are given there. Don't you have a summary of what classes you get at that computer science school? and furthermore computer science can be useful but I don't think you have to know what hardware is in a computer to create an android app.
SterAllures said:
Depends I know a few Computer science schools where they teach PASCAL I don't think 4 years of PASCAL will be usefull so it kinda depends what classes are given there. Don't you have a summary of what classes you get at that computer science school? and furthermore computer science can be useful but I don't think you have to know what hardware is in a computer to create an android app.
Click to expand...
Click to collapse
You have no idea what you're talking about. A computer science degree is not about what language you learn and how to program. It's about the concepts of computer science. It doesn't matter what language a computer science program uses. It has everything to do with the conceprd you learn to apply to programming.
Sent from my GT-I9000 using XDA App
If you wanna work on Android, start with an app instead of trying to work on the framework. You'll learn a lot more, much faster.
It sounds like your definition of a computer science degree is closer to what I'd call "computer theory".
Q: What's the difference between theory and practice?
A: In theory, there's no difference between theory and practice.
Yes, learning threading concepts (for example) in one language will carry over reasonably well to another... but you'll still need to learn a new API, and no two APIs are conceptually identical. Actually being familiar with a given language/API/OS/IDE out of the gate is a pretty big deal when it comes time to Actually Get Hired... or just doing stuff on your own with It (whatever It might be).
I was going to start a new thread with the following post, but I think my questions fit with this thread...
"I have a scientific/technical background and know some networking and Linux basics (i.e. enough to set up a very functional home server with SFTP, Samba, DLNA server, etc from Ubuntu/Deb packages), but I have very little computer programming training.
Where is the best place to start if I would eventually like to develop Android apps?
Should I focus on programming fundamentals with Java as the main programming environment or step right into the Android SDK with Eclipse?
Any links to recommended tutorials and lessons would be greatly appreciated too.
Thanks!"
It sounds to me like Java is the best language to use when learning programming fundamentals if the intent is to develop Android apps in the future. Links to recommended educational resources would really make this a valuable thread.
@ChiefNugget: Please learn first Java and then if you have understood the basics take a look at the developer.android.com site. You should buy a good Java Programmer Book Click
Couple of things to get straight here:
1. "Android" is written in C++ - This is the OS of the phone, it's not written in Java - if you want to be big like Cyanogen you'll need to know C++ very very well. *Sidenote: EXCITED FOR GINGERBREAD CODE TO DROP SOON*
2. Java is not a compiled language (why no OS is written in it) it is a "Interpreted" language meaning that there is very little change from what you type to what the JVM (Java virtual machine, in our case "Dalvik") actually interprets and runs as "Java Byte Code"
So it depends what you want your concentration to be in, if you want to write machine level code - hit up the C++ side of things, if you want to write Apps - java is where you should go.
How ever, I recommend to anyone who wants to become a developer, learn C++ before you learn anything. It's difficult for a reason - it makes you better in the end when you understand how memory is managed and why you shouldn't do things that lots of developers do.
Kcarpenter said:
Couple of things to get straight here:
1. "Android" is written in C++ - This is the OS of the phone, it's not written in Java - if you want to be big like Cyanogen you'll need to know C++ very very well. *Sidenote: EXCITED FOR GINGERBREAD CODE TO DROP SOON*
Click to expand...
Click to collapse
And linux is written in C.
Kcarpenter said:
2. Java is not a compiled language (why no OS is written in it) it is a "Interpreted" language meaning that there is very little change from what you type to what the JVM (Java virtual machine, in our case "Dalvik") actually interprets and runs as "Java Byte Code"
Click to expand...
Click to collapse
That is quite debatable. Between "javac", and JIT compilers, java code does indeed get turned into machine code. And "compiling to bytecode" is still has a valid meaning. When I think interpretted languages, I think "no code is checked until it is executed". You find out about syntax errors when you run it, not when you hit the "build it" button on your IDE.
Kcarpenter said:
How ever, I recommend to anyone who wants to become a developer, learn C++ before you learn anything. It's difficult for a reason - it makes you better in the end when you understand how memory is managed and why you shouldn't do things that lots of developers do.
Click to expand...
Click to collapse
Oh, granted. With java you ALMOST don't need to know what pointers are... but what's left will HANG YOU if you're not careful.
GC's spoil you. Kids these days! Why when I was your age... Anyway, getting into the habit of releasing memory early on means closing files and other resources is likewise well understood. Someone learning java only runs into resource management later on... "stunts their growth" as it were... like Europeans and fractions (metric vs Seemingly random combinations of units).
Get off my lawn!

[Q] Getting started with developing games

Hello everybody.
Various game concepts have been springing up in my mind lately and I am starting to think that I should make them a reality: that's one of the reasons why I bought OUYA.
Problem is...
I know absolutely NOTHING about programming, but I am eager to learn. Does anybody know how should I begin (besides of course getting a good Java manual, which I plan to do ASAP)?
Thank you in advance.
Pretty much just learn as much Java as you can and then start with the tutorials on the Android website. I've done very little Android programming though...very little.
There is a couple ways you can go. You can either use java code with the sdk, or C++ using the ndk. Java will be much easier to use, but because it utilizes a garbage collector, you need a slightly higher understanding of how the code works to write fast running code. C++ is more difficult to learn, especially for a beginner, but because you manage memory manually you have complete control over how your game runs. I would recommend starting with java. There is a good book called Beginning Android Game Development which is published by APress, that covers all the basics.
timkd127 said:
There is a couple ways you can go. You can either use java code with the sdk, or C++ using the ndk. Java will be much easier to use, but because it utilizes a garbage collector, you need a slightly higher understanding of how the code works to write fast running code. C++ is more difficult to learn, especially for a beginner, but because you manage memory manually you have complete control over how your game runs. I would recommend starting with java. There is a good book called Beginning Android Game Development which is published by APress, that covers all the basics.
Click to expand...
Click to collapse
Java first. Garbage collection may be something of a crutch, but if you've never touched programming before in your life, you'll want to focus on learning how to just deal with data structures and methods before worrying about memory management.
Of course, that said, you don't want to learn terrible habits in Java either.
Rirere said:
Java first. Garbage collection may be something of a crutch, but if you've never touched programming before in your life, you'll want to focus on learning how to just deal with data structures and methods before worrying about memory management.
Of course, that said, you don't want to learn terrible habits in Java either.
Click to expand...
Click to collapse
Agreed
Thank you everybody! I'm getting the book Timkd127 suggested as soon as I have some spare time
Pkmns said:
Thank you everybody! I'm getting the book Timkd127 suggested as soon as I have some spare time
Click to expand...
Click to collapse
Glad to help. I did just remember though, that book approaches game dev assuming you already know some java. You might want to familiarize yourself with the language before you spend money on a text.
timkd127 said:
Glad to help. I did just remember though, that book approaches game dev assuming you already know some java. You might want to familiarize yourself with the language before you spend money on a text.
Click to expand...
Click to collapse
That's my concern for the OP. Most resources I've seen for learning Android development assume some Java knowledge and most Java resources assume some basic level of knowledge about programming in general. In this case the OP is claiming to have none of that.
The good news is there are many paths available, the bad news is there are many paths available
Most paths fall into one of two categories:
1) Very high level - Flash and Unity are the two best examples for Ouya that I can think of off the top of my head. While both allow you to get into the code both also provide ways to build some things without getting much into code. Great for getting up and going but a lot of times you can end up finding yourself limited by your tools when you take this kind of approach. Personally I'm not a huge fan. In general you tend to develop skills that are specific to the engine/platform you're working with rather than general skills. The low barrier to entry can be attractive - but the frustration of making your square ideas fit into the round holes provided by your tools can be an issue down the road.
2) Very low level - Grab a text editor and start coding some java is more or less what this breaks down to. But even this path there are several libraries you can use to help yourself along and you can even get lower level and dive into the NDK to write native code in C++. The steep learning curve can scare a lot of people away from this path - but you tend to build more general skills that are easy to re-apply with other tools and scenarios.
I cover my thoughts on some of this specific to Ouya better in my thread on OuyaForums where I'm following my own progress on building some simple games for Ouya: http://ouyaforum.com/showthread.php?4074-Baby-steps
Even though it's more intimidating I personally strongly suggest taking approach 2 before looking into things like Unity and GameMaker - develop your fundamentals then look into tools that can help you leverage them into bigger and bigger ideas.
Whichever path you take at some point you're going to need to know how to code. If you're starting with absolutely no knowledge about coding then it's going to be a bit harder. For example the Android Game Development book (Which I'm currently reading and finding very good - it's also written by the author of libGDX which is the library I'm using to speed development.) assumes a basic knowledge of Java and suggests "Thinking in Java" which is available free on-line (for older versions but they're just fine) to bring people up to speed with Java. I'm also reading that (actually reading that more than the android game development book right now) to brush up on my Java basics. But at the start of that book the author makes it clear that he assumes a basic background in some other programming language! Apparently the printed versions of that book come with a CD including a multimedia course covering programming basics. Phew! That's a lot of books to get through!
They aren't great but one set of tutorials that is aimed at the complete and utter noob are the Kilobolt tutorials that were actually started here on XDA before moving to the authors own site here: http://www.kilobolt.com/tutorials.html
I'm not completely in agreement with the approach those tutorials take or with all of their examples...but they are the best I've seen for someone starting with absolutely no programming knowledge looking to get into Android and by extension Ouya development.
If I was just starting out the advice I'd like someone to give me would probably be:
1) Start with the Kilobolt tutorials.
2) Once you're through Unit 1 start reading Thinking in Java
3) Once you're through TIJ or Unit 3 add in Android Game Development
4) Once you think you're ready for AGD start looking into libGDX
5) Build a SIMPLE game. Play some old atari 2600 games and try to replicate one.
6) Make that simple game fancier - add some modern touches like better graphics and sound, a high score list, achievements, power ups....
7) Let your dreams take over.
One other source you may want to look into as a total beginner is Udacity...I saw their Java course a few weeks ago and signed up for it but haven't been following it because it's more beginner oriented than I was looking for and...well it's incomplete. One of my big beefs with the Kilobolt tutorials was I started following them last year - and the update rate on them quickly dropped so low I forgot about them. Now that they're complete that isn't an issue. But I wasn't about to dive into another incomplete learning resource so when I saw that Udacity's Java intro wasn't complete I didn't even watch more than the intro video. But it's probably worth checking out here: https://www.udacity.com/course/cs046
jhitesma said:
That's my concern for the OP. Most resources I've seen for learning Android development assume some Java knowledge and most Java resources assume some basic level of knowledge about programming in general. In this case the OP is claiming to have none of that.
The good news is there are many paths available, the bad news is there are many paths available
Most paths fall into one of two categories:
1) Very high level - Flash and Unity are the two best examples for Ouya that I can think of off the top of my head. While both allow you to get into the code both also provide ways to build some things without getting much into code. Great for getting up and going but a lot of times you can end up finding yourself limited by your tools when you take this kind of approach. Personally I'm not a huge fan. In general you tend to develop skills that are specific to the engine/platform you're working with rather than general skills. The low barrier to entry can be attractive - but the frustration of making your square ideas fit into the round holes provided by your tools can be an issue down the road.
2) Very low level - Grab a text editor and start coding some java is more or less what this breaks down to. But even this path there are several libraries you can use to help yourself along and you can even get lower level and dive into the NDK to write native code in C++. The steep learning curve can scare a lot of people away from this path - but you tend to build more general skills that are easy to re-apply with other tools and scenarios.
I cover my thoughts on some of this specific to Ouya better in my thread on OuyaForums where I'm following my own progress on building some simple games for Ouya: http://ouyaforum.com/showthread.php?4074-Baby-steps
Even though it's more intimidating I personally strongly suggest taking approach 2 before looking into things like Unity and GameMaker - develop your fundamentals then look into tools that can help you leverage them into bigger and bigger ideas.
Whichever path you take at some point you're going to need to know how to code. If you're starting with absolutely no knowledge about coding then it's going to be a bit harder. For example the Android Game Development book (Which I'm currently reading and finding very good - it's also written by the author of libGDX which is the library I'm using to speed development.) assumes a basic knowledge of Java and suggests "Thinking in Java" which is available free on-line (for older versions but they're just fine) to bring people up to speed with Java. I'm also reading that (actually reading that more than the android game development book right now) to brush up on my Java basics. But at the start of that book the author makes it clear that he assumes a basic background in some other programming language! Apparently the printed versions of that book come with a CD including a multimedia course covering programming basics. Phew! That's a lot of books to get through!
They aren't great but one set of tutorials that is aimed at the complete and utter noob are the Kilobolt tutorials that were actually started here on XDA before moving to the authors own site here: http://www.kilobolt.com/tutorials.html
I'm not completely in agreement with the approach those tutorials take or with all of their examples...but they are the best I've seen for someone starting with absolutely no programming knowledge looking to get into Android and by extension Ouya development.
If I was just starting out the advice I'd like someone to give me would probably be:
1) Start with the Kilobolt tutorials.
2) Once you're through Unit 1 start reading Thinking in Java
3) Once you're through TIJ or Unit 3 add in Android Game Development
4) Once you think you're ready for AGD start looking into libGDX
5) Build a SIMPLE game. Play some old atari 2600 games and try to replicate one.
6) Make that simple game fancier - add some modern touches like better graphics and sound, a high score list, achievements, power ups....
7) Let your dreams take over.
Click to expand...
Click to collapse
Thank you for all this info! I'll probably dive in the Kilobolt tutorials as soon as I have some free time, then I'll start thinking about which way to take later (I don't know whether all this is more frightening or exciting )
jhitesma that's a very informative and helpful post. Nice.

Categories

Resources