Skip to content

feat: resolve #25 - improve downloader UI accuracy and ergonomics#26

Open
KenjiBaheux wants to merge 2 commits intoonderceylan:mainfrom
KenjiBaheux:main
Open

feat: resolve #25 - improve downloader UI accuracy and ergonomics#26
KenjiBaheux wants to merge 2 commits intoonderceylan:mainfrom
KenjiBaheux:main

Conversation

@KenjiBaheux
Copy link

Overview

This PR addresses the user confusion regarding the 22GB storage requirement (Ref: Issue #25) and proposes improvement to the model initialization experience. It shifts the messaging from "22GB download" to a more accurate "system health requirement" while providing real-time feedback on which requirements are met.

Changes

UI & UX Enhancements

  • Dynamic System Checks: Replaced static text with a live "System Check" list. It now detects if the Chrome flag is enabled and uses the Storage Manager API to check for available disk space. That said, the availability() API should already take this into consideration.
  • Storage Clarification: Explicitly decoupled the 22GB system margin requirement from the actual ~2GB model download to prevent user drop-off.
  • Indeterminate Progress States: Updated the progress bar to pulse (indeterminate state) during "Checking" and "Extracting" phases. This provides immediate visual feedback even when the download percentage is at 0%. This is a bit hard to test but I hope I got it right.
  • Streamlined Requirements: Reordered compatibility items to lead with "low-friction" requirements (pre-requisites), moving the technical flag toggle to the end of the list.
  • Integrated Copy Helper: Added a "hover-to-reveal" copy icon for the chrome://flags link to reduce manual effort for the user.

Related Issues

Fixes #25

- Redesign requirements list with dynamic system checks (Flag, Storage).
- Add indeterminate progress bar state to fix "0% freeze" perception.
- Implement hover-to-copy interaction for chrome://flags.
- Reorder requirements to minimize premature abandonment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Discrepancy on model size

1 participant