What good practices are used to supply, store, flow, data, in a Android
application?
For example, the app EasyTaxi , iFood , among others:
- What is the need / advantage of a local database (what information is ideal for using a database, such as
SQLite
)?; - What application scenario in which the use of a shared database on a server for the large control of information flow (This would be an implementation of in
SQL
)?; -
These apps have two login types, one for the app and one for facebook, how authentication data is managed to maintain the fidelity that the user logging into the app is the same as logging on the facebook api?;
-
EasyTaxi has one module for the Taxi Driver and one for the passenger, which Data Technology is used to supply, store, flow, between one module and the other? >
Really know the best way for this to happen and which technologies to use in a scenario where the app covers a large flow of information and at the same time maintain the fidelity of the messages exchanges of the app, between the modules, the user, the server, it is important, I know how to do this with Delphi
, but mobile is brand new and everything is very beautiful.
I have read and used a little mongoDb
, nodeJS
, relational database, facebook api, but I want to know the straight path, after all we are accurate and this reference is very important.