Being a part of a company that preaches best development practices and lives by TDD, unit testing will be a big part of my Android development learning. Here is a good start to setting up UTs (the basis of this is the Hello World tutorial)
http://developer.android.com/resources/tutorials/testing/helloandroid_test.html
Sunday, September 18, 2011
Hello World tutorial
Very informative tutorial for beginners. If you're used to Eclipse, then setting up your local environment and running Hello World should ideally not take more than an hour
http://developer.android.com/resources/tutorials/hello-world.html
http://developer.android.com/resources/tutorials/hello-world.html
Setting min SDK version
Apparently setting the min sdk version is important. This is what determines if your app will run on a device or not. For example if you set the min-sdk verison to 5, it will not run on devices that have API versions less than 2.0 - for such devices the app will not even be available for downloading in the Android market.
It is suggested that you compile the app in the lowest available version that it can support. This version determines what functionality is available for the app use. For example if you want to use features that were introduced in say version 3 these features are obviously not available on lower version 1,2 - so the min sdk should be set to 3.
Android API versions are forward compatible so an app developed on version 1 will run on version 10. But while testing, please run the app with this lowest version - you can set versions in AVD.
More info about the different API levels:
http://developer.android.com/guide/appendix/api-levels.html
Here is the current distribution of Android platform versions - updated on Sep 2 2011. Based on this, I decided to set the min-sdk level to 3 - to support 1.5 and upwards.
http://developer.android.com/resources/dashboard/platform-versions.html
It is suggested that you compile the app in the lowest available version that it can support. This version determines what functionality is available for the app use. For example if you want to use features that were introduced in say version 3 these features are obviously not available on lower version 1,2 - so the min sdk should be set to 3.
Android API versions are forward compatible so an app developed on version 1 will run on version 10. But while testing, please run the app with this lowest version - you can set versions in AVD.
More info about the different API levels:
http://developer.android.com/guide/appendix/api-levels.html
Here is the current distribution of Android platform versions - updated on Sep 2 2011. Based on this, I decided to set the min-sdk level to 3 - to support 1.5 and upwards.
http://developer.android.com/resources/dashboard/platform-versions.html
Welcome to my Android world
I've been dabbling in Android programming for almost a year now, my primary interest - coding. Worked on a few sample apps, been exploring the API, involved in local user groups etc. but so far i haven't written a committed app yet. This is what I intend to do to learn the full capabilities of this emerging technology and get myself prepped for what I think is the future of IT.
The intent is to chronicle my learning experiences, my failures (hope I don't have too many of those!!) and anything else that I can share.
Hope I have fun doing what I'm planning to do, and hope the readers (if any!) get something good out of my efforts.
The intent is to chronicle my learning experiences, my failures (hope I don't have too many of those!!) and anything else that I can share.
Hope I have fun doing what I'm planning to do, and hope the readers (if any!) get something good out of my efforts.
Subscribe to:
Posts (Atom)