Package-level declarations
Types
The avatar/banner upload lifecycle, surfaced on the profile so each phase gets its own feedback: a spinner while Compressing or Uploading, an error indicator on Error, and the normal edit affordance when Idle.
Bundles the pieces Navigation 3's shared-element transition between PostCard and PostDetailScreen needs: the enclosing SharedTransitionScope and the per-entry AnimatedVisibilityScope that scopes the transition's enter/exit animation. Nullable and optional everywhere it's consumed, so @Previews and designsheet call sites - which have neither a SharedTransitionLayout nor an AnimatedVisibilityScope available - keep compiling unchanged by simply omitting it.
The button on a StatusPrompt that recovers from the state the prompt describes.
Properties
Fixed shared-element key: only ever one current-user avatar on screen at a time.
Fixed shared-element key: only ever one current-user banner on screen at a time.
True while work is in flight — taps are blocked and a loading indicator is shown.
Functions
Circular avatar with a small photo-camera badge overlaid bottom-end. Tapping the avatar itself (when not uploading) opens a full-screen viewer via onAvatarClick; tapping the badge opens the image picker directly via onEditClick - two separate tap targets, matching the common "tap to view, tap the pencil/camera to change" pattern.
Full-width banner. Tapping the banner itself (when not uploading) opens a full-screen viewer via onBannerClick; a small photo-camera badge opens the picker directly via onEditClick.
Announces topics newly discovered by the catalogue sync (see TopicsRepository.pendingNewTopics). Purely informational — new topics start unfollowed; the user adds them from Account → Interests.
The feed's primary story card: a hero image, a topic pill and reading-time estimate, the headline, a Markdown summary, an attributed source line, and a bookmark / read-source action bar. Stateless - bookmark and read-source intents are pushed up via onBookmarkClick and onReadSourceClick, and tapping the card body surfaces onCardClick (used for the shared-element transition into PostDetailScreen). When sharedTransition is supplied, the hero image and the headline are shared elements that animate into their counterparts on the detail screen.
The detail pane on wide layouts before the reader has picked a story.
Full-page view of a single Post, sharing the story-card visual language of PostCard (topic pill, reading-time, attributed source, action bar) so navigating between them feels continuous. Unlike PostCard, its markdown body is not height-capped - the whole point of a dedicated detail page is that content isn't truncated. When sharedTransition is supplied, the hero image and the headline animate in from their counterparts on the originating card.
A compact saved-story row for the bookmarks list: a thumbnail, the headline, and a topic/source line, with an optional remove action. Stateless - taps surface via onClick and onRemoveClick.
A peeking-card browser: the current card is large and centered, with the next card's edge peeking in from the direction of orientation's scroll axis. The main Feed peeks vertically (next card below); collection/source browsing peeks horizontally (next card to the side) — both patterns are from the reference video.
The one composition for every terminal state in the app - empty, error, signed-out, nothing-selected: an icon inside a tonal circle, a title, a short explanation, and an optional button that gets the user out of the state.
Stable per-topic tint: the same topic always maps to the same hue, on every platform (Kotlin's String.hashCode algorithm is identical across targets). Used by the placeholder below; exposed so other surfaces (chips, charts) can adopt the same coding later.
A topic chip with nothing to tap, for listing topics rather than filtering by them — the account screen shows what the user follows and has nowhere to send a tap.
A topic rendered as a chip — the single way Skimbyte draws one. The feed's TopicFilterRow and the account screen's followed-topics list both come through here, so a topic looks and is announced the same way wherever it appears.
Branded stand-in for a story image: a topic-tinted gradient with the topic's initial. Rendered underneath coil3.compose.AsyncImage wherever story images appear, so the loading state, a failed fetch, and a post with no image all look intentional instead of leaving a flat dark void (which reads as broken).