Liam Ferguson

Product designer & developer

I design digital products and get them built.

I’ve worked in web design and development, B2B ecommerce and employee communications software. I recently moved to Germany and am looking for my next role in product design or design engineering.

Available November 2026

Experience

  1. Product Designer

    Thrive.App · Belfast, Ireland

    Sole product designer for Thrive’s employee app and CMS, working across three engineering teams. I helped define features, design flows and interfaces, and review implementation.

    PasskeysChatPlannerApp Store screenshot generator
  2. UX Designer

    Allstate · Belfast, Ireland

    Researched and designed an internal application for casualty claims adjusters. I worked with product, engineering, legal and claims experts to understand their workflows and develop user flows, prototypes and detailed interface designs.

  3. Digital Developer

    G&G Advertising · Toronto, Canada

    Built websites, email campaigns and digital advertising as the agency’s first and only developer. I worked directly with creative teams and clients.

  4. Web Developer & Designer

    31interactive Ltd · Belfast, Ireland

    Designed and built websites for clients in housing, hospitality, enterprise and local business, using the agency’s in-house CMS.

Side projects

Thrive.App

Passkeys for employee sign-in

Product design · 2025

I designed passkey setup, sign-in and recovery for Thrive’s employee app. The challenge was making sign-in easier while keeping access tied to a verified employee account and explaining what stayed on the device.

An account comes first

An employee app cannot let anyone create an account and start reading company information. People need to be registered in the organisation’s system before they can get access.

I placed passkey setup after the employee’s first password sign-in. At that point, they already have an account and have proved they can access it. The passkey makes subsequent sign-ins smoother without weakening the identity checks that gate access.

Each organisation decides whether passkeys are optional or required. When optional, employees can skip setup and add one later.

Explaining what stays on the device

Asking someone to use Face ID or a fingerprint in an app provided by their employer could raise an uncomfortable question: is the company collecting that information?

The introduction explains that they can use the same face, fingerprint or PIN check they use to unlock their device. Their biometric information stays on that device and is not shared with the employer.

Simplify your next sign in

Sign in securely with your device’s Face ID, fingerprint, or PIN. Faster, safer, and no passwords to remember. This never leaves your device and isn’t shared with your employer.

Continue
After the first password sign-in, the app explains that the biometric check stays on the employee’s device.

Keeping another way in

Many frontline employees don’t have a work email address or another account recovery channel. Once passkey sign-in was enabled, recovery couldn’t rely on simply emailing someone a reset link.

Losing a phone does not always mean losing the passkey. With a provider such as Apple or Google, a synced passkey can be available on another device using the same account. That depends on how their device and provider account are set up.

I also designed a way to sign in using a device where the employee is already signed in. They get a code on the device they want to access, then enter it in the app on their signed-in device.

Their passkey is on their phone, not this computer. Instead of a password, they can sign in using the phone they’re already signed in on.

Recovery needs a person

If an employee loses access to their passkey provider as well as their devices, they can request a recovery code and leave a message for an administrator.

The administrator sees the request in the CMS, including its IP address and an option to look up an approximate location. Those details provide context for checking the request, rather than handing over access automatically.

The app can notify the administrator, but recovery actions happen in the CMS. I made that boundary explicit so a notification would not be mistaken for an instruction to approve the recovery flow.

Account reset

Account recovery request for Jake Smith

A recovery request was submitted for Jake Smith’s account. Before approving, confirm that the request genuinely came from the account owner. All recovery actions must be completed in the CMS.

Go there now
The app alerts an administrator to the request. Recovery actions happen in the CMS.

Handling abusive requests

Recovery also needed a way to handle repeated or malicious requests. If an account was being targeted, an administrator could turn on an IP allowlist for that person. Recovery requests and sign-in codes would then only work from trusted addresses.

Blocked requests still appear to succeed. Someone trying to get into the account learns nothing about whether it exists or why their request went nowhere.

Fewer people locked out

I designed setup, everyday sign-in, device linking and recovery as parts of the same flow. Making the normal path easier mattered, but employees and administrators also needed to understand what happens when something goes wrong.

Passkeys are now used by thousands of employees across most of Thrive’s customers, and there are fewer reports of people being unable to sign in.