ANODA Discuss your product

A custom orthotics app, from HR invite to insoles

Hike brings custom orthotics to people on their feet all shift, through their employer.We designed its brand, employee iOS app and HR admin.

Hike HR admin: the Northwind roster with the CSV upload, two uploaded files and the employees’ names and emails; Hike app loading screen on a phone: the logo on blue, Hello! and a note that the data is being processed
iOS
app installed from the App Store, onboarding to the order
3D
foot scan guidance, permissions, capture, checks and retries
Desktop
admin the employer’s roster and invitations
Brand
from zero the logo, the visual language and a trade-show booth

Hike is a new workplace foot-health company that brings custom orthotics to employees through their employer. We gave Hike a brand from zero and the product design : the employee iOS app with its LiDAR foot-scan journey, a desktop HR admin and the design system under both, then carried the brand onto an exhibition booth.

What happens between an invite and a pair of insoles

The employee’s path from HR’s invitation to the order, and the employer’s side that starts it:

  1. Invite

    • HR’s roster upload
    • Invitation email
    • App Store download

  2. Explain

    • What the programme is
    • What happens next

  3. Tell us

    • Name and job
    • Body and shoes
    • Delivery address

  4. Where it hurts

    • One condition a screen
    • Anything else

  5. Scan

    • Pain map
    • Sizing guide
    • Permissions
    • Capture
    • Checks and retries

  6. Order

    • Processing
    • Order status
    • Feedback
HR’s rollout Each person’s pace
The employer invites everyone at once; each employee installs, answers and scans alone, and should never need to call HR.
Clinical detail Plain words
The orthotics need precise answers about pain and a usable scan; the questions have to read like a conversation.
A new company Enterprise buyers
Hike had no history to point to, so the brand, the app and the booth had to look like one established company.

One pain question, read top to bottom

Found
Asking people to rate conditions they may not have names for, like plantar fasciitis or bunions, loses them on the first word.
Decided
Each condition gets a screen of its own in the same order: where you are in the questions, a picture of the foot with the painful area shown, a few lines in everyday words, three answers, and Next, which unlocks once one is chosen.
For the user
An employee recognises the pain from the picture before reading the name, answers with one tap and always knows how many questions are left.
Hike pain question 1 of 11, toe pain: a foot with the toes marked red, a description of common causes and symptoms, and No, Sometimes and Yes above a disabled Next

  1. Where you are

    The condition’s name and the question’s number.

  2. The picture

    The foot, with the painful area marked.

  3. In plain words

    What the condition feels like and where it comes from.

  4. The answer

    No, Sometimes or Yes, one tap.

  5. Next

    Unlocks once an answer is chosen.

How the work progressed

From a brand for a company that didn’t exist yet to an app, an admin and a booth, one question closed at a time.

  1. Discovery & user flows

    Who does what between HR’s invitation and the order

    Artifact User flows for onboarding, the foot scan and orders, reworked from a first version into a second

  2. Wireframes

    The order of the form, the questions and the scan before colour

    Artifact Greyscale wireframes of the employee app

  3. UI — iOS app

    An app a first-time user can finish alone

    Artifact Onboarding, the form, the pain questions, the scan journey and orders, redesigned again in a follow-on release

  4. UI — HR admin

    How the employer brings a whole team in

    Artifact Sign-in and a roster built from uploaded employee files

  5. Exhibition booth

    The brand in front of enterprise buyers at a trade show

    Artifact A backdrop, stand banners and an overhang

  6. Delivery

    What the developers needed to build it without guessing

    Artifact The design system and the screens, organised by flow

Three journeys, mapped before they were drawn

Found
Onboarding, the foot scan and orders each branch: a shoe size that needs other instructions, a photo to retake, a second order that has to wait.
Decided
Every journey was mapped end to end in FigJam, then reworked into a second version. The app keeps a short tab bar, and the employer works in a two-tab desktop admin.

  1. Onboarding

    From the splash screen and the login link sent by the employer to general information, the pain questions, shoe details and the delivery address, then on to the scan or home.

    Open the full map
    User flow of Hike onboarding: splash, onboarding, login by a link generated by the company, general info, foot pain checkboxes and shoe details, address, success, then the foot scan or home

  2. The foot scan

    The pain map, a branch for shoe sizes over 11, the reasons for camera and sensor access, the photo and its check, then the video and its check, each with a way back.

    Open the full map
    User flow of the Hike foot scan: pain map, a shoe-size-over-11 decision, sizing instructions, the permission explanation, system access, capture photo, preview and an is-everything-right loop, then instructions for the video

  3. Orders

    Orders in progress and received, each with its details, feedback after delivery, and a new order that waits twelve months after the last one.

    Open the full map
    User flow of Hike orders: my orders, orders received with feedback, orders in progress with the expected date, and a new order that checks whether it is the first
Hike HR admin roster: Dashboard and Roster in the header, a CSV upload area, two uploaded files and the employees with their emails

Two tabs for the employer

HR signs in to a dashboard and a roster; employees are added by uploading a file, not typed in one by one.

  • User flows for onboarding, the scan and orders
  • A second version of every flow
  • A short tab bar in the app
  • A two-tab HR admin

What each step asks of the employee

From the invitation to the order, each in the words and size a first-time user needs, then the employer’s side.

An invitation that explains itself

Found
The employee didn’t choose Hike; the employer did. The first message and screens have to say what this is and what to do next.
Decided
The invitation email carries one link. The first screens ask a question the reader recognises and show the whole programme in three steps: fill in some information, scan your foot, pick up your insoles.
Hike invitation email on a phone: you have received an invitation to the Hike application, with a link to the app to order custom insoles
Hike intro screen: an illustrated worker thinking about a sore heel, Are you on your feet all the time?, and That’s me!
Hike intro screen: a phone with three bubbles, fill in some personal information, scan your foot, pick up your new insoles, and Start

A form with nothing extra

Found
Orthotics need a name, a body, a job and an address, and a long form on a small screen is where first-time users give up.
Decided
Short steps with a numbered progress line, pickers instead of typing wherever a list will do, and Continue that stays grey until a step is complete.
Hike form step 1 of 4: full name, date of birth and job type filled in, and Continue
Hike form step 2 of 4: age, gender, weight and height chosen from pickers
Hike form step 4 of 4: state of residence, zip code and street address, with a note that they are needed for delivery

Where it hurts, one condition at a time

Found
A checklist of medical terms asks people to diagnose themselves.
Decided
A short break says how many questions follow and why. Then each condition has its own screen with a picture and plain words, and the last one lets people describe anything else in their own words.
Hike break screen on blue: Great! One more stage!, eleven questions about foot pain to make the right insoles, and Next
Hike pain question 2 of 11, heel pain: feet with the heels marked red, a description, and Yes selected
Hike last question, 11 of 11: describe any other foot pain or issues, with the keyboard open

Getting ready to scan

Found
A foot scan fails before it starts if people don’t know where it hurts, how to stand or why the app wants the camera.
Decided
A tappable map of each foot first, then an illustrated sizing guide with a separate path for large sizes, and the reason for camera and sensor access before the system asks.
Hike foot pain map: choose the left or right foot and tap the areas of the sole that hurt, then Next
Hike foot sizing: an illustration of a foot on paper against a wall, three steps for shoe sizes 11 and under, and I have size 11+
Hike video instructions: an example clip of both feet and pro tips, record for 20 seconds, keep the foot and camera still

Capture, check, retry

Found
A blurred photo or a foot out of frame only shows up later, when the order is already on its way.
Decided
The camera frames the feet with corner guides, every capture comes back as Is everything right? with Reshoot beside Next, and the end of the scan says what happens next and when the insoles should be ready.
Hike camera in photo mode with red corner guides around both feet on the floor
Hike capture check: the photo of both feet, Is everything right?, with Reshoot and Next
Hike success scanning: your order has been processed, with the estimated date the order will be ready

After the scan

