Let's proceed to the file handling and discuss how you should handle files. First, people shouldn't need to think about the file system while creating, viewing and manipulating files. If your app works with files downplay file handling as much as possible, meaning it shouldn't be something that draws unnecessary attention. You should also instill confidence that work is always preserved unless cancelled or deleted. In general, don't make people explicitly save files. Instead, save changes automatically at regular intervals when opening and closing files, and when switching to another app.

In some cases, such as well editing an existing file, save and cancel options may still make sense for the sake of confirming whether it is actually captured. don't provide an option to create local only files. Users often expect all of their files to be available on all of their devices whenever possible. Your app should support cloud based file storage through a service such as iCloud. implement an intuitive and graphical file browsing interface. Ideally, use the system's familiar document picker from browsing files.

If you implement a custom file browser, make sure it's intuitive and efficient. File browsers work best when they're highly graphical, providing visual representations of files. To speed up navigation, minimize gestures, and consider providing a new document button. So people don't need to go elsewhere to create a new document. let users preview files without leaving your app. You can use the quick look to let people view the contents of keynote numbers and pages documents, PDFs, images and certain other types of files.

Even if your app doesn't actually open those files. when appropriate, share files With the other apps. If it makes sense, your app can share its files with the other apps through a document provider extension. Your app can also let people browse and open files from other apps.