v1.73 is a mobile-focused release. The main act is our new architectural foundation for iOS and Android: Starter Kits give you full ownership of your editor configuration. On the engine side, CE.SDK now supports SVG export across all platforms.
Own Your Mobile Editor — Not Just the Config
The old model was simple: drop in a solution component (PhotoEditor, VideoEditor, DesignEditor), pass a license key, ship. For most teams, that was exactly the right starting point. Fast to integrate, zero configuration overhead, a full editor running in your app within hours.
As products matured, though, teams needed more. Deeper customization. Granular control over behaviors. An editor that felt like theirs.
That's what Starter Kits for Mobile addresses.
The prebuilt solution components are replaced by a single Editor entry point and a set of Starter Kits: complete, working editor projects for each use case that live in your codebase, not ours. Set it up in minutes.
For your product, this means: you can adapt the editor to fit your product, not the other way around.
Everything Is In Your Code Now
Each Starter Kit is a real editor project — not a thin config wrapper. Every toolbar item, every callback, every loading phase is written out explicitly in files you own.
That means your team can read the integration, review changes to it, and understand exactly what the editor does and why. No more hunting through SDK internals to figure out why something behaves the way it does.
SDK Updates Stop Touching Your UI
Previously, updating CE.SDK could introduce new buttons, changed defaults, or different menus without you asking for them. Your QA had to catch it.
That dynamic is reversed now. Engine improvements, bug fixes, and performance gains come through updates as before. But your editor UI stays exactly where you left it. New features arrive as optional building blocks, documented and ready when you want them.
No More Customization Ceiling
The old configuration APIs had a line between what you could change and what you couldn't. Starter Kits remove that line entirely. You can restructure initialization, inject custom logic between loading phases, and build workflows specific to your product.
If you can see it in the code, you can change it.
If none of the five kits match your needs, the Editor view accepts raw configuration directly.
Migration
This is a breaking change on both iOS and Android. Migration guides cover every change with before-and-after examples.
→ Android Migration Guide
→ iOS Migration Guide
Starter Kit Repositories
| Editor | iOS (Swift) | Android (Kotlin) |
|---|---|---|
| Photo | GitHub | GitHub |
| Design | GitHub | GitHub |
| Video | GitHub | GitHub |
| Postcard | GitHub | GitHub |
| Apparel | GitHub | GitHub |
Export Vector Designs as SVG
Until now, users working with vector content in CE.SDK had no path to get that content out as a vector file. CE.SDK v1.73 adds SVG export via the image/svg+xml MIME type.
Text is exported as vector paths for consistent rendering across environments regardless of font availability. Drop shadows, blur, effects, and embedded raster images are rasterized and included as embedded images within the SVG output.
→ Exporting Blocks Engine Guide
Changelog
See the full changelog for the complete list.
Thanks for building with IMG.LY.
Join 3,000+ creative professionals who get early access to new features and updates—subscribe.