With Snap Kit, Snap moves on from being a “Camera company” and becomes a camera platform, enabling developers to embed, not copy, its best features
Evan Spiegel has finally found a way to fight back against Mark Zuckerberg's army of clones. For 2.5 years, Snapchat foolishly tried …
Context & Ripple Effects
For 2.5 years after Instagram cloned Stories, Snap's answer to Mark Zuckerberg's copying machine was to keep shipping features faster — a race it kept losing. The strategy flipped when reports emerged of Snapkit in the works, and the Snap Kit developer platform launched weeks later: instead of guarding the camera, login, Bitmoji, Stories and Snap Map inside Snapchat, Snap now licenses them into other apps.
This article frames that shift as the end of the 'camera company' era: embedding beats copying because a clone of a feature is worthless if the original ships as infrastructure everywhere. The same playbook later extended to AR, where Lens Cloud gave Snap's AR developers free backend services for multiuser, location-based experiences.
First-order effects
- Developers building third-party apps gain drop-in access to Snap's login, Bitmoji avatars, public Stories, Snap Map content and camera — making Snap an identity and media layer inside apps it doesn't own.
- Evan Spiegel converts Snap's most-cloned assets from defensive moats into distribution channels, directly attacking the clone dynamic that had defined the Meta–Snapchat rivalry.
Second-order effects
- 'Login with Snapchat' puts Snap head-to-head with Facebook Login for third-party sign-on, forcing Meta to compete for developer mindshare rather than simply replicate features.
- Every app that embeds Snap Kit deepens user lock-in to Bitmoji and Snap identity outside Snapchat itself, raising the cost for any rival to displace those assets.
Third-order effects
- If the embed-don't-copy logic holds, Snap's future bets — from the AR developer stack around Lens Cloud to the headset push detailed in the FT's reporting on Spiegel's revival effort — are platform plays first, consumer products second.
- The broader structural lesson for consumer social: when feature cloning is cheap, defensibility migrates from the app surface to SDKs, identity graphs and developer ecosystems — the territory Spiegel now calls distribution.
The trend: Consumer social apps under pressure from feature cloning are repositioning as platforms, licensing their signature capabilities into other apps to make distribution — not any single feature — the moat.