Logic code reuse between apps for Android and other platforms: To ContentProvider or not to ContentProvider?

Question

I\'m developing an app which I want to make available both for Android and Blackberry (possibly to JavaME in the future). The business logic will be common to all the platfo

Answer 1

This question has now moved beyond the ContentProvider point and into more general territory. I did implement what I had posted about in the original question using the second bullet point - i.e,

Implement SQLite access in the ContentProvider - and then have the DataStore implementation "call" the ContentProvider under the covers

However, as I proceed, I see more such challenges in trying to keep the code common. A few examples:

1. java.util.List not available on Blackberry and JavaME platforms. The only work-around is to use arrays or Vectors. How much of a hit is it to use Vectors in Android?

2. Libraries for binding POJOs to XML/JSON do not work well on JavaME/BB platforms. Some of these libraries make use of reflection (GSON), while most of them use annotations, or at least java.util.List. None of which are available on JavaME. Hence, it is best to write the XML/JSON parsing/framing logic for these platforms by hand. That begs the question - once the effort has been put in to write such a parser, why not reuse it on Android as well?

3. JavaME/BB do not support Generics. While this is not much of a "problem" as such (since all my code is internal - not an API), I will either see too many warnings in Eclipse, or have too many @SuppressWarnings("rawtypes") in my code!

Well, well. Looks like what I set out to achieve and assumed to be a simple task is much more complicated after all!