The biggest Android event of the year is coming in a matter of weeks.Â Google I/O is a “gathering focused on pushing the boundaries of web applications using Google and open web technologies. Google engineers and web development leaders will lead you through two days full of in-depth breakout sessions on the latest technologies, and informal Q&A at Fireside Chats.”Â
One of the bigger names expected is Dan Morrill, an Android Advocate.Â Before Dan and the others head there, he stops by the official Android Developers blog to talk future proofing apps.Â As a developer, the concern arise over whether to write an app now, or wait for the next version.Â In this case, it’s the 1.1 version versus the 1.5 version.Â Do you write for what already exists or do you take the “wait and see” approach?Â Thankfully, it is possible to take steps to ensure that whatever version of the SDK you use, your app is future proof.
As Dan outlines, there are five things he recommends you do as a developer:
- Avoid Using Internal APIs
- Avoid Directly Manipulating Settings
- Avoid Going Overboard with Layouts
- Avoid Bad Hardware Assumptions
- Avoid Incautious Rotations