This is more of an advice question. I am creating and applying that any user from the function will be allowed to make their car's make, model, year and transmission.
Initially, all but first drop-down The menu will be disabled. When the user first chooses "make" from the first drop-down, the second drop-down, model, will be enabled and will display "model" for the user who only chooses "make". If the user selects Ford for the first option, then the second drop-down will be populated only with the Ford model, i.e. Focus, Mustang etc.
I created a web version some time ago and the way I was after every user choice, I inquired from a database, populated the next drop-down, and then refreshed the page. The database was meant to keep the information accessible by the user, the database was not used to keep any information about the user, just data about cars. The way I entered the database was from a CSV file.
My question to you is that, as the application only requires pulling information, it is not included, do we also need a database? Or should we include the CSV file (~ 3 MB) in the APP and the query?
At this time, I'm just really leaning with the CSV file in APP installation. If you think we still need a database, what would be the best option? (MySQL or SQLite).
A good read on Android storage options is located.
If you are reading data only, then I suggest you use the built in resources. There you can keep your data in different arrays and then read it through
No comments:
Post a Comment