I'd like to provide backup functionality to my app, it's a financial app.
I'm not really sure what type to provide, dropbox or wifi, or something different?
I just want to provide something simple / quick to develop, so users can import / export aka restore / backup.
Any suggestions / thoughts ?
Possibly the quickest way is to use iCloud - that said, Apple strongly discourage you from using iCloud in apps to store sensitive data. If your data is very sensitive (ie, financial), it sounds like you might need to look into some kind of secure system. Plain e-mail as suggested may not be the best solution.
From what I understand you want your users to be able to backup their data from within your application. If this is correct then you can create a CSV file and then send it to either your server to store, or maybe allow your users to email themselves the file (as long as you allow some sort of method to import CSV files - preferably if you stored this on your own servers and database for the user).
Here is a good link for converting your users data to a CSV file.
How to convert the NSMutableArray to CSV file on iPhone?
Related
I am writing a server that allows user to upload images. It appears that most people tend to store those files on the filesystem directly.
My question would be if that really is the way how to do it. I'm not familiar with the capacities of a server but what I'm curious about is e.g. how to make sure that the server does not run out of (hard drive) memory?
I would also like to know how one would organize those files for many different users. Is it enough to just store it like war/images/<user-database-id>/<uuid-for-image>.(jpeg|png) by just using the user ID inside the database or are there a lot more things to consider when it comes to storing images?
I think your best bet would be to use a cloud storage system such as Amazon S3, Google Cloud Storage, Rackspace, or MS Azure.
Using a path like the one you suggested ought to be possible but you could also omit the user-database-id if that database already gives you a list of objects owned by that user.
In my App I Want to implement two way syncing with My server. I want to work offline When I do not have internet. I have managed core data for that. But at starting of my app I want to load all my data(that contain text , images) to sqlite file.
Is it a good approach? I think It is not user friendly. After Offline work I need I want to sync the changed data with server. I achieved it with the CSV File(text in CSV file and all my images are going with NSURLSessionDataTask). But this work is so complex to handle. Can any one help me with a good solution. Every solution is welcome
There is a possibility that a user of my app may enter tens/hundreds/thousands of pieces of information into the app. For example, they may enter names, addresses, phone numbers of various people.
What would you recommend is the best way to store (a potentially large amount) these strings?
Ideally, I'd like to be able to export the inputted data as a text delimited file or a spreadsheet.
You should consider either CoreData or sqlite. CoreData can be over an xml or sqlite database. If you use sqlite, you should consider the fmdb wrapper on github
But, a lot depends on the access patterns. Sqlite is very fast but it also offers querying capabilities.
Sqlite3 is a great way to store a large amount of data.
http://www.icodeblog.com/2008/08/19/iphone-programming-tutorial-creating-a-todo-list-using-sqlite-part-1/
Failing that you could always use NSUserDefaults
I've tried looking around but honestly not finding much help. I am mostly seeking for advice as to how I should approach to develop what I am thinking.
I want to accomplish something like this.
Imagine a website, with a backend database. This database contains information fed by users themselves. The website is fully functional, now I want users to be able to have the same functionality on their iPhones. I don't use a local database because I want all users to be able to have access to the same database, and this changes constantly.
What would be the best approach to:
Allow users to access all the information currently available on the website (database perspective).
Able to edit & add new entries to the database
I don't know if me creating an array to hold all this data would be wise to do. Specially with large amounts of data. I dont know how well it can scale.
Should I create a duplicate SQL lite database on the phone itself duplicating that of that website? What do you guys feel would be a good approach to this?
Comments, links, references would be greatly appreciated.
Thanks!
Sounds like the perfect time to create an API for your website. If the size of you application is not very big, you can use the same database, but would be good to run the API separated from the web server.
Essentially, such an API should allow you to make requests to certain URLs for retrieving, updating and deleting information from the database.
Depending on what server-side platform you are currently using, there are many options.
Client-side, your iPhone app can use http://restkit.org/ or http://allseeing-i.com/ASIHTTPRequest/ if you feel confident.
I'm diving into iOS development. I am building a simple Diary app. I'd like to be able to export my data somehow to my other computers. What are some common, simple steps to export plain textual data?
Thanks in advance for all your help!
A few options spring to mind.
Give the option to email it
Utilise 3.2/4.0's file sharing APIs to allow access to documents created within the app via iTunes
Upload to a webservice
I'm sure there are more, but that's what I immediately thought of.