Environment for testing Android database

Question

Environment for testing Android database

Navigation

#1 by (1 votes)

0

I'm developing a simple app with Android Studio, using Java as the language. Currently, I am implementing the login and logout routine and I have some doubts. 1) Do I need to use some local DBMS written in SQL to access locally registered users for the application to simulate the login act? All data would be fictitious, just for local testing and validating access errors or code syntax. Could you recommend one with better performance? 2) After performing the tests, how should I proceed in terms of making the database available for access via Web services? Can I use the same bank I created earlier, or should I create one using another technology?

I'm not much inside the workings of these logistical access to banks with Android, so my questions can sweat a little pointless. I'm using Ubuntu OS.

java android android-studio

asked by anonymous 08.06.2017 / 15:07

1 answer

DASHBOARD - Can you export to the Browser ?! (Any language for the web) [closed] Sql server 2008 connection

score 1 · Accepted Answer

1) Do I need to use some local DBMS written in SQL to access locally the registered users for the application to simulate the login act?

Android works with SQLite database (there are NoSQL alternatives), which is local, and also has SharedPreferences to save simple data. SharedPreferences stores only one key-value set.

All data would be fictitious, just for local testing and validating access errors or code syntax. Could you recommend one with better performance?

It looks at whether Firebase meets your need: link

2) After performing the tests, how should I proceed in terms of making the database available for access via Web services? Can I use the same bank I created earlier, or should I create one using another technology?

The native Android database (SQLite) works only with local data, as I mentioned earlier, and remote connection is not possible. In this case, to work with remote data, you need to create a webservice and consume the data by storing it locally. Libraries like Retrofit and Jersey help with this implementation:

link

I do not know if this is what you wanted, but it should help.