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 2 years ago.
Improve this question
I am beginner to building Apps with React Native + Redux.
I am trying to create an App family budget. It's almost done.
BUT I have two questions for them who already created these kind of apps.
What is the best way to save data? I want to save it (data: expenses/dates/category etc) on devices iOS (not database) if it's possible. I think it does not take a lot of memory. I've read about AsyncStorage, but not sure about it. Is it still present after reloading App/Phone?
How to share data between two users? I want to make a function, like sharing the budget between family members.
I will be very grateful for the recommendations and suggestions, maybe even for some good articles with explanation.
Thanks!
If you are using redux, you can use redux-persist to store your state on devices.
To share data between devices, you probably need to implement a remote server (cloud), which receives budget changes and propagates them to other family members.
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
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 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
With the new app-extension kit, I'd like to know if it's possible to build an app that tracks various usage statistics of other apps. For e.g., the no of times someone uses their calculator or the no of minutes spent on Quora.
This is a really nice idea to enhance the ability of iOS system. However, even in iOS8 this is unlike to achieve. Apple has offered so limited APIs for APPs to access other APPs. In those APIs, I cannot find any one to record other APPs' launching or closing. (Except you call that from your own APP so that you can record the time, but this is meaningless.)
In the official document for App Extension Programming, manager for APP is not a type that is mentioned in the guide. I'm afraid that you have read it and it cannot give you more help.
I tried to do research on the most detail list of iOS APIs to find whether this is possible. But since iOS5.0, Apple no longer provided the API diffs. Here is the search result.
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
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 am currently new to ios so I do need help in this. I am trying to probe the sandbox of an iphone to retrieve any data from an application such as contacts. From what I know, I need to have understanding of c/obj c programming and understand the features of the mobile with regards to sandbox. So for my questions,
1)How should I get myself started?
2)Are there any features of the mobile regarding about sandbox should I need to understand before proceeding? (Some examples would be great)
3)Do I need to create my own application such as an app that stores contacts to probe on(using XCode)?
4)Any critical information that I missed out?
Much help is needed. Thanks. This is for educational purposes
The sandbox is given to you by iOS, no need to set up or anything. The sandbox means that your app is limited in accessing system resources, specifically file system, documents and settings. It can play only in its "sandbox". But there is no mock like environment that you can use for testing.
For more info on the sandbox, check out the iOS Programming Guide.