Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'm creating a social media app.
I want to know a way to cache a users profile picture once downloaded from the Parse network and then each time the app is loaded check if an updated picture has been found and load that one, then cache that one.
I have no idea how to approach this, does anyone have any ideas?
There are plenty of third-party libraries for caching you can find on Github, or you can simply use NSUserDefaults or CoreData to save the pictures(or really anything) to disk. To check if a picture was modified, you can give the picture an identifier, compare it with the response from the server, and re-save the picture, or do whatever is needed.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
Could someone please provide from their experience the step-by-step guide or some tips how to download the videos from some specific url, save it locally (please suggest which database to use CoreData, realm or SQLite) and then show it to the user for example in the collectionView?
Firstly, do not store the videos in a database. Use the documents directory. For downloading the videos you can use the URLSession’s dataTask(with:completionHandler:) method or a library such as Alamofire. Once downloaded to local storage, you can go through the files stored there and filter them by extension if you have more file types than just videos. This can be done asynchronously in viewDidLoad(), storing the URLs into an array, then bind them to your collection and call reloadData().
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I would like to know what are the best practices regarding, Modeling data when no network connection available, if the app you are building is cloud computing based, but still you want to be able to have basic functionality and I guess some persistent data?
PD: I am kind of new to IOS development
UserDefaults is okay for small bits of data that don't change often, but as it has to rewrite the entire user defaults dataset to a file each time a change it made, it is not robust enough for anything of volume or with frequent changes. For that you would want CoreData or a third party open source solution like Realm.io.
You can try to using the 'cache' where you store temporary data.
One way to achieve this is NSUserDefaults where you set a variable (let's say users profile photo) and when the user opens his app again, the image will be loaded even if there is no internet connection since its cached. Hope this helps!
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I'm working on an app with quite a few images and general information about them. Are there any general guidelines about when it is a good idea to just bundle the data with your app and when it should just be downloaded on first run? When you should use Core Data and when just keyed archiving is sufficient? Or is there a better solution I haven't even considered?
I imagine that the data will be updated from time to time, but not frequently. I'd like the app to be able to download updates.
Kind of a vague question, and I apologize for that.
It depends on whether the initial data (images & information) is important and always the same.
If you wish to have it dynamically changed to whatever is updated on the server then you shouldn't bundle it within the app. On the other hand, if the initial data is trivial and you can just include it in the app.
Now if you wish to store the initial data locally in the app, given that the data is just images and theirs information, I would recommend to just use keyed archiving to keep things nice and simple.
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 6 years ago.
Improve this question
I have simple TableViewController with customers. Every cell has photo, name and phone number. I want to cache this information. So when you will be offline or has slow connection, you will see information from last refresh until data refresh again. Refresh will start every time you enter this screen. I will have more screens, where I will want to cache different informations. I want to ask you about best practice of caching in iOS.
My idea is to use CoreData with Fetched result controller. Is it good idea or not?
if it's limited data you need to cache, you can also consider NSUserDefaults to read - write and delete.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
My app has to integrate uploading image to set it as profile picture. The thing is all the images has to be stored in web services.
As web service has not been yet created. what is the best way to store images for temporary purpose so that i can integrate it easily when i have been provided with the backend.Sample tutorials can be helpful
My best idea is to use FTWCache (https://github.com/FTW/FTWCache) and cache it localy. Later, using webservice, you can still use your already written cache mechanism to implement NSURLConnection with caching. Profit! ;-)