15:I[981,["658","static/chunks/658-a698693f56d0116a.js","183","static/chunks/183-6beeeb801c274aaa.js","474","static/chunks/app/%5Btype%5D/layout-631c4730b83c8223.js"],"Posts"] 16:T718,Hi HN,

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.17:T4be,I built a small browser puzzle game:

We open sourced a rite of passage for the permanent underclass problem

Impressions from Mozilla 1.2B (2002)

When is AI coming to CAD design?

Separation of direct and globalscvene components using HF illumination

Learnings from Building an AI Root Cause Analysis Agent

An Open Source SDK and Runtime for Building Agents

Apple Blocks US Users from Downloading ByteDance's Chinese Apps

Unstract: Open-source platform to ship document extraction APIs in minutes

Meta's Renewed Commitment to Jemalloc

Ignoring the Wisdom of Crowds

If photons have no mass, how can they have momentum?

Uber is letting women avoid male drivers and riders in the US

Deterministic metrics for requirements quality (IEEE 830, no LLM)

Show HN: MessyData – Synthetic dirty data generator

Tanker War

Helix 02 Living Room Tidy [video]

Un hack me now mate

Show HN: The Mog Programming Language

Show HN: OpenClix, Agent friendly, open-source retention tooling

eInk wall remote for HomeAssistant – fed up with tablets and hacked Kindles

Show HN: DocTracker – track client documents and send reminders

Models have some pretty funny attractor states

Show HN: We built an MCP server so LLMs can self-correct against business rules

Seldom: An Anonymity Network with Selective Deanonymization

Use /loop to run Claude Code on a Schedule

AI agents are coming for government. How one big city is letting them in

The Government Told Courts It Could Easily Refund Tariffs. Now It Says It Can't

How to Track Competitor Pricing Changes Automatically

Canadian employment trends in the era of generative artificial intelligence

Show HN: A daily arithmetic puzzle with a hidden Hard Mode