A quick survey of Android app development tutorials/posts yields volumes of beginner guides and hyper specific technical details. Certainly beginner guides are critical - every developer needs a jumping off point. Additionally, technical proficiency is requisite for developing meaningful apps. But is that all it takes to be a good Android developer? Is the job really all about "How to do X"?
Not in my experience.
I'm a professional Android developer with about 5 years in the Android app industry. My anecdotal experience has demonstrated that classic software engineering principles, application architecture, effective communication, and agile development processes are where the most value lies for Android developers.
I'd like to bring that experience and insight to Steemit...that is, if Steemit readers like you would appreciate the insight. If so, please up-vote this post, I'll get the signal that Android dev strategies are in demand, and I'll begin writing guides that might help you solve your app development problems in new ways.
Future posts will attack questions like these:
- Is code really the solution to coding problems? (Intro to application architecture)
- What if Android apps are the same as all other apps? (Analysis of Activitys, Services, and Broadcast Receivers)
- Do you even know why you're writing code? (Code readability)
- Source code isn't a meritocracy...or is it? (Code ownership and oversight)
Etc, etc, etc...
Let's fill in the holes of Android dev education together. Simply click that upvote and I'll get to writing!