Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
Just wanted to know if Firebase Persistence Storage is encrypted when it caches to the disk on the device. We want to leverage Firebase syncs on a certain path to push faster updates to the users.
The disk persistence that Firebase Database uses on the local device when you enable persistence is not encrypted by the Firebase client. Anyone who has access to that file can read the data inside it.
Firebase storage is not encrypted
This will be useful : Securing Firebase: Preventing administrators from being able to see all users' data in the Forge?
Firebase storage provides rules for providing security to data. Visit here
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I have a requirement to write data processing logic at Server-side and based on the outcome of that logic to send notifications to multiple iphones. I want to use Google Firebase to store data. But I am not sure if Google Firebase allows to write some programming logic at Firebase side to manipulate those data. Can someone please advise if I can write code logic at Google Firebase? T
To run server-side logic in response to events happening in your Firebase project, you'll want to look at Cloud Functions for Firebase. With Cloud Functions you write code that runs on Google's servers and that is called in response to activity in your Firebase project, or calls from your client-side app.
The documentation has a page with common use-cases, which includes sending notifications to users when something relevant happens in the database.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I am developing an iOS calendar app using swift.
I'm using a firebase database because the server needs some data.
But it takes too long to fetch data, and nothing is visible unless there's a wifi (or cellular) connection.
I want to make my schedule visible even if I turn off wifi or cellular, like Google Calendar or iCalendar.
I heard that there are sqlite, realm, and core data available. Which of these should you use? Can all three be synchronized with firebase?
If you are using Firebase then there is no need of using another Database or saving mechanism. Firebase has offline Capabilities which should suffices your situation.
Have a look at this Offline-Capability
You can enable offline access with just single line of code:
Database.database().isPersistenceEnabled = true
With this enabled, Firebase will automatically handle the synchronisation.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am developing an app where I am going to use NSUserDefaults to store some profile variables (name, picture, etc), I think.
I think I need to store some long huge lists of values for each user and I read about Parse and Core Data. What is the best? Can Parse replace Core Data?
What is useful on this case? Both?
Thanks in advance
Parse will store your data on their infrastructure on the cloud. You can enable Parse object caching to keep that data for offline use as well. For most apps I build, I avoid using CoreData (although Parse may be internally using some for of local store, could be CoreData) and use Parse explicitly with caching.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm building an app which fetch posts from server. My question is straightforward: My UITableview has a data source. The data source can load data directly from the server when user hit reload. So why do I want a local store like core data?
One benefit is that loading from a local data store is much faster than loading from a web service. As such, a common pattern is to cache the most recently retrieved data in a local data store and display that while you're making an asynchronous request for any updates.
One example would be Facebook's apps. When you open them from a completely shutdown state they are populated with previously loaded posts, and when a refresh request completes the UI then refreshes with the new data.
The thing to remember is that with mobile devices network connectivity can be highly variable and/or non-existent. If your app requires connectivity and up to date info at all times, then maybe you don't need a local store? But it does help improve the overall user experience generally speaking.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
The question is very simple.
Should I use Core Data only to persist data, to store it locally on a device or should I use it ALWAYS just to manage my application's model even if I do not persist significant amount of data?
What do you think?
Core Data provides an infrastructure for change management and for saving objects to and retrieving them from storage. It is not, though, in and of itself a database. You can use an in-memory store in your application.
Use it Always ? : NO. Use it when you think that your require the features that the Core Data framework offers to you, like any other framework.
Short answer is no. As others said if you do not need persistent store just create runtime objects and manage them.
Even when you need persistent database, Core Data is not always the best solution. For example if you have multi-platform app, or if you plan to port your application in future I'll definitely consider use base sqlite3 with requests. This way I can use same database structure in my Android, iOS and BB application, and even my sql statements will be written only once(with their interface) and then I'll just need some platform specific implementation above them.