Good for dogfooding. :)

Unfortunately, none of the built-in can be easily/directly ported: History panel: - Needs to use the BrowserProvider DB because of the awesomebar search and sync i.e. we can't use HomeProvider - Has a non-trivial way of splitting items into sections (Today, Yesterday, ...) Top sites: - Needs to use the BrowserProvider DB for the same reasons than the History panel - Has a grid stacked as header in the list that offsets the data in the list itself. We have no API for that (yet) Bookmarks: - Needs to use the BrowserProvider DB for the same reasons than the History panel - We don't support folder hierarchy navigation (yet) (see bug 942295) Reading list: - It will have its own content provider because it needs reading list-specific columns (read state, word count, etc) - We'd need to keep it in sync with the offline storage - Probably needs to be sync'd across platforms

I don't think it's worth doing this.