When we are out talking to developers about AIR, we spend a lot of time discussing offline applications. AIR has a lot of functionality for building offline applications such as connectivity APIs and an embedded SQLite database engine. What we don’t focus on is how you actually approach architecting these applications. Not only do you need to consider how to architect your code, but how do you actually surface the functionality to the end user?
Google recently announced a new browser plugin that allows you to build offline applications within the browser called Google Gears. Much like AIR, Google Gears uses an embedded SQLite database to store data for offline access. But again it is up to the developer to consider how to architect their application to use this functionality effectively.
Although there are differences between the Google Gears and AIR implementations, the way you architect your application is going to be very similar. Google just recently published a case study of a startup called Remember the Milk that is using Google Gears to do offline data storage within its Ajax based task management application. Although this article is targeted at developers using Google Gears, there is a lot of information that will be valuable if you are developing a Flex, Flash, or Ajax based AIR application and want users to have access to online data when they are offline.