I explored Huspy’s mortgage calculator through the lens of Progressive Disclosure. The question I...

I explored Huspy’s mortgage calculator through the lens of Progressive Disclosure. The question I...I explored Huspy’s mortgage calculator through the lens of Progressive Disclosure. The question I...

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Taste Test

Create your own

Sajid Ali

• 2d

I explored Huspy’s mortgage calculator through the lens of Progressive Disclosure.

The question I wanted to test was simple: Does every input need to be visible from the start?

In this design exploration, I reorganized the flow so users first define their mortgage context, then choose an interest rate. Predefined rates remain immediately available, while Custom Rate reveals the manual interest-rate field only when the user explicitly needs it.

The goal wasn’t to remove flexibility. It was to keep the common path simple while preserving advanced control for users who need it.

Would you prefer the custom interest-rate field visible upfront, or only when you choose a custom rate?

Figma UX Design Product Design

1 vote

Ends in 1m

TRUEFRAME

max

• 2d

the result card makes the numbers easy to read

Sajid Ali

• 2d

Thanks! I kept the result card largely unchanged because the hierarchy there already felt clear. My main exploration was around reducing upfront complexity in the input flow.