Question 1

How to save scratch progress in MCScratchImageView?

Accepted Answer

MCScratchImageView doesn't have built-in persistence. You need to manually save the progress property (a CGFloat) to UserDefaults or a database and restore it by re-initializing the mask or implementing custom logic.

Question 2

MCScratchImageView vs other iOS scratch libraries?

Accepted Answer

It's simpler and easier to integrate than alternatives, but lacks advanced features like animation or state saving. For more complex needs, consider other libraries or custom Core Graphics implementations.

Question 3

How to customize scratch animation in MCScratchImageView?

Accepted Answer

The component doesn't support custom animations; scratching is immediate based on touch input. For animated effects, you'd need to modify the source code or layer additional animations on top.

Question 4

Does MCScratchImageView work with SwiftUI?

Accepted Answer

It's designed for UIKit and Interface Builder. To use it in SwiftUI, wrap it in a UIViewRepresentable, but this adds complexity and may not integrate seamlessly.

Question 5

How to handle multiple scratchable areas in one view?

Accepted Answer

You can use multiple instances of MCScratchImageView positioned separately, as there's no built-in support for a single view with multiple scratch zones; each requires its own instance.

Question 6

What's the performance impact with large mask images?

Accepted Answer

The README doesn't address performance. With high-resolution images, scratching might lag due to real-time image processing. Optimize by using smaller images and testing on target devices.

MCScratchImageView

What is MCScratchImageView?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions