Build, review and deploy with Git

Connecting to Git was one screen with no way through it

Half of our developers struggled to connect Git inside Appsmith, with new issues reported every week.

Half of our developers encounter difficulties activating Git within Appsmith, through community reporting 2-3 issues every week when connecting.

50% of active builders who use Git hit an error

Plenty went wrong. But developers should not have had to fix it. Connecting could have been seamless instead of steps to work out.

Mapping the journey pulled out the 3 steps that matter

There was no existing pattern to be “inspired” by

Six tools connect to Git and no two ask in the same order. With nothing to follow, the flow came from our own users.

Six tools connect to Git and no two ask for the same things in the same order. With no convention to follow, the flow had to come from what our own users got stuck on.

A pod braindrawing session, so every angle was in the room

Everyone drew alone before anyone talked, so no one anchored on the first idea in the room.

Everyone drew alone before anyone talked, so no one anchored on the first idea in the room. Each take caught something the others missed.

None of the above flows asked which provider you use

Every tool opened on generating a key. None asked where the repository lives, so choosing a provider became step one.

Every one opens on generating a key. None asks where the repository lives, which is what tells the flow how to help. Choosing a provider became the first step.

The flow was settled, the teaching was not

The wizard settled the order of the steps, not how anyone gets through them, so a recording walks through each one.

The wizard settled the order of the three steps, not how anyone gets through them. Each one happens on a page we do not control, so the flow shows them instead.

Every part, gap and state, measured to the pixel

The dialog taken apart for handoff, every gap, size and state written down so nothing was left to guess.

The dialog taken apart for the handoff. Every gap, size and state is written down, so engineering had nothing left to guess.

Three steps, every screen and every path through them

Pick a provider and the second question opens. Yes, and Configure git lights up; No, and the dialog first shows how to make an empty repository. Either way leads to step two, where pasting the remote URL turns Continue on, and to step three, where the key goes on the repository and a tick confirms it has write access before it connects.

Testers connected first time, and after release 72% more did

In user testing, people connected on their first try. After release, 37 of the 130 builders who started connecting on the new flow got through, against 37 of 224 on the old one: 28.5% against 16.5%, about 72% more.

The flow, as it ships

The shipped flow as a walkthrough, from picking a provider to a connected repository.

The shipped flow, captured as a walkthrough. Take it end to end, from picking a provider to a connected repository.