Building Postly: What a Green Connection Badge Should Promise

I noticed a connection card in Postly that said two accounts were connected. Both had expired. The card was green.

That small detail led to a useful product decision. We were showing that accounts had been saved. Someone preparing a post needed to know whether those accounts were ready to use.

I’m building Postly to help people plan and publish their content. The goal behind this work is a clearer customer experience: helping people understand whether they can proceed and what needs their attention. That is part of product excellence for me. A reassuring status has to earn its place in that workflow. If a person needs to reconnect an account, the product should make that clear before they depend on it.

Start with the decision someone needs to make

The question behind a connection count is simple: can I use these accounts, or is there something I need to fix?

I asked for the display to separate active accounts from accounts needing attention. In the case I reviewed, the useful message was “0 active · 2 need attention.” An expired account should also have a visible Reconnect action. The person should be able to see the problem and the next step together.

We also separated the color of the status badge from the surrounding card. The card stays neutral. The badge uses green when all connections are healthy, amber for mixed or unverified states, and stronger amber when none are active and reconnection is needed. The words carry the meaning alongside the color.

A correction has to follow the workflow

Changing one card would have left the same ambiguity elsewhere. We carried the health labels into the dashboard and the account picker used when choosing publishing destinations. An account whose status has not been verified should say so.

That matters because people move through a product. A warning on one screen loses value if the next screen makes the same account look ready again.

The implementation and focused tests are complete, and the changes have been pushed to the main code branch. I haven’t yet verified the production rollout or measured whether this reduces failed publishing attempts or support requests.

The founder lesson I’m keeping

It is easy to spend a product review discussing features and miss the promise made by a small label.

The question I’m taking into product reviews is simple: what will someone reasonably believe after reading this?

If a badge says connected, ready, saved, or published, I want its meaning to match the action the person is about to take. Where something needs attention, I want the recovery step close by.

This is part of building Postly in public: sharing the small decisions behind a more useful publishing workspace, along with what we have and haven’t verified. The aim is to make connection status more honest and the next action easier to find.

Explore Postly for planning and publishing your content.