developer portal

context

Sensedia is a leading API company, but its developer experience didn’t reflect that. The old portal was rigid, confusing, and underused. As the Product Designer, I led the redesign of the platform, focusing on technical autonomy, performance, and conversion.

problem

• Developers struggled to find and understand the APIs.

• Navigation was clunky and the information architecture didn’t scale with the product.

• The portal caused recurring doubts and slowed down the technical onboarding of partners.

strategic goals

• Position Sensedia as a leader in developer experience.

• Increase API engagement.

• Make onboarding faster, smoother, and scalable.

what I did

• Conducted research with internal and external devs

• Mapped major usability friction points

• Benchmarked portals like Stripe, Twilio, GitHub

• Redesigned the entire information architecture

• Created navigation flows and accessible UI components

• Ran usability tests focused on first impressions and usage flow

• Validated results with engineering and tech writing teams

solutions applied

• Welcome page with a clear view of what the portal offers

• Modular structure, easy to scale with new APIs

• Improved documentation readability

• Smart search and persistent side navigation

• Reusable components using the Design System tokens

results and impact

• Average onboarding time dropped from 5 days to 2

• Fewer support tickets about integration issues

• 47% increase in time spent on the portal

• Portal became an internal reference for future dev-facing products

key learnings

This project deepened my understanding of developer needs, sharpened my ability to translate technical problems into accessible solutions, and reinforced the value of collaboration across Design, Tech, and DX.

Tech, tools and skills applied: figma, ux writing in partnership with tech writers, accessibility (WCAG), dev experience, design system e prototyping.