Solving Solved Problems
July 29, 2013
Last week Google simultaneously announced and released Android 4.3.
The release included a number of new features to the platform plus performance improvements. For developers it brings a number of new API’s. They also updated system images, build tools and the Android support library.
The support library exists to bring backwards-compatible support to API’s introduced in new Android versions.
Most notably this latest support library update included a new ActionBar class which allows developers to bring backwards compatible support for the ActionBar, introduced in Android 3.0 (Feb 24th 2011), to Android 2.1+.
But here in lies the problem. An extremely popular, globally used and well supported library already exists to solve this problem - see ActionBarSherlock. I use it for Dash, at Etsy, and in most of the other apps I’ve worked on. I know other large tech startups use it (Square, GitHub, Foursquare) and even Google themselves included ActionBarSherlock in their 2012 Google I/O app.
Now that we’re halfway through 2013, instead of solving a solved problem, Google could have taken the opportunity to include support for new Android 4.3 API’s in the support library. Like the awesome new ViewOverlay or Optical Bounds Layouts.
This would help solve an unsolved problem, the bittersweet situation after each Android platform release where we developers realise it’ll be a long time before we can use any of the new features annouced.
Maybe the best Google can do when it comes to compatibility is a 2 year timeframe? Guess we’ll have to wait and see.