Apps Database, local or not? (MySQL/SQLite?)

[jepperaskdk]

So, I've started the process of building my app, and i have been doing a lot of visual-styling, but now i'd like to add some functionality.

What i'd like my app to do:This app is a workout-app. I will have my users register/login, meaning communication between the app and a database (already got a website+database).

The user will be able to manage and create workouts, but i dont believe theres any reason to store that on a physical-database, since the information will only be used by the user. So i've considered SQLite, which i believe is a local textfile-based database, which will install with the app itself.

So how do i structure this? I know this is a big question, am im just trying to seem like i know what im talking about, and hoping to get a "yes you can do that".

So my question, will the SQLite be enough? Is it common to have the users data stored locally only?

I will have the user set up a profile, with height, weight, age and stuff like that, and these could be stored online - and then remained in case the user reinstalls the app. This is mostly textfile-based information, so would it be smarter to just keep everything on my 'real' database, since it will probably be very small amounts of data?

If you know any links, books, video's or whatever on this, they're all welcome! Thanks in advance.

 

[Rukbat]

SQLite is enough for almost any cellphone app - provided that you give the user some way to back up the data off-phone, and restore from the backup. Even for something as non-critical as working out (this isn't all the user's passwords, or his accounts receivable), if something happens to his phone, or your app blows up the database because you forgot that it crashes when LTE turns on (or some other bug that all apps have), the user would probably like to be able to get his data back when he reinstalls the app.

But if SQLite is good enough for medical records (it is), it's good enough for a workout app.