2025 Q4 Release Recap ♥︎

As we kick off 2026, we wanted to take a moment to share our 2025 Quarter Four Release Recap, highlighting 8 of the most impactful improvements delivered for you in Q4, in case you missed them in the holiday season rush.

In Q4 2025, we focused on tightening the connection between design, delivery, and diagnostics. These changes build on earlier work across Insights, SDKs, and Action Flows, so you can move faster while trusting the behaviour and reporting of your in‑app experiences. Here’s our top eight:

1. Web SDK supports a new Modal stream container option Web SDK 25.3.0 offers a ready-made modal container mode savng your developers time and hassle when implementing the classic interruption-style modal experience for urgent and time-sensitive messages.

2. Web SDK now supports custom padding, extended filters & dropdown polish Web SDK 25.4.0 introduced new controls over card and element padding, and supports richer dropdown styling options and new content‑aware stream filters, letting you present cleaner, more on‑brand experiences while targeting cards based on what is actually inside them. This makes it easier to fine‑tune which customers see which messages, without extra data plumbing or bespoke UI work.

3. Compose SDK adds push notification analytics Android Jetpack Compose 25.3.1 now tracks when Atomic push notifications are received by the host app and emits a dedicated notification-received event. You gain clearer visibility into the difference between delivery and engagement, helping you refine your strategies with more confidence.

4. Compose SDK reaches first stable release With 25.3.0, the Android Jetpack Compose SDK graduated to its first stable release and became the recommended SDK for new Android integrations. It offers a modern foundation with text inputs, checkboxes, video, horizontal containers, and runtime variables, while the existing Android SDK remains in support mode for a smoother upgrade path.

5. Safer and more flexible send‑request handling in Action Flows Action Flow send‑request steps now support “acceptable response codes” and emit specific errors when no response is returned or when credentials are missing, instead of treating everything as a generic failure. Your integrations become more resilient and easier to troubleshoot when downstream services misbehave.

6. Inline credentials and faster Flow debugging You can now create credentials directly inside the Action Flow editor, and the graph automatically centres on steps with validation errors. Conditional steps surface script output and errors, and invalid scripts can no longer be saved, which significantly reduces time spent tracking down configuration issues.

7. Custom event listeners and scheduled triggers (GA) Custom event listener and scheduled trigger capabilities in Action Flows moved to general availability in Q4. You can confidently drive production‑grade journeys that react to in‑app behaviour or time‑based milestones, without relying on external schedulers or additional glue code.

8. Insights filters and timezone‑aware reporting A customer‑ID filter in Insights and improved timezone handling for “Last started/sent” metrics make it easier to answer “who saw this, and when?” directly in Atomic. This reduces the need for exports or external BI just to validate targeting and timing.

Alongside these headline improvements, Q4 also delivered better content‑level visibility in card automation steps and a series of smaller fixes and UI refinements across the Workbench and SDKs, making everyday building and operating smoother overall.

The 2025 Q4 Atomic.io Release Recap →

We’re well underway with the Q1 2026 roadmap, with exciting new Action Flow Experimentation and AI tools along with many ongoing improvements based on your feedback.

The full list of Q4 changes can be found in our changelog. If you’d like to explore how these features could support your workflows, contact our team.

We can't wait to showcase what's coming next quarter 👋