So, you've got an idea for the best app never to hit Android, and you know it'll take the world by storm once you get it published. There's just one problem: you don't know Java from an Indonesian island. You could quit your job, shop around for investors, hire programming talent, and try to make it on your own. Or you could submit your app idea to Dandy and let the people decide.
We've only got about a month left before Ouya units start landing in the hands of backers and a few months before the full-blown retail launch. A retail launch that we now learn will include GameStop, Best Buy, Target, Amazon, and an undisclosed number of other sellers. Yes, including brick-and-mortar stores. Things are starting to look pretty good for the little console that could.
Speaking in an interview with the Wall Street Journal, Ouya's CEO released a few extra details, including the price: $100 for the console, which we knew.
As a developer, I absolutely love days like today. If the high-level "improves performance and stability and fixes bugs" changelog of Android 4.1.2 isn't good enough for you, how about we dive into the actual low-level source code commit logs Android engineers made into AOSP since 4.1.1_r1.1 (JRO03D) all the way through today's release 4.1.2_r1 (JZO54K). These commit logs are spread over probably 100+ repositories, so hunting for all of them manually would probably take you days.
As an Android developer, I like to keep tabs on the tools I use every day, especially ones as important as ADT for Eclipse and SDK Tools. As was the case several times before, the Android team in charge of both of them posted previews of upcoming releases of ADT 20 and SDK Tools r20, available for manual download ahead of the final releases.
Yup, you heard me correctly - 20, not 18 or 19.
In preparation for the upcoming final releases, the Android team today released ADT 17-preview (Android Developer Tools plugin for Eclipse) and SDK Tools r17-preview with the following improvements that eager developers can try out without waiting any longer.
Out of all the additions and changes, I'm mostly excited about the new network usage tool, the fix for the dreaded "Conversion to Dalvik format failed with error 1" error when trying to use Proguard (oh, how many hours I wasted on this one), and the end to default ids for various layout elements.
In order to make it easier for Android developers to get started with creating robust applications, the Android team today formalized and unified various coding tutorials into one clearly defined area of the Android dev site: Android Training. The tutorials, or classes, are very well put together, with splits into logical steps to make them flow well, along with sample code you can utilize to "do your homework." There is no fee for taking any of them - think of Android Training as a collection of well organized and curated tutorials.
To help Android developers automate some things and catch certain errors early on, the Android Tools team is pushing ahead with a new dev tool called Android Lint. Android Lint will be available in the next release of ADT (16) and Tools (r16).
If you're not familiar with the "lint" paradigm, a lint tool generally helps you validate your code using a certain set of rules in order to avoid common pitfalls.
While most of you have heard of Open Source software at this point (I hope you have, anyway), you probably aren't aware that each year Packt Publishing puts on a contest to highlight the best and brightest Open Source projects across all platforms. The contest is currently in its voting stage, ends on October 31, 2011.