I wanted to save all my data from firebase database into a local database in (JSON format only) for my application to access it when not connected to internet. It consists even images in it along with string form of data.
Firebase allots very less space for offline mode saving data into the application hence can't use it.
I want data to be first saved in my local database and then to be retrieved into the recyclerView of my application.
Moreover I want to save login details as well as other user specific details required to keep the application function without internet into particular user's login.
Searched for answers but no reliable or step by step guide I encountered.
Are these things possible? What should I do ? Please guide.
Related
Hi I was really hoping to get some guidance with React Native. I'm currently building an App using expo. It's a two part question.
was how to go about storing data when the internet connection is lost. In Africa, internet connection can be lost at any time.
Currently, once the user is logged in, I am saving data into state using Context API. I save my access token on Secure store and some user data on Async storage. However these dont store large amounts of data. How reliable and efficient is SQLite and realm and would you recommend any other option? Realm is not supported on Expo Go however it is seeming to be the best option.
and 2) Supposing I used SQLite or any other option to store data on the phone, how to i go about updating the data on the phone with the newest data on the server once internet connection comes back. I was thinking to overide the entire data?
I'm building a SPA site in React (using redux).
To my site, any user can connect through Google or Facebook.
Each user who logs in to the site receives a personal user_id.
For each user, the system needs to keep a history of documents created by this same user (like the recent docs in Word).
I need to create functionality that whenever the user is logged in he will be able to see a history of the five documents he has created/updated.
In addition, the latest documents will load even after disconnecting and reconnecting to the system.
To load the history into the system I am thinking of using a dedicated index in ElasticSearch.
My question is which way would be suitable the most to use when the user is already logged in and creates several documents one after the other -
Should I need to save everything within the index in ES or is there a smart way to save and update the information locally without producing a lot of calls to DB?
I want that in the end there will be only 2 DB calls that are made in total - one call to load the information on login and one call to update the information when the user logs out. Any other create and update docs will save locally on the client side until leaving the site.
I am currently building a Flutter App for both iOS and Android and the purpose of the app is to collect data from user via lots of forms and then submit it to a backend endpoint.
I need to consider number of things:
User completes half of the form(s) and wants to save locally but submit it later
User submits the form but gets network error so data should not be lost
user submits successfully. at this point data should be either deleted from local storage or be kept and later should get sync with backend db.
Technical points
I may need to use local db. What's the best approach for it?
Maintain global state until data is either stored or sent
I would like to reach out to stack overflow community where collegues may have run into similar situation and can give me some ideas/hints on how best I can architect the app. And What are the libraries / pub packages I can use.
I need to use Flutter only.
for storing the to be submitted data you might be looking for the shared preferences plugin. this lets you store data locally on the phone and lets you edit and delete this when the sync has been completed.
I have a question about web3js.
If my site will load data directly from blockchain (MetaMask) without loading them into the database, and immediately through js bring them to the site then:
1. If a large number of events (1-10 kk) then analyze them on the side of the browser is a bad idea? Need to record everything in the database and the user to publish the analyzed information from the database?
2. When a user enters the site, then in fact his browser parses the information out of the blockchain (if using MetaMask)? Not my server. And I do not care how many connections go through web3js at the same time
What the best?
1. Get all data with web3js and show them on site.
2. Or get all data and writing to database, then use ajax for dinamic show data?
For the past two days, I finally was able to understand how to extract data from Facebook's Graph API.
How to use Graph API to get user's total friend count [JavaScript]
Awesome, right? Now, for the next part.
I want to be able to store this data so that it can be publicly displayed on a user's profile within the application I am developing.
Here is the flow that I am thinking:
User goes to create an account on my application
User is asked via OAuth to pull in their Facebook data such as their profile picture, friend count, etc.
Their data is stored and synced to be always up-to-date [this is what I am trying to figure out]
The data stored is publicly displayed on their profile (such as their friend count)
I never went back to this - but from my understanding now versus what I knew back when I posted this; all one would need to do is store the data in a database so it can be spit back out- and it would just be associated to the user.