If you’re like me, dutifully following updates from the Android Developers group and the Google Mobile Blog, you probably got excited last week that Google had quietly announced an analytics API giving Android and iPhone applications Google Analytics-esque metrics. And like you, I also immediately checked out the SDK documentation only to find the links it contained to the SDK download were giving back a 403! Serious Buzzkill!
Wheel of Yum has been on the Android market for a few weeks now and keeps getting lot’s of positive feedback. So a few days ago we decided to submit it to this year’s Android Developer Challenge. We agreed on some new features, an improved UI design, and got coding. Being that the ADC submission deadline is tomorrow midnight PT we knew we were kind of up against a wall getting a new release ready, but got everything built and tested by early Sunday evening anyway … and thats when we tried to submit our app to the ADC market…
Working on the new UI for our upcoming 1.1 release of Wheel of Yum I ran into a bug in how Android renders the alpha channel data of a PNG file laid out above a SurfaceView.
Unable to sleep, I got hacking at our upcoming release of Wheel of Yum this morning only to get totally stuck on a bug in how Android animates empty container views. In our particular case we have a custom view derived from FrameLayout that adds a single LinearLayout as it’s only child view upon construction. At runtime, our custom view listens for Touch events and dynamically adds\removes various ImageView instances to the inner LinearLayout. When a given Touch event is complete (i.e. MotionEvent.ACTION_UP) the LinearLayout starts a fade-out style animation: