OpenClix

David Parrelli, Taimur Haider, Minyong Lee, Alan Cho, Jace Yoo, and Jihoon Seo looked at the mobile engagement space—think Braze, Amplitude, the whole gang—and said "nah, that's way too complicated for indie builders." So they built OpenClix, an open-source, local-first retention engine that runs entirely on-device with zero backend dependencies, zero control planes, and zero vendor lock-in. It's literally just config-driven JSON that your app reads. That's it. No API keys, no proprietary SDKs, no 6-month implementation timeline. They vendored the source directly into your repo so you own every line.

Here's the wild part—OpenClix is built for AI agents. The folder structure is legible, the interfaces are explicit, and there are clear edit points where an AI can safely modify engagement rules without breaking everything. They call it "agent-first" and they're not joking. You can literally have your AI teammate read, tweak, and deploy retention flows on its own. For indie devs who don't have a growth team, that's not a luxury—that's the only way to compete with teams that have 20 people doing nothing but push notifications.

The mobile engagement market is dominated by platforms that want to own your entire stack. OpenClix said "actually, we'll pass" and built the anti-platform platform. MIT licensed, fully auditable, forkable, and yours. Retention tooling should be simple, open, and fully yours—that's their belief, and they backed it with code. If you're building a mobile app and you're tired of feeding the engagement industrial complex, OpenClix is your way out.