Question 1

How to create a custom folder in AppFolder?

Accepted Answer

Extend an existing directory class, define a new Directory subclass, and expose it as a property. For example, to add a 'Files' folder inside Application Support, extend Library.Application_Support and add a class Files with a computed property Files returning subdirectory().

Question 2

AppFolder vs using FileManager directly: which is better?

Accepted Answer

AppFolder is better for type safety and code clarity in complex directory structures, as it eliminates string-based paths. However, FileManager offers more low-level control and is sufficient for simple apps without abstraction overhead.

Question 3

Does AppFolder work with SwiftUI projects?

Accepted Answer

Yes, AppFolder is a Swift framework compatible with SwiftUI, as it relies on Foundation APIs and can be integrated into any Swift-based iOS, macOS, watchOS, or tvOS app, including those using SwiftUI.

Question 4

How to set up AppFolder for app extensions?

Accepted Answer

Define an AppGroup enum with your group identifier, then use AppGroupContainer to access shared directories. For instance, AppGroupContainer<MyAppGroup>.Library.Caches provides a type-safe URL for shared caches.

Question 5

Is AppFolder stable enough for production apps?

Accepted Answer

Caution is advised, as the README warns it's in an early stage with potential instability. It's best for experimental or non-critical projects, or for teams willing to handle possible breaking changes.

Question 6

Can I use AppFolder on macOS without issues?

Accepted Answer

Mostly yes, but note that AppFolder.tmp is deprecated on macOS and may not match NSTemporaryDirectory(). Use FileManager.default.temporaryDirectory instead for temporary files on macOS.

AppFolder

What is AppFolder?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions