Replicon / iOS kiosk design

Cloud Clock

One person. One clear next action. Ready for the next shift.

My role
Product designer
Partners
Product, support & iOS
Context
Shared workplace kiosk
Focus
Recognition & state changes
01 / Problem

Make clocking in the smallest part of the shift.

A shared workplace kiosk needed to help one employee make a quick, correct change, then be ready for the next person.

One person should complete a clear session on a shared device.The kiosk focuses on the current employee and their next action before returning to a shared state.
One person should complete a clear session on a shared device.
02 / What exists today

A shared device, several ways to identify yourself.

The source describes a kiosk used for clocking in, breaks, transfers and clocking out. Badges, QR codes and login also allowed someone to clock in for another person.

Several ways to identify someone led into the same kiosk.Badge, QR and login methods surround the shared clocking interface.
Several ways to identify someone led into the same kiosk.
03 / What’s wrong

Too many choices at the moment of action.

The existing kiosk presented choices without giving enough priority to the action that matched the employee’s current state. Support’s issue catalog helped define the redesign.

Choices need to follow the employee’s current state.A crowded set of kiosk choices competes with the single action that fits the employee’s state.
Choices need to follow the employee’s current state.
04 / What I explored

Let the current state set the next choice.

I explored recognition with login and QR alternatives, actions matched to work state, remembered job selection, and a clear confirmation. Two taps was a design target.

Make the state determine what the kiosk asks next.Three kiosk studies give identification, contextual action and confirmation distinct roles.
Make the state determine what the kiosk asks next.
05 / Low-fi architecture

Identify, act, confirm, reset.

The state model links who is using the kiosk to the actions they can take. This reconstruction shows the documented sequence, including the three-second return to the camera.

System flowHow the pieces connect
Inputs
  • Live camera
  • QR or login alternative
The interaction
  1. 01Identify employee
  2. 02Read current state
  3. 03Choose relevant action
Outputs
  • Clock in / change state
  • Confirmation
  • Reset for next person

After confirmation, return to the camera in three seconds.

The kiosk sequence / 01

Start with recognition, with a way around failure.

The documented flow begins with a live camera. If facial identification is unavailable, it offers login or QR scanning.

The original state flow, presented in the portfolio’s visual language. The two-tap path was a design target.

06 / Wireframes

One employee, one complete session.

These reconstructed wireframes show identification, the relevant action, and confirmation. They explain the original design rather than presenting a new usability study.

Wireframe sequenceExplore the sequence
01 / 03

Start with a way in

Shared clock / IdentifyWireframe
Live camera
Identify yourself
Recognition
QR scan
Login
Device / Location
01Recognition has visible alternatives. The kiosk is ready for the next person.

Reconstructed from the documented design; sample content is illustrative.

07 / Solution

Make the person’s state readable at a glance.

A written status, color band and contextual actions work together. The original screen below shows the work-state view, with transfer, break and clock-out actions.

08 / Research

Support supplied the problems. Recovery still needs testing.

I worked with product, support and iOS engineering. The next evaluation should cover recognition failure, wrong job selection and whether three seconds gives people enough time to read a confirmation.

Recovery and confirmation timing are the next questions to test.An evaluation plan examines recognition failure, wrong-job selection and time to read the confirmation.
Recovery and confirmation timing are the next questions to test.
09 / Outcome

A clearer transition model; speed and accuracy remain unverified.

The design makes the session explicit: identify the employee, collect the required context, confirm the change and reset. The presentation’s performance claims have no documented method, so they are not treated as measured outcomes here.

The design makes the start and end of a session explicit.An employee’s confirmed change returns the kiosk to a ready state; no speed result is implied.
The design makes the start and end of a session explicit.
1ONICA FM

Choose a perspective. Access is approved personally.

Public mode is open to everyone. Other perspectives open by invitation.

Level 010 XP

100 XP to the next level

Your progress stays in this browser.