Case study
Appsmith Git Connect
Turning Git setup into a guided product experience
Appsmith ↗Choose your depth
The problem, my contribution, outcomes, and strongest screens.
My role
Product design · Developer experience · Interaction design
Product focus
A shared three-step model for Git connection, application import, and precise failure recovery.
Overview
I redesigned Appsmith’s Git connection and import journeys as one guided three-step model. Developers can choose a provider, configure SSH, grant repository access, and recover from failure without losing sight of where they are or why each external action is required.
The problem
Connecting or importing through Git crossed Appsmith and an external provider. Repository requirements, remote URLs, SSH keys, deploy keys, and write access all had to be correct before the product could succeed, but generic errors left users unsure which system to fix.
What I drove
- Converted technical prerequisites into a visible three-step flow shared by connection and import.
- Explained each repository action in context, with embedded guidance at the moment it was needed.
- Covered providers, existing repositories, remote URLs, key generation, deploy-key permissions, and confirmation.
What changed
- Turned repository and SSH prerequisites into a visible, teachable sequence.
- Connected configuration, import, success, and recovery through one reusable interaction model.
Impact
What the work was designed to move
Business impact
One interaction model across connection and import made a technically demanding capability easier to implement, support, and extend.
Customer impact
Developers can see the current step, understand each repository action, and recover without restarting the journey.
Revenue impact
Supports activation and continued adoption of Git workflows that increase Appsmith’s value for professional development teams.
Highlights evidence
3 essential screens from the final experience.
Continue reading