Question 1

How do I handle state changes in CoreRender?

Accepted Answer

Use coordinators to manage state—they are non-transient objects that hold data and call setNeedsReconcile() to trigger UI updates. This mirrors the CounterCoordinator example where count increments prompt reconciliation.

Question 2

CoreRender or SwiftUI for a new iOS project?

Accepted Answer

Choose SwiftUI if targeting iOS 13+ and wanting full Apple support with native features. CoreRender is better for supporting older iOS versions (10+) or integrating declarative patterns into existing UIKit/Objective-C codebases without a full rewrite.

Question 3

Can I use CoreRender with Objective-C?

Accepted Answer

Yes, CoreRender is compatible with Objective-C, allowing it to be used in mixed-language projects or pure Objective-C apps targeting iOS 10+. The README emphasizes this as a key feature for broader adoption.

Question 4

How to animate views in CoreRender?

Accepted Answer

Animations rely on UIKit's system; you can animate properties within coordinators or use UIView animations by accessing concrete views via coordinators after reconciliation, though this might require manual intervention beyond the declarative API.

Question 5

What's the performance impact of using CoreRender?

Accepted Answer

CoreRender uses efficient diffing and fine-grained recycling for performance, but in highly dynamic UIs with frequent updates, the reconciliation overhead could be noticeable compared to manually optimized imperative UIKit code.

Question 6

How to debug when CoreRender doesn't update the UI?

Accepted Answer

Ensure setNeedsReconcile() is called after state changes in coordinators, and check the virtual DOM hierarchy for issues. Debugging may involve inspecting coordinator state and the reconciliation process, which lacks built-in tools compared to SwiftUI.

Render

What is Render?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions