By Peter Ramsey

19 Aug 20

Buying Bitcoin on Coinbase Company Logo
Coinbase6 min read
Listen

Buying Bitcoin on Coinbase

Buying Bitcoin on Coinbase Featured Image

From a user experience perspective, buying, storing, trading and selling cryptocurrency—like Bitcoin—is still a pretty rough experience.

There’s a steep learning curve, terminology to understand and a regular supply of horror stories about hackers stealing cryptocurrency to make the experience uncomfortable for most.

Coinbase is on a mission to change that.

They want to make buying cryptocurrency feel safer and simpler, in the hope that it entices new investors, who would otherwise be put off by the idea of managing their own digital wallet.

But how could the user experience be better? Is it good enough?

Summary

  • 🐎

    Avoiding the ‘get started’ trap.

  • 🧏‍♂️

    Why you need a feedback architect.

  • 👨‍🦰

    Be aware of the header.

Please rotate your device to view this slideshow

Note, this won’t work if ‘rotate: lock’ is on in your device settings.
5739
5740
5741
5742
5743
5744
5745
5746
5747
5748
5749
5750
5751
5752
5753
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764
5765
5766
5767
5768
5769
5770
5771
5772
5773
5774
5775
5776
5777
5778
5779
5780
5781
5782
5783
5784
5785
5786
5787
5788
5789
5790
5791
5792
5793
5794
5795
5796
5797
5798
5799
5800
5801
5802
5803
5804
5805
5806
5807
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820
5821
5822
5823
5824
5825
5826
5827
5828
5829
5830
5831
5832
5833

👇

That’s all for the slideshow, but there’s more content and key takeaways below.

Slide 1 of 96

3 UX takeaways

1. The 'get started' trap

The Coinbase app really doesn’t have any onboarding. But, they do have something that I’ll refer to as the ‘get started’ trap.

A ‘get started’ trap works like this:

🙅‍♂️

1. Lack of onboarding

The user is left wondering what to do.

🤞

2. Tempting action that promises ‘help’

A CTA that says something like ‘get started’ or ‘learn more’.

🤯

3. Pushes you in the deep end

The CTA doesn’t offer guidance at all, and just starts an action. i.e., making a payment or choosing a monthly subscription.

In effect, this is where something promises a helping hand, but is nothing more than a shortcut to doing what the company wants you to do.

After signing up to Coinbase—and verifying your ID—you’re greeted with this very tempting ‘Get started’ button.

null image

But clicking it doesn’t offer any help at all. Instead, it immediately asks you how much Bitcoin you’d like to buy. And, it defaults to Bitcoin—removing the choice about which cryptocurrency you’re interested in.

This doesn’t help you get started with Coinbase, and the CTA is nothing more than an illusion—an onboarding trojan horse.

The key takeaway here is that Coinbase’s users probably do want to buy some cryptocurrency—that’s why they signed up.

But they also want to understand how Coinbase works, and to be sure that it’s the platform for them, before entering their card details.

If Coinbase is going to keep capturing new users, they’ll need to appeal to people who haven’t already decided that they’re ready to purchase Bitcoin.

2. Feedback architecture

In the physical world, you almost always get feedback which lets you know if something worked or not—without any additional effort from that item’s creators.

For example, if you used a faulty vending machine, which didn’t dispense your drink, you’d know pretty quickly. You wouldn’t need to see an error message—the lack of drink is your error message.

null image

But with software, someone needs to be the architect of this feedback. These error messages need to be created and implemented.

When these moments haven’t been implemented properly, you end up with a confusing and broken experience. This is exactly what happens when adding a new card to your account on Coinbase.

Click 'add card':

Click 'add card':

Then:

Then:

You add a card, see a spinner and then get put on the homepage—without any attempt to tell you if adding your card was successful or not.

I don’t need to explain why this is bad UX, but rather I can point to a few reasons why this type of mistake is so common:

📋

1. Volume of possible states

The number of possible outcomes for a medium-sized SAAS product is enormous, and it grows with every new feature.

🔬

2. Inadequate testing

Maybe you can add your card in 4 different places, but only 3 of these journeys were tested at the last deployment.

🤷‍♂️

3. Unclear responsibility

This types of UX mistake will often slip through ‘job role’ cracks. Is it the designer’s job? The product manager’s? The developer’s?

3. No surprises, please

As a designer, I always aspired to create something unique. Perhaps a new homepage layout that nobody had seen before (and that didn’t just copy Stripe).

But, the truth is: designing the best experience isn’t about being unique, it’s about being easy.

And guess what feels really easy to use? Things that feel familiar.

As an example; which of the two designs below do you feel is easier to use?

Option A:

Option A:

Option B:

Option B:

Objectively, I could put forward a half-reasonable argument why the second option is okay. (It’s not better, but I’ve used an extreme example on purpose).

The point is, we’re so used to keyboards being at the bottom of the page, that any deviation from this design would be confusing, a shock and very difficult for people to come to terms with.

These rules are often unspoken, and mostly subconscious. But, here’s one that I think you’ll appreciate: almost every app screen can be split into two sections:

null image

😴

1. The header

This is where predictable stuff goes. Like the company logo, back button, page title, breadcrumbs and the device settings (battery , signal etc.).

🍯

2. The actual page

This is the bit that I should pay most attention to.

This isn’t true all the time, but it’s true often enough that when people use apps they don’t typically even read what’s in the header.

Which is where Coinbase make a mistake: the only way you’d know that you were buying Bitcoin on this page, is if you read the page title—which is in the header.

The natural first-viewing of this screen is messy, because people try to work out what they’re doing from the body of the content, and eventually work their way up.

I’m not suggesting that you can’t put things in the header—not at all—rather, that the main body of the page should also make it clear what you’re doing.

You’ve finished this study

+1

Become a BFM+ member to track your progress, create a library of content and share learnings within your team.

You’ve finished this study

Other studies picked for you

How Product Psychology Could Stop Uber Drivers From Stealing

How Product Psychology Could Stop Uber Drivers From Stealing

How upstream thinking could reduce stolen orders, avoid tip-baiting and increase driver happiness.

How to Reduce Churn by Doing Your "One Thing"

How to Reduce Churn by Doing Your "One Thing"

When it comes to onboarding, it's often more effective to do just one thing (really damn well).

BFM+ Exclusive

Unlock all 77 case studies with BFM+

View Plans
A Masterclass in User Activation (96% of them)

A Masterclass in User Activation (96% of them)Preview this content

Discover the art of setting a goal and then using that to immediately create the perception of success.

All of the UX analysis on Built for Mars is original, and was researched and written by me, Peter Ramsey.

Never miss the free UX analysis

Free case studies, the moment they’re released, plus a digest of the best UX Bites every few weeks.