HomeVideos

The Onboarding Behind My $40K/Month App (Full Breakdown)

Now Playing

The Onboarding Behind My $40K/Month App (Full Breakdown)

Transcript

400 segments

0:00

If you're building a mobile app right

0:01

now, there is one thing that will make

0:04

or break your revenue. And it's not your

0:06

idea, your design, or your marketing.

0:08

>> Your onboarding is the single most

0:10

important part of your app because an

0:13

app is nothing more than a sales funnel.

0:15

>> This is Mao. He built a mobile app that

0:17

makes over $40,000 a month, and he is a

0:20

genius when it comes to building

0:23

onboarding flows that convert.

0:25

>> Every screen before hitting the paywall

0:27

is just building a case of why the user

0:30

should pay you.

0:30

>> So, I asked him to come on to the

0:32

channel to do a full screen-by-screen

0:34

breakdown of his entire onboarding flow

0:36

that turned his app into a $40,000 per

0:39

month business. He's going to walk us

0:41

through the psychology, the design

0:43

choices, and why every single screen is

0:46

placed exactly where it is. By the end

0:48

of this video, you're going to learn why

0:50

making your onboarding longer can

0:52

actually triple your conversions, the

0:54

exact screen that gets one in eight

0:57

users to leave a review, and the

0:59

psychology tricks that convince users to

1:01

buy before they ever even hit the

1:04

paywall. If you're building anything in

1:05

mobile, this might be the most important

1:07

video you'll watch this year. All right,

1:10

let's get into it. Welcome to Starter

1:11

Story Build.

1:14

All right, guys. Before we dive in, we

1:15

talked to Mao for 40 to 50 minutes, and

1:18

we couldn't include everything in this

1:20

final video. So, after watching this

1:22

video, if you want to download the

1:23

extended version of Mao's onboarding

1:25

guide that has all of his screens, all

1:27

the tactics, and everything, just head

1:29

to the first link in the description to

1:30

grab it for free. All right, let's dive

1:32

in. Okay, Mao, welcome back to the

1:34

channel. You did an awesome video about

1:37

this awesome app that you built, and we

1:39

asked you to come back to talk about one

1:40

thing that a lot of people asked about

1:41

in the comments, which is onboarding.

1:43

But, if you could remind us real quick

1:45

about who you are, what you built, and

1:47

how your app is doing now.

1:49

>> Yeah, of course. Thanks for having me

1:50

on, Pat. So, my name is Mao Bern, and I

1:53

built a mobile app that makes over 40K a

1:55

month. And I don't have, you know, a

1:57

design background or a UX background at

1:59

all. I studied finance in college. I'm

2:01

just a guy who taught himself about AI.

2:03

But, what I do have is the experience of

2:06

building a few mobile apps from scratch,

2:08

just completely obsessing over what

2:10

actually makes them convert. Through

2:12

trial and error, I started iterating my

2:14

onboarding since studying what I

2:16

considered to be, you know, the best

2:17

onboardings in the market. And, you

2:19

know, everything changed, and that's

2:20

when my app started skyrocketing.

2:22

>> I hear a lot of people on the channel

2:23

talk about this onboarding and how

2:25

important it is with mobile apps, but

2:27

could you just explain what that means?

2:28

Like, what is onboarding and why is it

2:31

so important?

2:32

>> Yes, I'm going to sound like a broken

2:33

record, but your onboarding is the

2:36

single most important part of your app

2:38

because an app is nothing more than a

2:40

sales funnel. When a user first opens

2:42

your app, they have zero context about

2:45

what your app does. They don't know, you

2:46

know, if it's going to solve their

2:48

problem. And this is why the onboarding

2:50

matters even more right now. Every

2:52

screen before hitting the paywall is

2:54

just building a case of why the user

2:56

should pay you.

2:57

>> Okay, cool. I want you to give me the

2:58

high-level overview of how to set up an

3:00

onboarding. What are like the pillars of

3:02

onboarding that pretty much any app

3:05

should have?

3:05

>> So, onboardings are like a story. They

3:09

have an introduction, a climax, and a

3:11

conclusion. Every screen serves a

3:14

purpose, and most of them have nothing

3:16

to do with the product itself. They're

3:18

about making user feel heard, making

3:20

them reflect, and making them convince

3:22

themselves that they need your app. So,

3:24

just keep that in mind as we go through

3:26

this.

3:26

>> Okay, cool. So, let's go through the

3:28

three pillars. So, it's introduction,

3:30

climax, and conclusion. Let's dive into

3:33

the introduction side of things right

3:35

now. Can you walk me through all the

3:37

concepts in here and all the screens of

3:39

your app?

3:40

>> So, I actually have four principles in

3:42

the introduction section of the

3:43

onboarding. The first one being that you

3:45

need to frame the problem and solution

3:47

in the first three screens of your app.

3:49

The sooner the better, cuz confusion

3:51

honestly just kills conversions. And

3:53

users need to know exactly what they're

3:55

getting themselves into. In Prayer

3:56

Lock's case, the way we do it is we

3:58

welcome you, and then in the second

4:00

screen, right there, we tell you, "Hey,

4:01

like, did you ever feel like your phone

4:02

gets more attention than God?" We're

4:04

already framing the problem of phone

4:06

addiction, social media addiction. And

4:08

then in the third screen, we give you a

4:10

solution in very simple terms. Prayer

4:13

Lock helps you put God first. So, right

4:15

there, we're framing the exact problem

4:17

the user has. And the user knows exactly

4:19

what they're going to get from the app.

4:21

The second principle of the introduction

4:23

is to give the users an aha moment in

4:26

under a minute. Hit them with a stat or

4:29

realization that is very personal to

4:32

them. The way we do that in Prayer

4:34

Lock's case is actually very unhinged

4:36

cuz we ask you first for your name, then

4:39

we ask their age and how long they are

4:41

on their phone each day. And whatever

4:44

they answer, in the next screen, they

4:46

always get a stat that kind of just

4:48

blows them away. Which is on average,

4:50

they're going to use their phone 16

4:52

years over their lifetime. But then we

4:54

tell them, "Hey, don't worry. We are the

4:56

solution." Again, do you have just 5

4:58

minutes for God each day? Let's build a

5:00

plan for you. And then the next

5:01

principle of the onboarding is to ask

5:03

questions. Now, most people think that

5:06

the questions are so that you as the app

5:08

maker get to know more about your users,

5:12

but that's not the case at all. What you

5:13

actually want to do is to make the users

5:16

convince themselves that this is an app

5:19

that they need. In Prayer Lock's case,

5:21

again, we just ask very personal

5:22

questions that we already know the user

5:24

struggle with, like thinking bigger,

5:26

what does a thriving faith look like to

5:28

you? And each answer choice is very

5:29

deliberate. The fourth principle of the

5:31

introduction is that you need to reflect

5:35

the user's answers back at them. So, if

5:37

in your onboarding, you ask a question

5:39

about social media addiction, and they

5:40

tell you, "Yes, I have social media

5:41

addiction."

5:43

In the next screen, you would say, "Hey,

5:45

we feel that you have social media

5:46

addiction." So, in PrayerLock's case, we

5:48

ask him, "What do you want to achieve

5:50

with PrayerLock?" They say, "I want to

5:51

put God first before my phone, build

5:53

consistent prayer habits, etc." We just

5:55

spit those same answers right back at

5:56

them in the next screen. And this sounds

5:58

silly, but what this does is makes the

6:00

user feel heard, makes the user feel

6:02

like this is going to be a personalized

6:04

experience for them. And then something

6:05

to keep in mind, longer onboardings will

6:07

do better. In PrayerLock's old

6:09

onboarding, we had only around 20

6:11

screens, and our conversion rate with

6:13

free trial was around 3%. When we

6:16

updated the onboarding to be more than

6:19

10 to 15 minutes long depending on the

6:20

user, our conversion rate 5x'd to 15%.

6:24

The reason this happens is because of

6:26

something called loss aversion. And

6:28

people in general would rather not lose

6:31

than win something. So, by the time they

6:33

get to the paywall, they're thinking,

6:35

"Hey, I already invested 10 minutes, so

6:37

I might as well just give it a shot and

6:38

start the trial. Why not?"

6:40

>> Mal's onboarding principles are

6:42

incredible. If you're building anything

6:44

in mobile, this is gold. We actually

6:46

ended up recording a lot longer than

6:48

what we could include here in this

6:50

Starter Story Build YouTube video. So,

6:52

we actually asked Mal to write up a

6:53

detailed guide on how to create an epic

6:56

onboarding flow that converts. And

6:58

inside we go on an even deeper dive into

7:00

each screen he sets up and why. He'll

7:02

break down every single screen, why it

7:04

works, and how you can implement it

7:06

inside your app. Just head to the link

7:08

in the description and download it for

7:10

free. All right, let's get back into the

7:11

video. Okay, let's move to the second

7:14

pillar of onboarding. What did you call

7:16

this section? Let's dive in.

7:18

>> So, the second part of your onboarding

7:20

is the climax. And again, I have two

7:23

principles for the climax part of the

7:24

story. As in any story, the climax

7:27

should be the most exhilarating, fuse

7:29

with the most fun, the most entertaining

7:30

part. The easiest way to get that done

7:33

is through the first principle. Let the

7:35

user actually try your main feature

7:38

during the onboarding. In PrayerLock's

7:40

case, the way we do it is we ask you two

7:42

questions and then we generate a prayer

7:44

for you. Then the second principle of

7:46

the climax on your onboarding is getting

7:48

them to leave a review. And the screen

7:50

that actually gets them to convert on a

7:52

review is showing some type of

7:54

gamification aspect, some type of

7:56

streak.

7:57

In our case, we show their first day

7:58

streak of their prayer journey with a

8:00

little fire animation. But after showing

8:03

that, we then hit them with the review

8:05

model. And one of the reasons why

8:06

reviews are so important is because most

8:09

users will actually never pay,

8:11

especially if it's a hard paywall app.

8:14

So a review is the next best thing they

8:16

can give you. So don't waste that moment

8:18

by showing the review model either too

8:20

early where the user still getting

8:22

familiar with your app or too late where

8:25

the emotional peak has already died

8:28

down.

8:29

>> Wow, this is super cool. I'm actually on

8:31

the App Store listing right now and you

8:33

have like thousands and thousands of

8:34

reviews. Why get so many reviews? What's

8:37

the purpose of having a lot of reviews?

8:38

Does it bring you more revenue or why do

8:40

that?

8:41

>> So actually reviews do two things for

8:42

you.

8:43

The first one and the most important one

8:45

is social proof. When you're about to

8:47

download the app and you know, in the

8:48

App Store and you see 13,000 reviews,

8:51

like that gives you much more confidence

8:53

that this is you know, something that

8:54

you might want to download cuz a lot of

8:56

people have done it too. And then the

8:57

other reason is for ASO. You know, it's

8:59

just how well you rank on the App Store.

9:02

So you want to make sure that you're at

9:03

least ranking at number one in your

9:06

app's name keyword. So my app is called

9:08

Prayer Lock. I want to make sure I'm

9:10

number one for Prayer Lock.

9:12

>> Okay, so let's move to the next pillar.

9:14

What's the final pillar of a great

9:16

onboarding? Can you walk us through

9:17

that?

9:18

>> Yeah, so the last pillar of your

9:19

onboarding is of course the conclusion.

9:21

And for the conclusion, I have three

9:23

principles. The first one is to show

9:24

them a summary of their journey. You

9:26

know, where they are, where they want to

9:28

go and how your app gets them there. And

9:30

a lot of this stuff sounds very

9:32

repetitive because in the introduction

9:34

of the onboarding, we were actually

9:36

reflecting back the answers. But you

9:37

want to keep doing that. Remember,

9:39

people, especially young people, have

9:41

short attention spans. So, it's a good

9:43

thing to be repeating yourself

9:44

constantly. In our app's case, we

9:47

actually first show them a little

9:48

summary here, tell them, "Hey, you're

9:50

going to have a prayer habit in 30

9:52

days." Try to always connect your app to

9:54

a certain habit that they can achieve in

9:56

an X amount of days. And then the second

9:58

and actually controversial principle is

10:00

to tell your users up front that your

10:03

app is paid, only if you have a free

10:05

trial. If you don't, I would say skip

10:07

this cuz you might lose a lot of people

10:09

there. And then compare your app against

10:11

something they already pay for in real

10:13

life. In Prayer Lock's case, we have

10:15

this screen where we compare the cost of

10:18

one coffee a month to spiritual peace.

10:20

So, you want to make the user be

10:22

thinking of your app as something that

10:24

is very worth it compared to, you know,

10:26

some other usual thing that they do with

10:27

their day. And then the third and last

10:29

principle is to try to get the user to

10:32

say that they are committed to using

10:34

your app. In our app's case, we

10:36

literally just asked them, "Hey, how

10:37

committed are you to making this feature

10:39

happen?" And usually, we have found that

10:41

95% of them will either answer extremely

10:43

committed or very committed. If they

10:46

were to answer any other thing, we have

10:47

custom copy for that situation. And then

10:50

as your last screen, I would recommend a

10:53

social proof screen, like the one we

10:54

have here. And yeah, that's it for the

10:56

onboarding. After of course, you have

10:58

your paywall, but don't overthink this

11:00

part too much. You know, the paywall is

11:02

actually not as important as people

11:04

might think, at least in the beginning.

11:06

The only thing I would say you should

11:08

add in your paywall is a notification

11:10

reminder 1 day before their trial ends.

11:13

That's like the only thing I would say

11:15

to focus on for your paywall.

11:17

>> Okay, cool. I think a lot of people

11:18

watching this might be wondering, "Okay,

11:20

this is cool. You showed me your

11:21

onboarding. This works great for you.

11:23

But what about everyone else that's

11:24

building apps? Will this work for them?

11:26

What changes would you make?" Uh

11:30

what would you have to say about this?

11:31

>> So, actually, I wasn't the first one

11:33

that did this. I took inspiration from

11:35

other apps like Twitter, like CalA I.

11:38

You know, a lot of these apps already

11:40

have very long onboardings and already

11:42

have the principles that I just

11:44

described. And if you're thinking it

11:46

might not work for your app, just keep

11:48

in mind that CalA I was just acquired

11:50

for probably multiple nine figures and

11:52

they have one of the longest onboardings

11:54

in the mobile app space. So, it

11:55

definitely works for your app. Just make

11:57

sure you follow the principles that I

11:59

laid out.

12:00

>> Okay, so last question I have, but

12:01

before I want to touch on it. You might

12:02

be watching this and thinking, "Okay,

12:04

this is cool, but how do I get users?"

12:05

Well, I'll put a link in the description

12:06

down there. Go watch our previous

12:08

starter story interview with Mao where

12:10

he talks all about that, uh, social

12:12

media and how he drives a lot of people

12:14

to actually check out the app and then

12:16

go check out the onboarding. So,

12:17

definitely check that out. Last question

12:19

that I have for you, Mao, is for anyone

12:21

that is building an app, but they're

12:23

want to figure out how I could do

12:25

onboarding uh, and do what you've done,

12:28

which is built an app from basically

12:29

zero to $40,000 a month. What would be

12:31

your main piece of advice?

12:32

>> So, I would say before you touch your

12:34

product, before you add useless

12:36

features,

12:37

obsess over two things. Obsess over

12:40

marketing first and then over your

12:43

onboarding. Do that until you hit at

12:46

least a 10% download to trial rate. Then

12:48

everything else comes after that.

12:51

>> Thanks for coming on, Mao, sharing all

12:53

this. I think people are going to really

12:54

enjoy it and uh, put a note in the

12:56

comments what you want to see Mao talk

12:58

about next. We can talk about

12:59

distribution, we can talk about

13:01

anything. So, put a comment in there.

13:02

Thanks, Mao, for coming on and sharing.

13:04

>> Of course. Thank you, Pat.

Interactive Summary

This video features app developer Mao Bern, who explains how his mobile app, PrayerLock, reached over $40,000 in monthly revenue by optimizing his onboarding flow. He details the three pillars of onboarding—introduction, climax, and conclusion—and explains why longer onboarding experiences, when built around user-centric psychology, can significantly increase conversion rates. Key takeaways include framing the problem and solution early, using personalization, leveraging loss aversion, and focusing on marketing and onboarding before adding unnecessary product features.

Suggested questions

4 ready-made prompts