Skip to content

Release notes

Public release notes.

A short, concrete and non-technical version of visible changes in the Omni Posto experience.

Public notes

What changes, why it helps, what you can do more easily.

Each product area is summarized with observable benefits, without build details or exploitable information.

Product areas

Improvements grouped by use.

The notes stay focused on what users see, understand and can do more simply.

Media

What changes

Preparing images and videos becomes easier to read, with previews and thumbnails that are simpler to follow.

Why it helps

You keep a better view of what is ready to publish and what still needs a check.

Easier to do

  • Import several media items without losing the flow of preparation.
  • Compare previews before choosing the right content.

Publishing

What changes

Publishing choices are presented more clearly before confirmation, with better context about the chosen destination.

Why it helps

You can review the content, platform and readiness more easily before confirming.

Easier to do

  • Quickly verify where a piece of content will be published.
  • Adjust a choice without losing the logic of the journey.

Follow-up

What changes

Feedback after publishing is easier to read, with clearer markers around visible results.

Why it helps

You understand faster what is published, what is ready and what deserves another action.

Easier to do

  • Spot a publication that has already been sent.
  • Find a published result without searching through several screens.

Account and access

What changes

Account and access screens give more direct messages during important steps.

Why it helps

You know better what is expected when you confirm, resume or finish an action.

Easier to do

  • Understand why an account step appears.
  • Return to the workspace path with less hesitation.

Interface

What changes

Screens become more consistent, with steadier wording and blocks that are easier to scan.

Why it helps

You spend less time interpreting pages and more time preparing publications.

Easier to do

  • Scan the most important information first.
  • Move from one product area to another with more stable markers.

Public level

The level of detail remains deliberately public.

These notes only describe visible product benefits. They do not list build changes or provide exploitable indications.

Readable by everyone

Notes made for quick understanding.

They provide enough information to know what improves, without turning the page into a build journal.

Product context

Read the more narrative version.

The devblog explains the same improvements with more user context.