Skip to content

feat(phone): weight text size preference for weight-selection surfaces (#1367) - #1399

Merged
9thLevelSoftware merged 6 commits into
mainfrom
feat/1367-weight-text-size
Nov 18, 2026
Merged

9thLevelSoftware merged 6 commits into
mainfrom
feat/1367-weight-text-size

Conversation

@9thLevelSoftware

@9thLevelSoftware 9thLevelSoftware commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

Weight text size for weight-selection surfaces (issue #1367)

Fixes #1367 — larger weight-selection text for older-adult / low-vision trainees. The stop-button request (#1366) is a separate ticket and is not included here. The feature is developed voluntarily at no charge.

What ships

A device-local, global Settings → Appearance → Weight text size preference (Standard / Large / Extra large, nominal 1 / 1.5 / 2) placed after Theme and before Dynamic color, that enlarges weight values on the safety-critical weight surfaces:

  1. Set Ready weight slider (SetReadyScreen)
  2. Routine Overview weight slider (RoutineOverviewScreen)
  3. Rest Timer weight slider (RestTimerCard) — per integration-model Correction 1
  4. Workout HUD bottom-bar readout — numeric weight, Echo Adaptive, and bodyweight No machine load (both value branches; supporting labelSmall labels stay unscaled)
  5. WeightStepper numeric value in exercise setup/edit

Explicitly unchanged (signoff Option B / SD4): Just Lift selection cards, CompactNumberPicker, shouldStackWeightCards. Also unchanged: rep sliders (5 call sites stay byte-identical in behavior), secondary weight displays, units/rounding/BLE/saved data (presentation-only, SD12), tvOS, backup/portal/SQLDelight schemas.

Binding design decisions (signoff corrections 1–7)

  • SD1 rendered cap: style multiplier M = E/O with effective rendered scale E = min(A×O, 2) (WEIGHT_TEXT_MAX_EFFECTIVE_SCALE = 2.0f), applied to fontSize and explicit sp lineHeight (SD3). Compose applies the OS scale exactly once, so rendered size is base × E, physically capped at 2× base. Every layout decision uses E, never A/M. Invalid/nonpositive/nonfinite inputs degrade to 1.0. The Android ceiling is proven through the real platform density converter (TypedValue.applyDimension) incl. nonlinear large-font scaledDensity — with a negative control proving the test catches the uncapped ×A regression.
  • SD2 Standard-above-cap exception: Standard keeps M = 1 through OS 200%; above the cap it is intentionally bounded (documented in the Settings help copy).
  • SD5 explicit opt-in: SliderWithButtons.isWeightValue: Boolean = false; only the 3 weight sites pass isWeightValue = true. Re-census on this branch (main@4d4de558): 3 weight / 5 rep = 8 call sites (RestTimerCard:577 weight / :530 rep, RoutineOverviewScreen:753 weight / :686,741 rep, SetReadyScreen:712 weight / :673,726 rep — classification re-derived, not inherited).
  • SD6 global device-local preference: enum name under settings key weight_text_scale; UserPreferences.weightTextScale → SettingsPreferencesManager → SettingsManager (field absent from overlayProfile) → MainViewModel.SettingsGlobalUiState → existing globalSettings flow (Settings destination still collects exactly 3 flows — contract test extended) → SettingsTab → EnhancedMainScreen CompositionLocalProvider(LocalWeightTextScale). Not in CoreProfilePreferences, portal codec, or backup codec; backup restore never writes the key.
  • SD7 responsive: radio rows (whole row toggleable, Role.RadioButton, ≥48dp, child radio onClick = null to avoid duplicate announcements) for compact/large-text layouts; segmented only where the labels fit. Effective scale E drives compact weight-header stacking (even at OS 1.0), WeightStepper value-own-row at E > 1.5, and the Routine Overview reduced-viewport condition. shouldStackWeightCards byte-identical.
  • SD8 copy: the signoff helper wording ships verbatim (localized in de/es/fr/it/nl too), scrollable, never clipped. Labels exactly Standard / Large / Extra large. No 3× option.

Test evidence (exact commands, main@4d4de558 + this branch)

JDK 17 (/opt/homebrew/opt/openjdk@17/libexec/openjdk.jdk/Contents/Home), discovered task names (SD13 — testDebugUnitTest does not exist on current main):

  • ./gradlew :shared:testAndroidHostTest -Pskip.supabase.check=true — BUILD SUCCESSFUL, 5784 tests, 0 failures (JUnit XML aggregate over 558 result files; full host suite incl. WeightDisplaySourceGuardTest + WeightFeatureGuardTest passing unchanged — T21).
  • ./gradlew :shared:compileTestKotlinIosSimulatorArm64 :shared:iosSimulatorArm64Test -Pskip.supabase.check=true — compile green. The iOS test run is environmentally red on this host: a clean-main control run (origin/main @ 4d4de558, separate worktree, same command) fails 229 tests (all readProjectFile-based source/SQL contract tests and sqliter simulator tests — docs/backend-handoff/* resolution under the Kotlin/Native test-runner CWD is broken here). This branch's run fails the same 229 plus 6 of the new WeightTextSizeSurfaceGuardTest source-guards, which fail only at the same readProjectFile resolution point (WeightTextSizeSurfaceGuardTest.kt:42) and are green in :shared:testAndroidHostTest. Pure-math WeightTextScaleTest/WeightTextScalingTest pass on iOS. No test was disabled to pass; no regression vs. clean main. CI (ci-tests.yml) compiles the iOS target on PRs and does not run the iOS tests.

New tests added (24): WeightTextScaleTest (T1/T3), WeightTextScalingTest (T7–T10, T18), WeightTextSizeSurfaceGuardTest (T16/T17/T20 + SD4/SD12 invariants incl. backup-restore non-interference), SettingsPreferencesManagerTest extensions (T2/T3/T13 incl. write-error + last-choice ordering), SettingsManagerTest extension (T4 overlay survival), WindowSizeClassTest extensions (T19), ProfileSettingsSeparationContractTest extensions (T14 + SD8 verbatim copy), WeightTextScaleAndroidConversionTest (T11 Robolectric), LocalWeightTextScaleDefaultTest (T12).

Presentation-only invariant (T22)

git diff origin/main --stat touches only presentation screens/components, the preference seam (UserPreferences/PreferencesManager/SettingsManager/MainViewModel), string resources, and tests. No data/ble/**, data/sync/**, sql/**, ProfilePreferencesCodec.kt, BackupModels.kt, DataBackupManager.kt, or shared/src/tvosMain/** changes.

User summary / release note (from user-instructions.md)

New Settings → Appearance → Weight text size (Standard / Large / Extra large) enlarges weight values in Set Ready, Routine Overview, rest, exercise setup, and the workout readout (including Adaptive and bodyweight modes). Combines with device text size up to a 2× readable limit; Standard is unchanged at normal device text sizes. Saved on this device only (not part of app backup; restore never resets it) and applies immediately — select Standard to return to the default size. Just Lift is unchanged in this first version; no 3× option. Training data, weights, units, and machine behavior are unchanged. No charge.

Visual evidence

Final in-app screenshots are captured from this implementation branch (real app in the iOS simulator, XCUITest + simctl capture, real OS text-size settings via simctl ui content_size) and uploaded to the coordinated rolling release tag v1.1.0. They are listed with release-asset links in an immediate follow-up PR comment (per pipeline convention: no local filesystem paths in public comments) and recorded in ticket state (final_visual_artifacts, final_visual_summary, final_visual_captured_at). The §6 matrix frames (all app choices × OS text sizes on a compact phone; short/tablet spot coverage) land in that comment.

Merge gate

This worker never merges. Handing to the escalated merge gate (phoenix-rca) when checks are green. Issue closes via the Fixes #1367 keyword on merge.

#1367)

Adds a device-local Settings -> Appearance -> Weight text size preference
(Standard / Large / Extra large; nominal 1 / 1.5 / 2) that enlarges weight
values on the safety-critical weight surfaces: Set Ready, Routine Overview
and Rest Timer weight sliders (SliderWithButtons isWeightValue opt-in),
both Workout HUD value branches (numeric/Adaptive and bodyweight), and the
WeightStepper numeric value.

SD1 rendered cap: style multiplier M = E/O with E = min(A*O, 2) applied to
fontSize and explicit sp line height; every layout decision uses E. SD2:
Standard keeps M = 1 through OS 200% with the documented above-cap bound.
SD4/Option B: Just Lift, CompactNumberPicker and shouldStackWeightCards are
unchanged. SD6: enum name under settings key weight_text_scale riding the
existing globalSettings flow (Settings destination still collects exactly 3
flows); not in profile overlay, portal codec or backup codec. SD8: verbatim
signoff helper copy, no 3x option.

Tests: 24 new tests (WeightTextScaleTest, WeightTextScalingTest,
WeightTextSizeSurfaceGuardTest, WeightTextScaleAndroidConversionTest,
LocalWeightTextScaleDefaultTest, SettingsPreferencesManagerTest,
SettingsManagerTest, WindowSizeClassTest and
ProfileSettingsSeparationContractTest extensions). Full host suite green:
5784 tests, 0 failures (test-results XML aggregate).

Fixes #1367
Copilot AI balanced review requested due to automatic review settings November 14, 2026 19:33

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

Devil added 2 commits November 15, 2026 12:10
…le (#1367)

The rendered-cap weight-text style helper (WeightTextScaling.kt) was placed in
shared/src/commonMain, but it imports androidx.compose.ui (TextStyle, TextUnit,
LocalDensity, sp). commonMain is shared verbatim with :shared-tvos, whose
commonMain dependency graph has only cmp.runtime — never cmp.ui (cmp.ui is a
phoneMain-only dependency). So :shared-tvos:compileKotlinTvosSimulatorArm64 and
:shared-tvos:compileKotlinTvosArm64 failed with "Unresolved reference 'ui'",
breaking the native-tv and native-tv-device CI checks.

Move the file unchanged into shared/src/phoneMain/presentation/util/ (same
package), alongside WindowSizeClass.kt and LocalWeightTextScale.kt. All five
public helpers are consumed only by phoneMain surfaces (SliderWithButtons,
WeightStepper, RoutineOverviewScreen, WorkoutHud); no commonMain/iosMain/
tvosMain code references them. commonTest sees phoneMain (precedent:
WindowSizeClassTest -> WindowSizeClass), so WeightTextScalingTest keeps
compiling, and :shared-tvos never compiles commonTest (its WindowSizeClassTest
androidx.compose.ui.unit.dp import is green on the base commit). This is a pure
relocation: zero behavior change, no tvOS/backup/schema scope touched.
Resolve localized strings conflicts by keeping both appended string
blocks (1367 weight-text-size + 1360 rest-control feedback) in de/es/fr/it/nl.
@9thLevelSoftware

Copy link
Copy Markdown
Owner Author

Merge conflict resolution + re-verification (implementation worker, run 10)

main advanced via #1398 (rest-control outcome contract), which conflicted with this branch in the localized strings.xml files. Resolved by keeping both appended string blocks (1367 weight-text-size + 1360 rest-control feedback) in values-de/es/fr/it/nl; all six locale files validate as XML and values/strings.xml carries both key sets. RestTimerCard.kt merged cleanly (the 1367 isWeightValue = true weight slider site coexists with the 1360 rest-control changes).

Merge commit 8c3c8d47d (origin/main 7e1b4ac70 -> this branch), pushed to feat/1367-weight-text-size.

Local verification on the merge result (JDK 21, -Pskip.supabase.check=true):

  • :shared:testAndroidHostTest — 5796 tests, 0 failures, 0 errors
  • :androidApp:testDebugUnitTest — 26 tests, 0 failures
  • :androidApp:testReleaseDexTypes — fixtures pass (valid typing accepted, String-to-Throwable rejected, missing artifacts fail closed)
  • :shared:validateSchemaManifest — 773 columns / 66 tables validated
  • :shared-tvos:compileKotlinTvosSimulatorArm64 + :shared-tvos:compileTestKotlinTvosSimulatorArm64 — pass (the [Feature]: Larger weight-selection font (2-3x) for low-vision / older-adult users #1367 tvOS compile fix is preserved)
  • :shared:compileTestKotlinIosSimulatorArm64 — pass

Note: the earlier native-tv / native-tv-device failures at a1c65ed0 were already fixed by fa190b02 (WeightTextScaling relocated to phoneMain); both legs passed on that head and CI is re-running on the merge commit now. No issue-state mutation; this is the existing PR #1399 resumed per infra-recovery guidance.

@9thLevelSoftware

Copy link
Copy Markdown
Owner Author

Final visual evidence — weight text size (#1367)

In-app screenshots captured from the implementation branch (head 8c3c8d47, capture checkout 82050c2b = head + one capture-only project.pbxproj simulator-target hunk, never pushed), real app build in the iOS simulator, driven by XCUITest + simctl capture with real OS text-size settings (simctl ui content_size: large = 100%, accessibility-medium = ~150%, accessibility-extra-large = ~200%). 20 curated frames are uploaded to the coordinated rolling release tag v1.1.0.

Rendered-size proof (workout HUD bottom-bar Weight/cable readout, pixel height of the value glyphs)

OS text size Standard Large Extra large
100% (large) 54 px (1.00×) 82 px (1.52×) 109 px (2.02×)
~150% (accessibility-medium) — — 109 px (capped)
~200% (accessibility-extra-large) 87 px (1.61×) 109 px (capped) 109 px (capped)

This matches the signed-off rendered-cap model E = min(A×O, 2) exactly: the rendered readout never exceeds 2× base at any device text size, Standard scales only with the OS (M = 1, the documented Standard-above-cap behaviour), and Extra large converges to the same capped size as Large once the cap binds. Measured programmatically (dark-glyph band height, identical frame position across cells).

Matrix frames (all on release v1.1.0)

Inline samples (Extra large at 100% vs Standard at 100%, then the Settings selector):

HUD readout — Extra large @ OS 100%

HUD readout — Standard @ OS 100%

Settings — Weight text size selector, Extra large selected @ OS 200%

Full curated set (all …/releases/download/v1.1.0/issue1367-final-<name>):

  • HUD bottom-bar readout across the matrix: compact-os100-{STANDARD,LARGE,EXTRA_LARGE}-hud-workout-*.png, compact-os150-EXTRA_LARGE-hud-workout-*.png, compact-os200-{STANDARD,LARGE,EXTRA_LARGE}-hud-workout-*.png
  • Settings selector per OS scale (all three choices driven through the real control): compact-os{100,150,200}-UI-settings-choice-{Standard,Large,Extra-large}.png
  • Signed-off helper copy (scrollable, unclipped): compact-os100-UI-settings-help-bottom.png
  • Set Ready / pre-workout config A/B at OS 100%: compact-os100-STANDARD-set-ready-STANDARD.png, compact-os100-EXTRA_LARGE-set-ready-EXTRA_LARGE.png
  • Option B control — Just Lift weight card at Extra large (deliberately unchanged in v1): compact-os100-EXTRA_LARGE-hud-readout-EXTRA_LARGE.png

Capture boundaries (honest gaps)

  • RestTimerCard and the in-routine SetReady/RoutineOverview weight sliders (SliderWithButtons isWeightValue sites) live in the routine-workout rest/set flow and need completed machine reps; they are not reachable in the simulator. Their wiring is proven by the committed tests (WeightTextSizeSurfaceGuardTest — 3 weight sites scaled / 5 rep sites byte-identical — plus WeightTextScalingTest, WeightTextScaleAndroidConversionTest, ProfileSettingsSeparationContractTest) and the signoff-stage prototype matrix (200 curated frames). Not faked here.
  • The routine-editor WeightStepper (rendered by ExerciseConfigModal) and the Configure Exercise sheet's wheel pickers (CompactNumberPicker) render identically across choices in these frames — for CompactNumberPicker that is correct signed-off behaviour (Option B/SD4 leaves Just Lift and the native picker untouched in v1); the scaled WeightStepper treatment is proven by its unit tests and surface guard tests.
  • Capture-environment disclosures: the machine is the app's simulator fixture (PHOENIX_SIMULATOR_FIXTURE=just-lift-connected); the app's "Set End Not Confirmed" safety dialog is acknowledged ("I checked") because no physical trainer exists in the capture environment; the EULA launch fixture seeds acceptance. No production behaviour depends on these.

This worker does not merge; handing to the escalated merge gate (phoenix-rca) — the PR body carries Fixes #1367 so merging closes the issue.

Devil added 2 commits November 17, 2026 17:52
Union-resolve additive strings.xml conflicts (values, de, es, fr, it, nl):
keep both this branch's weight-text-size strings and main's #1358 media
strings. No other conflicts; presentation files auto-merged.
Main's 6f95247 (#1406) landed 64.sqm (RepBiomechanics aggregateEligible /
velocity-loss clamp) without bumping the SD14 ratchet that
ExerciseMediaWiringTest enforces. The guard comment sanctions the bump
when a real migration lands; 64.sqm touches RepBiomechanics/WorkoutSession
only and does not mention ExerciseImage, so guard (b) is unchanged.

Pre-existing on clean main (both files byte-identical to origin/main);
required for this PR's merge of main to pass :shared:testAndroidHostTest.
@9thLevelSoftware

Copy link
Copy Markdown
Owner Author

Merge follow-up: main integration + migration-ratchet fix (PR follow-up worker)

Head updated 8c3c8d47 → 1ae2b67e (2 commits):

  1. merge: origin/main into feat/1367-weight-text-size — main advanced 6 commits since the previous head (fix: reflow set-summary text under accessibility width constraints (#1385) #1395, fix: bound badge dialog grid width before measurement (#1403) #1404, feat(hrm): generic BLE heart-rate sensors — Garmin broadcast support (#1359) #1402, feat(media): user photos on custom exercises (issue #1358 Phase 1) #1397, fix: rebuild iOS cue players after focus loss (#1357) #1405, fix(vbt): keep calibration and ramp reps out of set velocity aggregates (#1400, part 1 of 2) #1406). The only conflicts were additive strings.xml blocks in values/, de, es, fr, it, nl (this branch's settings_weight_text_size* keys vs Add photos/videos for custom workouts, displayed during use like existing workout media #1358's media_* keys). Resolved as a strict union on every locale — key counts verified additive (base + 7 + 30 per locale), all files parse as XML, no duplicate <string name> keys. Presentation sources (MainViewModel, SettingsTab, RestTimerCard) auto-merged.

  2. test: bump ExerciseMediaWiringTest migration ratchet 63 -> 64 — main's newest commit 6f952472 (fix(vbt): keep calibration and ramp reps out of set velocity aggregates (#1400, part 1 of 2) #1406, issue [Bug]: Velocity is 10x too low (stored as cm/s, labelled mm/s); set MCV and velocity loss include calibration and ramp reps #1400) landed 64.sqm (RepBiomechanics aggregateEligible + velocity-loss clamp) without bumping the SD14 ratchet in ExerciseMediaWiringTest.noMigrationTouchesExerciseImage (maxSeen <= 63). This is pre-existing on clean main (both the migration and the test are byte-identical to origin/main in this merge; main's own CI Tests run for 6f952472 is still in flight). The guard comment sanctions the bump when a real migration lands: 64.sqm touches RepBiomechanics/WorkoutSession only and contains no ExerciseImage mention, so guard (b) ("only 43.sqm may mention ExerciseImage") is unchanged.

Verification (local, JDK 17, -Pskip.supabase.check=true):

  • ./gradlew :shared:testAndroidHostTest on the merged tree: 6026 tests, 0 failures (583 result files; 1 pre-existing ratchet failure resolved by commit 2).
  • Presentation-only invariant (T22) re-checked post-merge: git diff origin/main touches no data/ble, data/sync, sql/, ProfilePreferencesCodec, BackupModels, DataBackupManager, or tvosMain files.

CI on 1ae2b67e is running; this PR remains with the escalated merge gate (phoenix-rca) for the final call — this worker never merges.

@9thLevelSoftware

Copy link
Copy Markdown
Owner Author

Merge gate — #1367 / PR #1399: not merged (new merge conflict)

The escalated merge gate (phoenix-rca) audited head 1ae2b67e. Verdict: hold. Sending back to PR follow-up. The only blocker is a new merge conflict.

Passed:

  • Signoff is approved (escalated-model review). The feasibility, architecture, integration, prototype, spec and user-instructions artifacts all exist.
  • The PR body has Fixes #1367, and GitHub's closing-issue reference resolves to [Feature]: Larger weight-selection font (2-3x) for low-vision / older-adult users #1367.
  • All 12 checks on 1ae2b67e are green. GitGuardian is not a gate. iOS Simulator Tests is non-blocking and was skipped.
  • There are 0 unresolved review threads. The only review is a COMMENTED review from the Copilot reviewer.
  • Final in-app visual evidence comes from the implementation branch. It is uploaded to the v1.1.0 release and linked in #issuecomment-6958580173: 3 embedded images, 20 frames.
  • Scope matches the signed-off spec. 34 files are changed vs merge-base 6f952472: the preference domain and persistence, the bounded scaling helper, the Settings selector, the SetReady, RoutineOverview and RestTimer sliders, the WorkoutHud readout and WeightStepper, plus tests. Nothing touches data/ble, data/sync, SQLDelight or migrations, codec or backup, tvOS, Just Lift or CompactNumberPicker. The stop-button request ([Feature]: Stop button should turn off the weight and stay in the current lift mode (Standard, Echo, etc.) #1366) is not included.

Blocker: after follow-up, main moved 6f952472 → c28f5094. That commit separately lands the same SD14 ratchet bump (63→64) in ExerciseMediaWiringTest.kt. GitHub now reports mergeable=CONFLICTING / mergeStateStatus=DIRTY. A local git merge origin/main conflicts only in the T6 comment block. The logic is identical on both sides (maxSeen <= 64).

Fix needed (PR follow-up): merge origin/main into feat/1367-weight-text-size. Resolve ExerciseMediaWiringTest.kt by taking main's version as-is. After that, this branch has no diff in that file. Push, wait for CI to go green, then hand back to the merge gate.

…-size

# Conflicts:
#	shared/src/commonTest/kotlin/com/devil/phoenixproject/presentation/ExerciseMediaWiringTest.kt
@9thLevelSoftware

Copy link
Copy Markdown
Owner Author

Merge conflict resolution #2 — main integration (PR follow-up worker)

main advanced again after the merge gate's audit (6f952472 → ca2fefe1, 5 commits) and ExerciseMediaWiringTest.kt went CONFLICTING again — main independently landed its own noMigrationTouchesExerciseImage ratchet bump (c28f5094) plus follow-on test changes (#1409, #1412).

Resolution: merged origin/main into feat/1367-weight-text-size (head 1ae2b67e → b83c7c95) with exactly one conflicted file, resolved by taking main's version of ExerciseMediaWiringTest.kt byte-for-byte (verified identical to origin/main:... by SHA-256). Our branch's earlier ratchet bump commit (63→64) is fully subsumed by main's own bump — main now ratchets at 65.sqm and the resolved file carries that. All other files auto-merged (including WorkoutHud.kt; weight-scale wiring re-verified present post-merge).

Verification on the merged tree (local, JDK 17, -Pskip.supabase.check=true):

  • Full host suite :shared:testAndroidHostTest: 589 suites / 6077 tests / 0 failures / 0 errors (JUnit XML aggregated; up from 6026 pre-merge — main's new tests joined).
  • PR diff (three-dot) remains limited to the signed-off weight-text-size scope files; ExerciseMediaWiringTest.kt dropped out of the diff entirely since it now matches main.
  • Presentation-only invariant (T22) holds: no data/ble, data/sync, sql/, codec, backup, or tvosMain changes.

CI is now re-running on b83c7c95. Final visual evidence is unchanged from the implementation stage (comment #issuecomment-6958580173, 20 curated frames on release v1.1.0). This worker never merges — handing back to the escalated merge gate (phoenix-rca) once checks are green.

@9thLevelSoftware

Copy link
Copy Markdown
Owner Author

CI on head b83c7c95 is fully green: 11 checks pass (Build Android, Unit Tests, Lint, Android App Unit Test Results, Shared Module Test Results, iOS Test Target Compile, iOS Schema Sync Check, Security Hygiene, native-tv, native-tv-device, GitGuardian) + 1 skipping (non-blocking iOS Simulator Tests). PR is OPEN / MERGEABLE / CLEAN vs main ca2fefe1, Fixes #1367 linkage intact. Handing to the escalated merge gate (phoenix-rca).

@9thLevelSoftware
9thLevelSoftware merged commit 2734310 into main Nov 18, 2026
12 checks passed
@9thLevelSoftware
9thLevelSoftware deleted the feat/1367-weight-text-size branch November 18, 2026 04:44
@9thLevelSoftware

Copy link
Copy Markdown
Owner Author

Merge gate: merged ✅

The escalated merge gate merged PR #1399 into main as squash commit 2734310. This closes #1367.

What ships: a new Weight text size setting under Settings → Appearance, with Standard, Large and Extra large options. It enlarges the weight number on these screens:

  • Set Ready weight selector
  • Routine Overview weight selector
  • Rest-timer weight selector
  • Exercise weight stepper
  • Workout HUD weight readout

The text grows up to about 2×. When the phone's own text size is also large, the effective size is capped so the two settings don't multiply each other. The setting is saved on each device. Just Lift is unchanged, and the stop-button request (#1366) is tracked separately. This feature is developed voluntarily at no charge.

Gate audit:

The change will be in the next rolling release (v1.1.0 notes).

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.

[Feature]: Larger weight-selection font (2-3x) for low-vision / older-adult users

2 participants