I work on Unity-to-Cocos ports for browser games and playable ads. My workflow combines playable-shared-kit conversion tooling, cc_playable_framework runtime integration, and capture-based visual validation.
The stack behind the port
playable-shared-kit: inspect and convert. cc_playable_framework: integrate, run and build. Scaffolds still need behaviour review.
A repeatable porting workflow
Start with one representative effect or mechanic. Fix mismatches, then replay the same controlled case.
Tooling that makes the result reviewable
Unity Intelligence supplies source inspection and Unity reference captures. demo-studio aligns captures and produces side-by-side comparisons. Resource and build tooling supports asset-footprint checks and browser delivery.
Compare visual behaviour using the same camera and clock. Check frame time, package size and input separately.
A low average difference can hide a missing flash. Review motion, trails, timing and capture warnings before treating a port as ready.
A real ported effect
Cocos Creator capture of a ported 3D Lasers effect. Original Unity asset: Hovl Studio, 3D Lasers. This GIF illustrates motion; full captures support validation.
Have a Unity-to-Cocos porting challenge?
Planning a migration, or hiring for porting expertise? Share your target platform and a representative effect or gameplay mechanic in the comments. I can discuss conversion scope, runtime integration and validation.
Top comments (0)