Remote in-app messaging
A backend-agnostic Flutter package for scheduling, targeting, and rendering in-app messages from remote JSON.
- Type
- Open source · Remote UX
- Role
- Creator and maintainer
- Period
- 2026 — Present
Evidence sequence
- 01View repository
- 02View on pub.dev
Public-safe record
The challenge
Product teams need to communicate inside an app without coupling every campaign or operational message to a new mobile release or one backend provider.
My contribution
I designed a host-agnostic package with configurable layouts, event triggers, audience rules, sticky A/B variants, frequency limits, scheduling, and safe kill-switch controls.
The outcome
Teams can drive consistent in-app experiences from remote configuration while retaining control over rendering, targeting, fallback behavior, and provider choice.
How I approached it
The public API keeps the package independent from Firebase In-App Messaging. A team can use Remote Config, another backend, or local JSON while injecting its own image handling and host actions.
Documentation covers setup, triggers, schema, targeting, frequency, styling, and the public API so the system remains understandable beyond its source code.