Question 1

How do I save a custom object to UserDefaults with Default?

Accepted Answer

Define a Swift struct conforming to Codable and DefaultStorable, then call write() to save and read() to retrieve. The README's VisualSettings example shows this with theme data.

Question 2

Is Default better than using UserDefaults directly for simple apps?

Accepted Answer

Default adds type safety and Codable support, reducing key errors, but for apps storing only a few strings or numbers, direct UserDefaults might be simpler and faster to implement.

Question 3

Can Default handle multiple UserDefaults suites or custom databases?

Accepted Answer

Yes, by overriding the defaults property in your DefaultStorable type, you can specify a different UserDefaults instance, such as a suite for app groups or testing.

Question 4

What happens if I need to store large amounts of data with Default?

Accepted Answer

Default isn't designed for large datasets due to UserDefaults' performance and size limits. For bulk data, consider Core Data or file-based storage instead.

Question 5

How do I migrate from NSCoding to Default for legacy code?

Accepted Answer

Default doesn't provide automatic migration. You'll need to manually convert NSCoding objects to Codable conformances and handle key transitions, which can be time-consuming.

Question 6

Is Default secure enough for storing user preferences like API keys?

Accepted Answer

No, Default uses UserDefaults which isn't encrypted. For sensitive information, use Apple's Keychain Services to ensure security.

Default

What is Default?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions