Android dev stack
Writing Android apps.
 |
Google App Engine
Notes:
the Web interfacing portion of my app talks to an App Engine app written with the webapp framework using JSON. Not a good fit for all projects - make sure you can live with its limitations, and that you have a reason to! |
 |
Android
Notes:
|
 |
QEMU
Notes:
The Android dev emulator runs in qemu. learn to love it -- but always test on a real device! |
 |
Eclipse Java Development Tools (JDT)
Notes:
The Android development plugin is actually quite nice, with logging support over ADB, remote debugging, and more. |
 |
appengine-admin
Notes:
Because the built in data store viewer is garbage, and differs vastly between what the SDK version can do and the production version can do. This is consistent, clean, and nicer to use. |
 |
SQLite
Notes:
The only way besides basic key/value Preferences or plain files to persist structured data in Android apps. |
 |
Git
Notes:
Even if you're an SVN shop, you'll need to check out the Android source with Git to look into the bowels of implementation code and upcoming updates. |
 |
Apache Subversion
Notes:
|
What is a Stack?
It's a list of software used to accomplish something. LAMP is an example.
To add a project to your stack, click 'Show Recommendations for this Stack' at the top middle of this page and then click 'I use this' on the projects you use.
Embed
Show the world what open source projects you use.
Android dev stack
