At Atomic.io we developed a user segmentation feature. In this blog post we’ll delve into a few interesting aspects of the feature’s implementation and how we use property based testing to ensure we have excellent test coverage across our duration-based filter criteria.

An upgrade to the Atomic workbench’s insights screen has been a long time coming, and it is finally here. We have entirely replaced the backend system used by the dashboard to ensure stability, timely results, and our own ability to extend and adapt the dashboard to the growing needs of our customers.

After identifying the need to have an in-app messaging channel, demonstrating ROI to internal budget holders and decision makers is a necessary and responsible step.

The latest feature added to Atomic’s extensive tool set is the “File Upload” element that can be added to a card. This new card input allows you to send cards asking your users to upload an existing image or take a new one - prompted by the Atomic card.

Sooner or later something in your product or service will break - how you respond matters.

Your team should communicate with customers in the channels you own. With Atomic you can meet your customers where they already are: inside your apps.

Whether it's quickly reaching out to customers to confirm suspicious transactions or requesting critical CDD documents, secure in-app messaging gives your compliance team the tools they need to act quickly and efficiently.

How we communicate with our team is as import how we communicate with our customers. A few refreshing ideas to reframe and improve how we do it.