Here are some facts:
- HTML5 has a Database API that lets you store things locally and retrieve them with SQL queries.
- Android lets you embed a WebView in your application to display web content.
- How to combine #1 and #2 is extremely poorly documented.
One thing that kills me about the Android documentation is how it’s so hit-or-miss. Some things are so well documented that I have literally been able to copy code out of the docs into my code and just change it a little. Actually, my roommate saw me do this at one point and accused me of plagiarism. But that is the subject of another post entitled “Why You Shouldn’t Take Coding Advice From Psychology Majors”.
But really, I think the #1 best thing you can do when releasing a platform or public API of any sort is include tons of samples, inline with the documentation. The real winners when it comes to doing this are the PHP documentation and the MSDN .NET Framework documentation. Almost every single class and function in the docs for these platforms includes a sample of how to use the thing.
Maybe it’s not a coincidence that PHP and .NET are so popular?
It took me way too long to find out how to enable HTML5 Database API support for content displayed inside a WebView on an Android. The pieces were scattered all over the Intertubes, though I finally found the last piece of the puzzle on Joe Bowser’s blog. Here’s the entire thing put together:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Note that the
onExceededDatabaseQuota is mandatory. I am pretty sure the default
quota is zero, so you need to override this method and provide a quota to allow
storage. I’m using
estimatedSize * 2 as the new quota since my app is browsing
to a known page that only stores a small amount of data. Your scenario may be