Found
Once the scan is sent, people want to know where their insoles are, and Hike wants to know whether they helped.
Decided
Each order has a details page with its status and dates, and after delivery a few questions with stars and a free-text answer.
Hike order details: custom insoles, status complete, created and delivery dates and the address
Hike questions after delivery: rate the quality of the insoles with stars and write a few words about them

The employer’s side

Found
HR has to bring in a whole team without typing every name, and see who is on the programme.
Decided
A desktop admin where HR signs in, drops the employee file into the roster and sends the invitations once the upload finishes.
Hike HR admin roster: a CSV file uploaded to 100 percent with Send! enabled
Hike HR admin sign-in: Welcome to Hike with email and password beside the footprint mark

A brand for a company that didn’t exist yet

Found
Hike had to look like an established healthcare company to the employers buying it and like something friendly to the people on the shop floor using it.
Decided
Logo directions from footprints to abstract waves and bold wordmarks, each tried as an app icon. The final mark is a soft wave in the medical blues over the Hike wordmark, and it carries from the app’s splash screen to a trade-show booth.
Directions of Hike logos on app-icon tiles: abstract symbols, footprints with the wordmark, bold wordmarks, and gradient waves with the wordmark
The final Hike logo: a blue gradient wave above the Hike wordmark with medical in light blue
Hike exhibition backdrop: the logo and We keep your workforce moving over illustrated workers in blue uniforms
Two Hike roll-up banners: We keep your workforce moving with the offer in cards, and illustrated people walking and running
Hike overhang banner: the logo and We keep your workforce moving on white with soft blue waves

One system from the question to the scan

Found
Pain questions, a pain map, a scan and an admin, designed over more than one release, could easily drift into different apps.
Decided
One UI kit for the app and the admin: the same foot illustrations, buttons, pickers, dialogs and progress, each drawn with the states people meet when something needs explaining or waiting for.

A foot drawn the same way everywhere

Every condition uses one illustration style, with the painful area in the same red, so the pictures read as a set.

  • Hike illustration for flat feet: two soles side by side, labelled Healthy Foot and Flat Feet, the flat one marked red along the arch
    Flat feet: A healthy foot beside a flat one.
  • Hike illustration for plantar fasciitis: one sole with the ball of the foot and the heel marked red
    Plantar fasciitis: The same sole, marked where it hurts.

Drawn for the moments in between

A word that needs explaining, an order that has to wait, a scan being processed: each says what is going on and what comes next.

  • Hike shoe width help: a dialog explaining wide, normal and narrow over the shoe information step
    What a word means
  • Hike dialog: You need to wait, new insoles can be ordered only 12 months after the previous ones were received
    Too early for a new order
  • Hike scan in progress: the foot map with a scanning line and a note to wait before the model is ready
    Scan in progress

Where the product ended up

One design for Hike’s whole journey: an employer uploads a roster and invites the team; each employee reads a plain invitation, fills in a short form, answers the pain questions one at a time and scans both feet with guides, checks and retries, then follows the order.

Around it, a brand from zero and an exhibition booth in the same look, with a design system under the app and the admin. ANODA designed it; the scanning technology, the app build and the insoles were built by others.

employee app, from the invite to the order
iOS
HR admin for the employer
Desktop
from zero to the booth
Brand

In the client's words

As a startup, we needed to move quickly and bring the whole business to life. ANODA helped us do that across our brand identity, app, website and even our exhibition booth. They understood what we needed to get started, helped us prioritise, and kept everything moving without losing attention to detail. Having one team connect all those pieces made a real difference—we could focus on building the business while they gave Hike a cohesive, professional presence from the start.

Aadi Bhanti Chief Executive Officer, Hike Medical

5.0

Afraid your rollout will turn HR into a help desk?

In Hike, an employer uploads one file, and every employee goes from the invitation to a finished foot scan on their own: plain words, one question at a time, and a way back from every failed capture. Tell us who has to get through your onboarding without help, and we’ll show you where they’d stop today.

Discuss your product Explore more case studies

What we brought to Hike

The product

The brand and the system