On Wed, Aug 3, 2011 at 1:53 AM, Zsolt Vasvari wrote:
> There is a lot of FUD about Android fragmenation. The vast majority
> of the issue mentioned can be dealt with with properly following the
> guidelines, but there is one issue that I don't know how to deal with:
>
> This forgotten issue is th
On Wed, Aug 3, 2011 at 6:53 AM, Mark Murphy wrote:
> On Wed, Aug 3, 2011 at 2:53 AM, Zsolt Vasvari wrote:
>> For example, if the user moves to a phone with an older version of
>> Android, I can support that older version of the platform just fine,
>> but the user is Sh*t-out-of-Luck trying to mov
On Wed, Aug 3, 2011 at 2:53 AM, Zsolt Vasvari wrote:
> For example, if the user moves to a phone with an older version of
> Android, I can support that older version of the platform just fine,
> but the user is Sh*t-out-of-Luck trying to move their database over
> and they cannot open their newer
On Wed, Aug 3, 2011 at 3:53 PM, Zsolt Vasvari wrote:
>
> For example, if the user moves to a phone with an older version of
> Android, I can support that older version of the platform just fine,
> but the user is Sh*t-out-of-Luck trying to move their database over
> and they cannot open their new
There is a lot of FUD about Android fragmenation. The vast majority
of the issue mentioned can be dealt with with properly following the
guidelines, but there is one issue that I don't know how to deal with:
This forgotten issue is the SQLite versioning problem.
For example, if the user moves to
5 matches
Mail list logo
