PRODUCT DESIGN · 2026

Custom Fields

Turning transaction notes into useful reporting fields.

Custom Fields case study

PROBLEM

Finance teams put project names and client details in transaction notes because Swipey had no columns for them. That information could explain a purchase, but could not be used to filter transactions or build reports.

CONTEXT

Alfie already helped people file expenses. I extended it to spot project names in transaction notes and suggest a Project column. An admin decides whether to create it.

  1. 1
    Suggest the field here

    Alfie offers to create the field where the admin is already reviewing transactions.

  2. 2
    No Project column yet

    The table has standard transaction columns, but no Project column yet.

FULL UI

Swipe to explore the close-up views, or use PREV and NEXT below.

Suggest a useful field

Alfie notices project information in transaction notes and suggests adding a field.

VIEW 1 OF 3

Suggest a useful field

FIELDS

A shared field affects how the whole company records expenses. I kept field management in one admin-only panel. Admins define the fields; people fill them in on their transactions.

  1. 1
    State who can make the change

    The admin-only notice explains the permission boundary directly.

  2. 2
    Keep shared settings together

    The field list groups visibility and required-field settings, rather than scattering them across transactions.

FULL UI

Admins manage shared fields

The notice states who can change the company’s fields and rules.

VIEW 1 OF 2

Admins manage shared fields

AI REVIEW

Alfie suggests project names from existing notes. Dashed outlines show which values still need review. The admin can accept them together or come back later, keeping suggestions separate from confirmed information.

  1. 1
    Show what is still a suggestion

    Dashed outlines distinguish the suggested project names from confirmed information.

  2. 2
    Keep review in the admin’s hands

    Accept all and Review later make the next action explicit.

FULL UI

Suggestions are not confirmed data

Dashed outlines mark the project names that still need review.

VIEW 1 OF 2

Suggestions are not confirmed data

PROTOTYPE

The prototype connects three steps: Alfie suggests a field, an admin creates it, and the admin reviews its values. These recordings follow that flow with example transactions.

TAKEAWAYS

Using the prototype revealed that a new column could appear offscreen. I learned to review the whole task, including where its result appears. Next, I would test with finance teams and check the mobile table.

Product DesignData UXAI InteractionDesign Systems