meldestelle/docs/06_Frontend
2026-04-02 22:29:21 +02:00
..
ErgebnisMaske Refactor Veranstalter and Veranstaltung flows: add VeranstalterProfil UI, event creation callback, profile enhancements, and save-enable matrix logic. Extend ZNS import and branding workflows. 2026-04-01 02:51:02 +02:00
FIGMA Implement Veranstalter and Veranstaltung management: Add VeranstalterDetailScreen, seed FakeVeranstaltungStore, and enable deletion of Veranstaltungen. Extend onboarding with device name validation. Refine UI for VeranstalterKonfigScreen, add InvalidContextNotice, and centralize navigation checks. 2026-03-28 01:37:32 +01:00
Logs infra: clean up Keycloak configuration, enforce consistency in .env, and improve health checks 2026-03-06 11:23:24 +01:00
Nennmaske Refactor Veranstalter and Veranstaltung flows: add VeranstalterProfil UI, event creation callback, profile enhancements, and save-enable matrix logic. Extend ZNS import and branding workflows. 2026-04-01 02:51:02 +02:00
Reports Migrate frontend navigation to V3: archive Navigation V2, implement updated screen-tree and back-stack rules, and adapt documentation for startable MVP flow. 2026-04-02 20:09:26 +02:00
Screenshots Implement Veranstalter and Veranstaltung management: Add VeranstalterDetailScreen, seed FakeVeranstaltungStore, and enable deletion of Veranstaltungen. Extend onboarding with device name validation. Refine UI for VeranstalterKonfigScreen, add InvalidContextNotice, and centralize navigation checks. 2026-03-28 01:37:32 +01:00
StartErgListen Add documentation and templates for Start-/Ergebnislisten v07: Introduce foundational templates, print styles and partials, and consolidate related session notes. 2026-03-30 22:55:51 +02:00
ARCHITECTURE_RULES.md chore: remove obsolete screens from meldestelle-desktop module 2026-03-26 15:09:44 +01:00
feature-implementation-guide.md refactor(ping-feature): integrate DI refactor, enhance web build, and update feature workflow 2026-01-17 12:05:34 +01:00
flow-fehler.png Refactor Veranstalter and Veranstaltung flows: add VeranstalterProfil UI, event creation callback, profile enhancements, and save-enable matrix logic. Extend ZNS import and branding workflows. 2026-04-01 02:51:02 +02:00
flow-wechsel.png Refactor Veranstalter and Veranstaltung flows: add VeranstalterProfil UI, event creation callback, profile enhancements, and save-enable matrix logic. Extend ZNS import and branding workflows. 2026-04-01 02:51:02 +02:00
MVVM_UDF_Pattern.md Implement MVVM + UDF: Add BewerbAnlegenViewModel, VeranstalterViewModel, and state management for Veranstalter and Bewerb workflows. Refactor existing Composables to use ViewModels and intents. Update Turnier UI for Bewerb creation with mandatory division logic, and add documentation for MVVM patterns and guidelines. Mark A-1 and A-2 as complete in the roadmap. 2026-04-02 22:29:21 +02:00
Navigation_Routing_Diagramm.md Migrate frontend navigation to V3: archive Navigation V2, implement updated screen-tree and back-stack rules, and adapt documentation for startable MVP flow. 2026-04-02 20:09:26 +02:00
Navigation_V2_Screen-Baum_und_Back-Stack.md Migrate frontend navigation to V3: archive Navigation V2, implement updated screen-tree and back-stack rules, and adapt documentation for startable MVP flow. 2026-04-02 20:09:26 +02:00
Navigation_V3_Screen-Baum_und_Back-Stack.md Migrate frontend navigation to V3: archive Navigation V2, implement updated screen-tree and back-stack rules, and adapt documentation for startable MVP flow. 2026-04-02 20:09:26 +02:00
offline-first-architecture.md chore: archive outdated architecture and roadmap documents, normalize documentation structure and metadata 2026-03-15 20:00:51 +01:00
README.md docs: add state-management strategy reference and SQLDelight session log 2026-01-28 13:00:55 +01:00
screen-flow_1-04-26.md feat(management-feature): add centralized administration screens and back-navigation support 2026-04-01 17:26:44 +02:00
state-management-strategy.md docs: add state-management strategy reference and SQLDelight session log 2026-01-28 13:00:55 +01:00
Teststrategie_Desktop.md Mark A-1 as complete: Add detailed QA Test-Strategie for Compose Desktop App, including test pyramid, tooling, conventions, and CI/CD integration; link roadmap and strategy documents. 2026-04-02 18:46:40 +02:00
uebersicht-v01.png feat(management-feature): add centralized administration screens and back-navigation support 2026-04-01 17:26:44 +02:00
uebersicht-v02.png feat(management-feature): add centralized administration screens and back-navigation support 2026-04-01 17:26:44 +02:00
Veranstalter-Card-v01.png Enhance Veranstalter and Veranstaltung flows: add confirm dialog for event creation, refine navigation logic, and improve onboarding with keyboard focus handling. 2026-04-02 00:41:29 +02:00
Veranstalter-Profil-Card-v01.png Enhance Veranstalter and Veranstaltung flows: add confirm dialog for event creation, refine navigation logic, and improve onboarding with keyboard focus handling. 2026-04-02 00:41:29 +02:00
verlauf-neueVeranstaltungTurnier-anlegen.png Refactor Veranstalter and Veranstaltung flows: add VeranstalterProfil UI, event creation callback, profile enhancements, and save-enable matrix logic. Extend ZNS import and branding workflows. 2026-04-01 02:51:02 +02:00
verwaltung_01-04-26.png feat(management-feature): add centralized administration screens and back-navigation support 2026-04-01 17:26:44 +02:00
web-setup.md chore: archive outdated architecture and roadmap documents, normalize documentation structure and metadata 2026-03-15 20:00:51 +01:00

type status owner last_update
Reference ACTIVE Frontend Expert 2026-01-15

Frontend-Architektur "Meldestelle Portal"

Dieses Verzeichnis dokumentiert die Architektur und die technischen Details des KMP-Frontends "Meldestelle Portal".

Übersicht

Das Frontend ist eine Kotlin Multiplatform (KMP)-Anwendung, die für die folgenden Ziele entwickelt wird:

  • Desktop (JVM): Eine eigenständige Desktop-Anwendung.
  • Web (JS/Wasm): Eine moderne Web-Anwendung, die im Browser läuft.

Die Architektur ist auf Offline-Fähigkeit und eine reaktive UI ausgelegt.

Modul-Struktur

Das frontend-Verzeichnis ist wie folgt strukturiert, um eine klare Trennung der Verantwortlichkeiten zu gewährleisten:

  • shells/: Die ausführbaren Anwendungen (Assembler-Module), die die App für eine bestimmte Plattform (Desktop, Web) zusammenbauen.
  • features/: Vertikale Slices der Anwendung. Jedes Feature-Modul kapselt eine bestimmte Funktionalität (z.B. auth-feature, ping-feature). Wichtig: Ein Feature-Modul darf niemals von einem anderen Feature-Modul abhängen.
  • core/: Gemeinsame Basis-Module, die von allen Features genutzt werden. Dazu gehören:
    • design-system/: Compose-Komponenten, Themes, Farben.
    • domain/: Fachliche Kernlogik und Datenmodelle des Frontends.
    • local-db/: SQLDelight-Datenbank-Setup und Queries.
    • navigation/: Navigations-Logik und Routen-Definitionen.
    • network/: Ktor-Client und API-Definitionen.

Kerntechnologien

  • UI: Compose Multiplatform für eine deklarative, plattformübergreifende UI.
  • Persistenz (Offline-First): SQLDelight für die lokale Speicherung von Daten.
  • State Management: Kotlin Coroutines und Flow in Kombination mit ViewModels.
  • Dependency Injection: Koin für die lose Kopplung von Komponenten.
  • Netzwerk: Ktor Client für die Kommunikation mit dem Backend.

Wichtige Dokumente