Changing the DB structure in iOS and Android projects?

Question

Database

We plan to make a new project, both for iOS and Android. Because Apparently, the DB structure may change over time, several questions arose:
- does it make sense to use SQLite in both versions, or is using CoreData under iOS more justified (again, due to a simpler change in the DB structure)?
- What would you recommend for working with databases (SQLite) under Android (changing the structure and preferably the data itself)? After all, as I understand it, there is nothing like phpMyAdmin for Android developers.
- Maybe there are ways to programmatically flexibly change the structure from version to version of the application?
I would be grateful for links to any useful materials.

Answer 1

1. In Android, out of the box, there is a versioned base.
2. You can think about a flexible base schema, where the entity is determined, for example, by a set of its properties (in a separate table)

Answer 2

For IOS it will be better to use CoreData.
I hope you find everything you need here .