Version 1.73 introduces a major UI architecture change on the native side: the legacy PhotoEditor, DesignEditor, VideoEditor, PostcardEditor and ApparelEditor views are no longer the primary integration path. Instead, a single Editor view powers all solutions, and the former solution UIs are provided as Starter Kits that you copy into your app and customize per your business logic.
Do I need to migrate?#
The React Native module wraps the native iOS and Android SDKs, so the impact depends on how much you have customized the native side of your app:
If you have not customized the native code#
You do not need to do anything. Bump the React Native package to v1.73 and continue using the module as before — the bridge keeps working with the new architecture under the hood.
If you have custom native code#
If you have forked, subclassed, or otherwise modified the iOS or Android editor code that the React Native module relies on (for example custom dock or navigation bar items, or custom callbacks wired in native code), you must migrate that custom code to the new starter kits architecture.
Follow the platform-specific upgrade guides for the parts of your app you have customized:
Both guides explain how to replace the legacy solution views with Editor plus a starter kit configuration class, how to update callback signatures, and how to configure UI components through the new builder API.