nightscout / nightscout/AndroidAPS

Easy to miss toggles on the calculator

Open
#3,210 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Kotlin
Stars
1.2k
Forks
6.4k
Avg merge
2d 7h
Merged PRs (30d)
19

Description

Screenshot_20240202-083736

Can we brainstorm some way to make the buttons a little more obvious in the hotspot shown? Due to the proximity to the OK and Cancel buttons, the toggles are very easy to accidentally press, and when they are toggled only a dimming is applied on/off. This makes it really hard for young or new users to the system to see, and it can often result in wildly incorrect bolus calculations.

Some ideas:

  • Borders around the buttons (toggles and/or OK and Cancel)
  • A more obvious on/off visualization
  • Placement of the toggles moved to be harder to hit accidentally
  • Confirmation dialog or some other mechanism to warn that the toggles have been pressed
  • A lock icon that requires pin entry to allow changes to toggles or other advanced features

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the calculator hotspot shown in the screenshot and inspecting the surrounding toggle, OK, and Cancel controls. Define a UI change that makes toggle state obvious and prevents accidental activation; done means the interaction is visibly distinguishable and safer for young or new users.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
accessibility, design, mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.