Camera controls: make auto and locked states clear

Name the mode before presenting its values

Halide Mark III presents Auto, Manual, Shutter Priority and ISO Priority as separate modes. Leica LUX places automatic labels for white balance and focus alongside exposure-related readouts and a dial. These examples show why a collection of numbers does not by itself describe which properties the person can change.

Make the selected mode explicit and explain the control relationship where needed. In a priority-style workflow, one value may be chosen while the camera adjusts another, according to the actual implementation. Do not style all displayed numbers as if they were equally editable. A readout that updates automatically needs a different interaction promise from a slider that sets a target.

When switching modes, preserve or reset values intentionally. If returning to manual restores a previous setting, make the result visible rather than surprising the person with an old value from a different scene. If a mode is unavailable on a particular camera, explain that capability boundary instead of leaving a disabled abbreviation whose reason is impossible to discover.

Keep the adjusted parameter and unit visible

(Not Boring) Camera labels its selected shutter-speed control and displays a fractional value with ISO and white balance nearby. Onform places shutter and ISO controls in a Manual panel with Reset and explanatory copy. The relevant lesson is the relationship between a gesture, its named property and the value it changes.

Avoid an unlabeled dial whose meaning changes without a visible state transition. Keep the property name and supported unit readable while dragging, and distinguish a fractional exposure duration from an ISO number or an exposure-bias value. A compact interface can still retain those identifiers; removing them entirely shifts the burden to memory and makes errors harder to diagnose.

Define the supported range from the actual device and current capture configuration. A visually identical slider may need different bounds after a lens or mode change. If a requested value must be adjusted, report the resulting supported value rather than leaving the old number on screen. Treat Reset as a scoped action so it does not unexpectedly change every manual property in the workspace.

Make lock scope explicit

Camera+ displays Exposure Locked alongside a separate focus adjustment and lock control. Afterlight shows a white-balance lock indicator in a camera workspace with additional automatic and ISO controls. These are not interchangeable global locks. Each one belongs to a particular property or supported relationship between properties.

Name what is locked and show when that state changes. If tapping a preview target locks focus but not exposure, communicate that distinction. If one gesture affects both, define the combined operation rather than letting a familiar padlock icon imply it. The state should remain understandable after the person opens another panel and returns to the live preview.

Test the lifecycle of a lock through lens switches, camera changes, backgrounding and capture-mode changes. Some configurations may not preserve the exact setting. When the implementation releases or replaces a lock, update the status promptly and explain any consequential change. A stale locked badge is more misleading than a brief, honest transition while the camera settles.

Separate white balance from focus targeting

Filmic Pro displays numeric white balance, ISO and shutter values alongside a selected-camera panel and a preview reticle. ProCCD exposes an AWB menu with named or symbolic lighting choices and a K option. A reticle and a white-balance preset may sit in the same workspace, but they address different camera decisions.

Keep the selected property visible when using shared gesture space. Tapping a reticle should not silently alter a different parameter because a temporary panel changed the gesture mode. If lighting presets are offered, label the selected preset as such rather than implying it is a measured description of the scene. A K icon alone does not establish that direct numeric entry is supported.

Provide readable status beyond the preview image. The effect of a parameter may be hard to judge under glare, in a low-contrast scene or on a small display. Text and accessible control values help establish what changed without relying exclusively on seeing the visual result. That feedback should describe the app’s actual state, not promise that the resulting image will be correct.

Keep control state legible across capture context

Kapi Cam presents a shutter-speed slider beside capture-mode and lens choices. Night Sky explains an ISO lock in a tutorial overlay above its camera controls. Both examples put a parameter inside a larger task, where changing mode or dismissing help should not obscure what the camera will do next.

Avoid teaching a gesture without teaching its resulting state. A tutorial can identify a lock action, but the regular interface still needs to reveal whether the property is currently automatic or locked after the tutorial disappears. Similarly, changing from photo to video should not leave the person looking at an apparently identical control whose supported range or meaning has changed invisibly.

Apple’s capture-device exposure documentation separates exposure modes, bias and custom exposure controls with capability checks. The UI should follow the capabilities actually available in its current configuration; a shared visual design is not a reason to promise the same controls on every lens or device.

Keep requests and camera feedback in sync

Represent each relevant parameter with its supported range, automatic/manual policy, requested value and confirmed value. Keep transient interaction state separate from confirmed camera feedback. A slider can respond immediately to touch while the camera configuration catches up, but the interface should not claim a hardware change succeeded merely because the thumb moved.

Associate updates with the active camera and configuration identity. A late response from the previous lens should not overwrite readouts for the newly selected one. Define how unsupported requests are clamped or rejected and show the resulting state. Keep exposure duration, compensation and ISO as different concepts rather than storing every number under a generic exposure label.

Make precise controls usable without relying on tiny drags. Offer supported step adjustments, readable values and accessible names that include the parameter and state. Large text should not cover the shutter or critical status. Avoid using only color to distinguish automatic, locked and unavailable values, and keep the live preview responsive without moving controls unpredictably beneath the person’s finger.

Test changes, not just a static camera screen

Ask a tester to lock one property, change another and explain which values the camera still controls. Change lighting while the interface remains open, then switch lenses and capture modes. Observe whether the person can predict the state from the labels without interpreting every visible change in the preview as a deliberate setting adjustment.

Test unsupported configurations, denied camera access, background interruption and rapid slider changes followed by capture. Inspect the actual supported capture metadata or device feedback where appropriate, rather than treating the displayed number as its own verification. Do not infer image-quality improvements from the presence of manual controls; that requires a separate evaluation with representative material.

Track accidental mode switches, stale status, incorrect reset expectations and repeated attempts to adjust an unavailable property. Separate user input from confirmed state transitions in diagnostics. These events can reveal control confusion without logging camera images, and they are more actionable than a general measure of time spent inside the camera screen.

Review control and capture state

Use these checks on a working build, not only on the polished reference state.

• ✓The active mode identifies which properties are automatic.
• ✓Every adjusted value retains its property name and unit.
• ✓Locks identify their actual property scope.
• ✓Lens changes refresh capabilities and confirmed values.
• ✓Reset has a visible and predictable scope.
• ✓Accessible input does not depend entirely on tiny drags.
• ✓The UI does not report a request as a confirmed capture setting.

Related design decisions

The camera and scanner examples address capture guidance and document framing. They answer a different question from manual parameter control.

Use the settings screen examples when deciding which persistent capture preferences belong outside the live shooting workspace.