Question 1

How do I store a Swift struct in Realm using Unrealm?

Accepted Answer

Conform your struct to the Realmable protocol and register it with Realm.registerRealmables() in AppDelegate. Then, you can save and retrieve it using standard Realm operations without subclassing Object, as shown in the usage example.

Question 2

Unrealm vs Realm Object: which should I use for a new iOS app?

Accepted Answer

Unrealm is better if you prefer Swift's native types and protocol-oriented programming, but Realm Object is superior for apps needing live objects or with existing Object-based code. Consider your real-time data needs and codebase style.

Question 3

Does Unrealm support Realm migrations?

Accepted Answer

Yes, but it relies on Realm's migration system, and since it uses native Swift types, you may need to handle type changes manually, similar to standard migrations but with attention to protocol conformance and data integrity.

Question 4

How to update an object manually in Unrealm after changes?

Accepted Answer

After modifying an object, you must call realm.add(object, update: true) within a write transaction, as live objects are not supported. This ensures the database reflects changes, but adds manual overhead.

Question 5

Is Unrealm thread-safe with Realm databases?

Accepted Answer

Unrealm mitigates thread-related crashes by handling access internally, but you should still follow Realm's threading guidelines. However, manual updates can introduce concurrency issues if not managed carefully.

Question 6

Can I use Unrealm with SwiftUI and @State?

Accepted Answer

Yes, but since live objects are lost, you'll need to manage state updates manually, possibly using Combine or custom observers to refresh views when data changes in Realm.

Unrealm

What is Unrealm?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions