mirror of
https://github.com/FluxaMedia/fluxa.git
synced 2026-08-06 08:48:51 +00:00
Detail screen fixes from review: - Resume button content is now actually centered (outer Column lacked horizontalAlignment). - Download buttons (primary + per-episode) get a download icon. - Season selector is now a visible pill with a dropdown-arrow icon instead of plain unstyled text, and opens a ModalBottomSheet listing seasons instead of an inline expand - easier to tell it's tappable and consistent with the "bottom sheet, not dropdown" request. - Episode thumbnails are bigger (was fixed 120dp, now split evenly with the text column) and synopsis moved to a full-width line below the thumbnail+title row instead of being squeezed into the narrow text column beside the thumbnail. - Hero renders the title logo (MetaDetail.logo, now exposed as DetailUiModel.logoUrl... already existed, just unused) when available, falling back to text title otherwise. Home hero: same logo-over-text treatment, plus an age-rating badge, season count, and a description line - all sourced from Meta fields (description/ageRating/seasonsCount) that were already fetched but not exposed on CatalogItemUiModel before now. Screen transitions: FluxaApp's main content switch (destination changes, opening/closing Detail, entering profile edit) was an instant when-block swap with zero animation. Wrapped it in AnimatedContent keyed on a computed screen identity, with a fade+scale enter and fade exit - the "no animation when navigating" gap. Per-screen composables switched from Modifier.weight(1f) (needs ColumnScope, no longer valid once nested inside AnimatedContent's content lambda) to Modifier.fillMaxSize(), with weight(1f) moved to the AnimatedContent itself. Not addressed, scoped out: HBO Max's top bar (app logo, notification bell, profile avatar) and category tab row (Home/Series/Movies/...) on the Home screen reference image - Fluxa's Home has no matching data model (no per-category content-type filter, no notification system) and the existing bottom FluxaNavigationBar already serves destination-switching, so adding a duplicate top tab row felt like UI without backing functionality rather than a real gap. Compile-verified on shared commonMain, iosMain, and both Android flavors. Visual result unverified - no way to render Compose UI in this environment. |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle.kts | ||