what-about-design: rephrase

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2020-07-19 16:42:07 +02:00
parent dfb1c92164
commit 59e5a276eb
Signed by: pep
GPG key ID: DEDA74AEECA9D0F2

View file

@ -111,9 +111,9 @@ is, and how the experience for it should be, i.e., design. This process should
be applied across a set of implementations, using the same design guidelines and
ensuring interoperability.
In practice it is not enough if somebody using [Conversations] on the mobile
talks to somebody else using [Dino] on the desktop, even if they both follow
the Compliance Suites of year X and can then interop on a “basic” level (still
In practice it is not enough if somebody using [Conversations] on mobile talks
to somebody else using [Dino] on desktop, even if they both follow the
Compliance Suites of year X and can then interop on a “basic” level (still
pretty advanced to be honest), they have different design guidelines and there
will inevitably be areas where they differ and some features won't behave as
expected on the other side. The issue is not that there is no design