{/* Type A */}
User Type A
Experienced fitter
{['Reads measurement data intuitively','Navigates 121 options confidently','Builds recommendation from experience'].map(t => (
{t}
))}
Needs from the platform
{['Flexibility','Depth','Override'].map(tag => (
{tag}
))}
↓ Lower priority in v1 design
vs
{/* Type B */}
User Type B
Less experienced staff
{['Live consultation, customer present',"Can't hold full product logic in mind",'Needs a defensible answer to explain'].map(t => (
{t}
))}
Needs from the platform
{['Guided steps','Clear output'].map(tag => (
{tag}
))}
↑ Primary use case · drove all decisions
Designing for type B was the core structural decision. Type A is the next iteration.
{[
{ title:'Catalog complexity', body:'121 saddle variants, differentiated by geometry, material, and fit profile. Filtering logic had to be rigorous, but the result had to feel trustworthy, not algorithmically arbitrary.', Icon:IconBook },
{ title:'Hardware integration', body:'The platform connected with on-site pressure measurement devices. Data capture had to embed in the consultation flow without creating a separate technical step.', Icon:IconHardware },
{ title:'Brand context', body:"Fizik is a premium cycling brand. The interface had to feel consistent with that positioning while remaining fast and legible in a live, customer-facing environment.", Icon:IconBrand },
{ title:'Flutter delivery', body:'Built in Flutter. Design decisions needed to be grounded in what Flutter could realistically support, shaping interaction choices through to handoff.', Icon:IconCode },
].map((c,ci) => {
const CIcon = c.Icon;
return (
);
})}
{c.title}
{c.body}
