I’ve decied to add a new (occasional) series to this blog which is primarily intended to keep notes on development for the Android platform. I need to write this stuff down somewhere, so I might as well do it here.
In this first installment, I want to deal with upgrades to your app’s database. As you may be aware, the SQLiteOpenHelper class defines a convenient onUpgrade() function, which is called when your database scheme needs upgrading.
Not for the first time I came across a missing API in Android yesterday. It’s not like you can’t live without it; in most cases you certainly can. But there’s a bit of functionality missing from Android’s View class that would be very handy when trying to extend existing widgets.
Today’s post on the Android Developers Blog annoys me. Titled Integrating Application with Intents, it describes pretty awesome mechanism by which one app can re-use parts of another app’s code, provided both are structured properly.
If you’re technically inclined, head over to that blog for the nitty-gritty of things. It’s pretty well done — and obviously not the part that annoys me.
Read more on PackRat’s blog: (Not) Integrating Application with Intents
It saddens me to say this, but Android’s Activity Lifecycle is broken by design.
It saddens me, because I enjoy developing for Android, and would like to be able to only say good things about it. But that doesn’t mean there aren’t bad sides either. Read on if any of this is of interest to you.
![[FSF Associate Member]](/images/fsf_4971.png){kind=small}
![[frdm] Support SFLC](/images/support-sflc.png "Software Freedom Law Center"){kind=small}
