How to become an Android developer?(kreci.net)
kreci.net
How to become an Android developer?
http://www.kreci.net/android/how-to-become-an-android-developer/
17 comments
This was invaluable advice from the HN community that really helped bootstrap my learning curve:
"Ask HN: Jumping into Android Development"
http://news.ycombinator.com/item?id=1347170
CommonsWare books +1
"Ask HN: Jumping into Android Development"
http://news.ycombinator.com/item?id=1347170
CommonsWare books +1
Eh. I don't mean to knock the article, but there's very little in the way of substance. 'Learn' (to program Android applications) and 'Learn to make your app popular' are just two bullet points out of six.
While I admire Kreci's willingness to share, there isn't remotely enough meat to this for it to be getting upvotes.
While I admire Kreci's willingness to share, there isn't remotely enough meat to this for it to be getting upvotes.
The reason for the lack of substance is pretty obvious. This is just thinly veiled linkbait to get you to buy his ebook. See the last (easy) step.
Yea. This article could have been written about any web store without needing to change much of the content within it.
[deleted]
I would also suggest picking up so general programming books, especially focused on OO programming techniques. The "Head First" series is a good place to begin. Once you get more experienced, head on over the Pragmatic Programmers publisher site for some more good reads.
Great article!
Great article!
Right now I'm using the "Sam's ... in 24 Hours" series - even though the title's promise is slightly misleading. The Java and Android Dev books from this series are pretty good, and I get electronic access to them for free through my university! Huzzah!
pick up MM's CommonWare book instead its somewhat better and usually more up-to-date..biases: MM is a peer and somewhat friend..
1) Get all excited about developing for a great open source platform.
2) Find out that the API is so utterly backwards that getting even simple things to work will cause you hours of pain browsing stack overflow until in blind rage you just want to kill whoever 'designed' this steaming piece of shit.
3) Kill yourself.
2) Find out that the API is so utterly backwards that getting even simple things to work will cause you hours of pain browsing stack overflow until in blind rage you just want to kill whoever 'designed' this steaming piece of shit.
3) Kill yourself.
1) Learn from the examples.
2) Launch an app in a week or two.
3) Profit.
To each their own I guess.
2) Launch an app in a week or two.
3) Profit.
To each their own I guess.
nothing of earth shattering here. I agree with most of the comments. Kreci- I don't mind marketing the ebook at the end. The problem is if you write something so little people will doubt about the content of the ebook too.
anyone can google "how to write android app" or "how to become an android developer". There would be tons of useful links relative links. What you can/should do is make your article unique. Some of the ideas are a) what are the steps involved in developing, submitting and marketing an android app, b) steps in developing android apps for novice developers (google dev site can be overwhelming for newbies). Just some thoughts :-)
anyone can google "how to write android app" or "how to become an android developer". There would be tons of useful links relative links. What you can/should do is make your article unique. Some of the ideas are a) what are the steps involved in developing, submitting and marketing an android app, b) steps in developing android apps for novice developers (google dev site can be overwhelming for newbies). Just some thoughts :-)
As usual comments welcome and very desired! Article is for the beginners as I really needed something similar when I have been starting...
Lets correct the damn article:
1. Learn android programming: Subset of JavaSE vm heap size, etc same design patterns as JaveME; no tot little interfaces and factories, speed wise avoid reflection and enums..learn the mobile java singleton patterns techniques borrowed from JavaEE are dependency injection with no aop
Look for the articles by the tool makers, Robolectric, robotium, MicroLog4Android, etc..
1. Learn android programming: Subset of JavaSE vm heap size, etc same design patterns as JaveME; no tot little interfaces and factories, speed wise avoid reflection and enums..learn the mobile java singleton patterns techniques borrowed from JavaEE are dependency injection with no aop
Yes you have to 'unlearn' some OOP java patterns
This somewhat still short..Look for the articles by the tool makers, Robolectric, robotium, MicroLog4Android, etc..
Its spam at this point. Please stop.