From d9b5198cd348a04c785bcdcfd1df293df17f55a7 Mon Sep 17 00:00:00 2001 From: Krille Fear Date: Thu, 30 Dec 2021 09:10:47 +0000 Subject: [PATCH] Update FluffyChat Design Guidelines --- FluffyChat-Design-Guidelines.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/FluffyChat-Design-Guidelines.md b/FluffyChat-Design-Guidelines.md index 4ce2c8c..8ab0ea5 100644 --- a/FluffyChat-Design-Guidelines.md +++ b/FluffyChat-Design-Guidelines.md @@ -6,15 +6,15 @@ To decide which feature makes sense in FluffyChat and which would be config bloa 1. FluffyChats code base should be as minimal as possible so we have a maintainable state. 2. We should not implement features which is the job of the OS. For example this includes: -2.1. Emoji-picker -2.2. Font selector -2.3. Theme switcher (Currently implemented but might be removed in the future) +- Emoji-picker +- Font selector +- Theme switcher (Currently implemented but might be removed in the future) 3. We should avoid implementing features which are hard to test. 4. We always have non-techy users as our prime target group in mind. 5. Therefore should avoid implementing configuration options, which could lead to security issues. For example this includes: -5.1. A switch to start a non-encrypted room. This could be clicked accidentally and lead to a fully unencrypted conversation. +- A switch to start a non-encrypted room. This could be clicked accidentally and lead to a fully unencrypted conversation. 6. We should always try to improve the accessibility of the app. 7. We should avoid implementing configuration options, which could lead to a bad UX as long as it does not help with the accessibility. For example this could be: -7.1. Let the user change every single color of the app (Like in KDE :-P). +- Let the user change every single color of the app (Like in KDE :-P). More guidelines will follow later... \ No newline at end of file