From f2c338aa96dffee9c06cc3f202ce2bf0ba83537d Mon Sep 17 00:00:00 2001 From: mARTin-B78 Date: Tue, 29 Sep 2026 14:41:26 +0200 Subject: [PATCH] docs: add TODO for a general UI/UX simplification pass on settings/config screens User's own comparison: VoiceStudio's integrations screen is cleaner than this app's Settings/Engines equivalent (880-line s-llms.html, 31+ fields all visible at once vs VoiceStudio's collapsed per-category model cards). Direction: progressive disclosure over one long flat form. Co-Authored-By: Claude Sonnet 5 --- TODO.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/TODO.md b/TODO.md index 8085c34..3bc3f04 100644 --- a/TODO.md +++ b/TODO.md @@ -249,6 +249,22 @@ Plivo/Telnyx) were in the same gap list but deliberately not picked -- leave tha anchor, casual conversational, storyteller) rather than trying to match VoiceStudio's exact catalog. Generate and store the demo clips once (not on every page load) and keep them small (the existing 24 kHz mono WAV convention). +- [ ] **General UI/UX simplification pass -- reduce how overwhelming this app's settings/ + configuration screens are.** User's own observation comparing live: VoiceStudio's + integrations screen (`http://192.168.178.8:3900/#/integrations`) is "way cleaner" than + this app's Settings/Engines equivalent. Concrete evidence for the gap: `s-llms.html` + ("Engines") is 880 lines with 31+ labelled fields all visible on one page at once, versus + VoiceStudio's per-category model cards (TTS/ASR/Dictation/Diarisation/Translation/LLM) + that each expand on demand -- see the `models.png` screenshot referenced in + `architecture/voicestudio-comparison.md`. Direction: progressive disclosure (group into + collapsed cards/categories, expand one at a time) instead of one long flat form; fewer + fields visible per step; a simpler default view with advanced options tucked behind a + toggle, mirroring the "Fast/Balanced/Quality/Max" tiering idea from the onboarding-wizard + item above rather than exposing every knob unconditionally. Not limited to Engines -- + once a pattern is settled there, audit Settings' other pages and any other dense + single-page form (Payloads, the magazine quality-run's settings, etc.) against it. Needs + its own before/after review with the user (screenshots or a walkthrough) since "simpler" + is a judgement call, not a number to hit. ### P0 — do first