Make the UI feel natural on phones by increasing combatant row height, tap target sizes, font sizes, and spacing on mobile. All features remain accessible — nothing is hidden, only resized for comfortable finger interaction. Includes safe area inset handling for notched devices.
Acceptance Criteria
Combatant rows use moderately increased padding and font sizes on phones (<640px), remaining single-line and fitting at least 8 rows on screen without scrolling
All interactive elements (condition tags, HP/AC/initiative values, rename/delete/add buttons) have a minimum 44px tap target on touch devices
Input fields use at least 16px font size on mobile to prevent iOS Safari auto-zoom
The action bar's custom stat fields (Init/AC/MaxHP) wrap gracefully on narrow screens instead of overflowing
Condition picker and HP popover are comfortably sized for finger interaction on phones
Safe area insets are respected — bottom bar has padding for iPhone home indicator, content avoids notch areas
All features remain accessible on mobile — no functionality is hidden or removed, only resized
Desktop layout (>=640px) is unchanged
## Summary
Make the UI feel natural on phones by increasing combatant row height, tap target sizes, font sizes, and spacing on mobile. All features remain accessible — nothing is hidden, only resized for comfortable finger interaction. Includes safe area inset handling for notched devices.
## Acceptance Criteria
- [ ] Combatant rows use moderately increased padding and font sizes on phones (<640px), remaining single-line and fitting at least 8 rows on screen without scrolling
- [ ] All interactive elements (condition tags, HP/AC/initiative values, rename/delete/add buttons) have a minimum 44px tap target on touch devices
- [ ] Input fields use at least 16px font size on mobile to prevent iOS Safari auto-zoom
- [ ] The action bar's custom stat fields (Init/AC/MaxHP) wrap gracefully on narrow screens instead of overflowing
- [ ] Condition picker and HP popover are comfortably sized for finger interaction on phones
- [ ] Safe area insets are respected — bottom bar has padding for iPhone home indicator, content avoids notch areas
- [ ] All features remain accessible on mobile — no functionality is hidden or removed, only resized
- [ ] Desktop layout (>=640px) is unchanged
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Make the UI feel natural on phones by increasing combatant row height, tap target sizes, font sizes, and spacing on mobile. All features remain accessible — nothing is hidden, only resized for comfortable finger interaction. Includes safe area inset handling for notched devices.
Acceptance Criteria