@pixelschubsi @adbenitez @delta
Right, that's a good point.

I remember, for example, that Matrix marks clients as Alpha/Beta/Stable (and Obsolete) in their list on matrix.org and allows to interactively filter by supported features.

By the way, as for the "features" filter. Afaik that's what Delta Chat wanted to avoid -- as stated previously, we want to be able to suggest a client that works well and supports all features consistently on all platforms.

And as for UI consistency. That doesn't mean we build a single cross-platform client, no. That's just, like, common UI concepts where it's applicable (e.g. we shouldn't bring swipes or other mobile gestures to desktop, obviously), a single translations source, same ordering of settings, of menu options, etc.

If we eventually create a list of clients with filters like on matrix.org, ig we can add "consistency" as a parameter?
Upd: consistency with what exactly? What is the reference ("official") implementation then?

But, on the other hand, if a developer wants their client to be consistent by features and UI across all (popular) platforms, but they don't build their own client for some of that platforms, then they have to work closely with Delta Chat team to get notified about new features, and…
that means they're a part of the team, but just working on a new client, not included in the "official list" before.

So. I think there should be a reference implementation anyway. Something which is like Element to Matrix. Well, a good reference implementation, which is the most used and most usable in the ecosystem, unlike Element.