Camera-based rep counting

A practical setup

For camera-based rep counting, identify the input, the access result, the Apple permission involved, and the alternative when that input is unavailable. Test the setup once while you can still verify every selection and permission.

Worked example

Configure the smallest version, pair it with a 10-minute daily limit, and run one complete lock-session-open cycle before expanding it. Leave a step, saved-place, or unrestricted option available whenever the context requires it.

MoveFirst states that supported repetitions can be counted on the iPhone, with camera footage processed on device and neither recorded nor sent. Review the camera permission, choose a comfortable supported movement, and test a short set with clear framing. When camera use is unwanted or unsuitable, use the daily Apple Health step target or a place you name without treating the alternative as a lesser result.

How to measure the experiment

Across 14 days, use 3 observations for reliability, comfort, whether the rule is understandable, and accidental locking. Record whether the setup appeared at the right moment and whether its fallback was genuinely usable.

Before you switch it on

A feature is ready when its purpose, permission, fallback, and review signal can all be explained plainly.

• ✓Confirm what the feature does and does not do.
• ✓Review the relevant permission before enabling it.
• ✓Keep a step, saved-place, or unrestricted fallback when appropriate.
• ✓Test one complete cycle with a non-essential app.

When to adjust the rule

Change the movement goal or the selection when the feature works technically but creates the wrong daily behavior; do not hide that mismatch with a stricter target. If the same exception keeps appearing, redesign the selection instead of negotiating with it each time.