shahondin1624/ShadowrunCharSheet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Auto-save has no progress indicator and hard-coded 500ms debounce #107

New Issue
Closed
opened 2026-04-04 18:42:40 +02:00 by shahondin1624 · 0 comments
shahondin1624 commented 2026-04-04 18:42:40 +02:00
Owner
Copy Link
Copy Source

Description

The auto-save system uses a hardcoded 500ms debounce with no visual indicator of save status. Users don't know if their data is saved, saving, or failed. On slow devices, the debounce might be too aggressive. If the user closes the app during a save, data loss is possible.

Files

  • sharedUI/src/commonMain/kotlin/org/shahondin1624/viewmodel/CharacterViewModel.kt (line 94)

Expected Behavior

  • Visual save status indicator (saved/saving/error)
  • Configurable or adaptive debounce timing
  • Ensure save completes before app exit when possible

Acceptance Criteria

  • Save status indicator visible to user (e.g., subtle icon in toolbar)
  • "Saving..." state shown during active save
  • "Saved" confirmation shown briefly after successful save
  • Error state shown if save fails
  • App attempts to complete pending saves on exit
## Description The auto-save system uses a hardcoded 500ms debounce with no visual indicator of save status. Users don't know if their data is saved, saving, or failed. On slow devices, the debounce might be too aggressive. If the user closes the app during a save, data loss is possible. ## Files - `sharedUI/src/commonMain/kotlin/org/shahondin1624/viewmodel/CharacterViewModel.kt` (line 94) ## Expected Behavior - Visual save status indicator (saved/saving/error) - Configurable or adaptive debounce timing - Ensure save completes before app exit when possible ## Acceptance Criteria - [ ] Save status indicator visible to user (e.g., subtle icon in toolbar) - [ ] "Saving..." state shown during active save - [ ] "Saved" confirmation shown briefly after successful save - [ ] Error state shown if save fails - [ ] App attempts to complete pending saves on exit
shahondin1624 added the priority:should-havetype:architecture labels 2026-04-04 18:42:40 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
epic:cards-rework
Epic: Attribute & Talent cards rework
 epic:character-creation
Epic: Character creation & build points
 epic:character-display
Epic: Character info display
 epic:character-management
Epic: Character management (editing, persistence)
 epic:combat
Epic: Combat & Initiative
 epic:cyberware
Epic: Cyberware/Bioware system
 epic:dice-rolling
Epic: Dice rolling UX
 epic:gear
Epic: Gear, Equipment & Vehicles
 epic:magic
Epic: Spells & Adept Powers
 epic:navigation
Epic: Navigation & page structure
 epic:responsive-layout
Epic: Responsive layout foundation
 epic:testing
Epic: Automated UI testing
 priority:must-have
Priority: Must-have for MVP
 priority:nice-to-have
Priority: Nice-to-have, polish and extras
 priority:should-have
Priority: Should-have, important but not blocking
 type:architecture
Architecture/infrastructure concern
 type:bug
Bug or code defect
 type:feature
New feature request
 type:usability
UX/usability improvement
No Label priority:should-have type:architecture
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shahondin1624
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shahondin1624/ShadowrunCharSheet#107
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?