In-app store theory: Buying scenarios?

[zardon]

I have an app I'm building where I would like the user to be able to have scenarios (with their own data), but I am unsure about the theory.

1. The app comes with a pre-built-in sqlite database (let's call this BASE.DB).

2. The BASE.DB at its most basics would be:

tbl_scenario { id, name, details, etc }
tbl_game {id, scenario_id, name, date_saved}
tbl_boxer {id, game_id, name, etc}

3. I would like the in-app store to give the customer different scenarios and their own data. The boxers could be different in each scenario.

I'm totally stuck on the theory (not the app-store bit).

1. How do you make sure the scenarios do not overwrite BASE.DB?

2. Do you make separate databases for each scenario? This is more of DB structure issue. How would you create a db structure for scenarios?

3. How do you tackle scaling issues? For example, BASE.DB = 3MB database, now the user gets 5 scenarios = 3MB * 5 = 15MB.

a. One answer would be you can only have 1-3 scenarios on your phone at any one time?

5. Can you use the in-app store purchases purely for SQLite databases which contain my scenarios?

Has anyone built an app that has in-app-store purchases for sqlite databases ("scenarios")?

[dany_dev]

Originally Posted by zardon

I have an app I'm building where I would like the user to be able to have scenarios (with their own data), but I am unsure about the theory.

1. The app comes with a pre-built-in sqlite database (let's call this BASE.DB).

2. The BASE.DB at its most basics would be:

tbl_scenario { id, name, details, etc }
tbl_game {id, scenario_id, name, date_saved}
tbl_boxer {id, game_id, name, etc}

3. I would like the in-app store to give the customer different scenarios and their own data. The boxers could be different in each scenario.

I'm totally stuck on the theory (not the app-store bit).

1. How do you make sure the scenarios do not overwrite BASE.DB?

2. Do you make separate databases for each scenario? This is more of DB structure issue. How would you create a db structure for scenarios?

3. How do you tackle scaling issues? For example, BASE.DB = 3MB database, now the user gets 5 scenarios = 3MB * 5 = 15MB.

a. One answer would be you can only have 1-3 scenarios on your phone at any one time?

5. Can you use the in-app store purchases purely for SQLite databases which contain my scenarios?

Has anyone built an app that has in-app-store purchases for sqlite databases ("scenarios")?

Using more than 1 db no make sense.

in tbl_scenario there is "id" that identify the single scenario, not? if so you should just add others records with other id. If there isn't add it a column like "id_scenario", so that you can insert more than 1 scenario, when you will do a query you have something like "SELECT * from tbl_scenario WHERE id_scenario='1'".

or i missunderstood your request?.

[zardon]

Originally Posted by dany88

Using more than 1 db no make sense.

in tbl_scenario there is "id" that identify the single scenario, not? if so you should just add others records with other id. If there isn't add it a column like "id_scenario", so that you can insert more than 1 scenario, when you will do a query you have something like "SELECT * from tbl_scenario WHERE id_scenario='1'".

or i missunderstood your request?.

This makes sense; the only issue is that you could wind up with a 1,000 boxers for different scenarios.

Maybe I'm just over-complicating the whole thing and just keep the whole app nice and simple.

Thanks for your help.