From 59e5a276ebfabffcea4a13b453c5510debe77086 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Maxime=20=E2=80=9Cpep=E2=80=9D=20Buquet?= Date: Sun, 19 Jul 2020 16:42:07 +0200 Subject: [PATCH] what-about-design: rephrase MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Maxime “pep” Buquet --- content/posts/what-about-design.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/posts/what-about-design.md b/content/posts/what-about-design.md index 8c85867..cf3f2b2 100644 --- a/content/posts/what-about-design.md +++ b/content/posts/what-about-design.md @@ -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