I’m sharing OpenClix, an open source toolkit for running mobile engagement and retention flows directly inside your app.

The motivation came from repeatedly seeing the same pattern when teams try to improve retention. They end up stitching together push providers, experimentation tools, analytics pipelines, and backend services just to ship simple onboarding nudges or re engagement reminders. The setup becomes complex very quickly.

OpenClix takes a different approach.

Instead of a hosted platform or heavy SDK, it provides config driven engagement logic that runs on device. Campaigns and rules live in a simple JSON config and react to app events locally. You can trigger notifications, schedule follow ups, or suppress messages based on user behavior without needing a backend control plane.

A few core ideas behind the project:

• Local first execution. Engagement logic runs on the device, which removes a lot of infrastructure and latency. • Source vendoring instead of SDK lock in. The code can live directly in your repo so you can inspect and modify it. • Config driven campaigns. Triggers, guardrails, and messaging logic are defined in a simple config file. • Agent friendly workflows. The project is structured so coding agents can safely generate and modify campaigns or rules.

Typical things people use it for:

• onboarding nudges • streak or habit reminders • re engagement after inactivity • retention experiments without a full growth stack

I’d love feedback on a few things:

• Does the local first approach make sense for engagement logic? • What types of campaigns would you want to run this way? • What analytics or integrations would make this more useful?

Happy to answer questions and discuss how others handle retention tooling today.