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.
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 7 years ago.
Improve this question
I am currently building an app and would like the option of having users view other users playlists. Is this possible?
Of course this is possible. All this data would be in a database, and you would write stored procedures that would fall in a REST API that you would call from your app. You would need to do the filtering of said stored procedure to show users any kind of data you want (if you only want to show 'friends' playlists, or 'people around you'..etc). Remember, it's just all data. Nothing more. You format the data to look nice, but it's still just data.
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 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 building a chat app. Now I know how to create a chat session, but I want to know how to preserve the data of chat history between launches.
Anyone could help me with this?
Work out a data model that can be expressed as a .plist (dictionary, array, string, number, data, date) and keep it in NSUserDefaults.
Use Core Data to mimic the data model coming in through the chat, you can then store all chat objects in core data as they are created and load them from core data on app launch.
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.
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 9 years ago.
Improve this question
I'm trying to determine what would be the best route to go for an app idea I have in regards to using a back-end service or not.
The app will not require any sign up / log in steps
The concept does have a part of taking a photo. For example, a photo could be taken every day, or multiple photos per day, equaling 365 + photos.
I'd like for the user to be able to view these photos at any time, and possibly export them all at once in some form (if that is possible) at any time.
What's the best way of doing this to have a good experience in the app?
I supposed you'd define a good experience in terms of photo storage by being quick. You really don't have many options. You could either write 365+ photos into your documents directory or write them into a CoreData store. I'd probably opt for the CoreData store, because I have a feeling you're going to have some metadata associated with the image.
Really though, this question is a bit too specific to your situation. See also Best way to store images in iOS