From 0fa667eebd30f3891fe52b97f4f38e8d41aa74a2 Mon Sep 17 00:00:00 2001 From: Jonathan Rainville Date: Thu, 12 Jun 2025 11:07:51 -0400 Subject: [PATCH] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Lukáš Tinkl Co-authored-by: Noelia <97019400+noeliaSD@users.noreply.github.com> --- docs/FURPS/tablet-build.md | 2 +- docs/FURPS/ui-modularization.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/FURPS/tablet-build.md b/docs/FURPS/tablet-build.md index 76929f242d..1fadb7015c 100644 --- a/docs/FURPS/tablet-build.md +++ b/docs/FURPS/tablet-build.md @@ -1,4 +1,4 @@ -# Table Build FURPS ([#17941](https://github.com/status-im/status-desktop/issues/17941)) +# Tablet Build FURPS ([#17941](https://github.com/status-im/status-desktop/issues/17941)) ## Functionality - Partial feature parity with desktop app expected - no keycard, biometrics and dapps. To be added later. diff --git a/docs/FURPS/ui-modularization.md b/docs/FURPS/ui-modularization.md index 333094e6ac..d1e459f41c 100644 --- a/docs/FURPS/ui-modularization.md +++ b/docs/FURPS/ui-modularization.md @@ -11,14 +11,14 @@ - Document architectural patterns and usage conventions to reduce ambiguity during development. ## Reliability -- Reduce tight coupling between backend logic and UI to minimize bugs from implementation side effects. +- Reduce tight coupling between business logic and UI to minimize bugs from implementation side effects. - Ensure predictable data flow with read-only modules and strictly typed store usage. - Safeguard against improper store usage with guidelines on instantiation and component scope. ## Performance - Avoid unnecessary data duplication and propagation through read-only modules and centralized ground truth state. - Minimize transformation overhead by using adaptors only when necessary for UI display logic. -- Ensure UI responsiveness by decoupling backend processing from rendering logic. +- Ensure UI responsiveness by decoupling business logic processing from rendering logic. ## Supportability - Use strictly typed interfaces (`no var`) to catch issues at compile time and improve tooling support.