跟讀練習: Why React Native apps make all the money - 通過影片學習英語口語

選擇練習模式

每種模式都會開啟全屏練習室。

117 句

如果句子過短或過長，請點選 Edit 進行調整。

Oh yeah, great.

Can I get a show of hands how many of you have used React Native?

Put your left foot up if you also use RevenueCat.

Yeah, it doesn't matter.

But for those people who mostly are, I guess, web developers here in the audience, I'm guessing at least, be not afraid.

This talk will start mobile first, but then it will take a sudden twist to also be about web.

But yeah, let's get into it.

Why React Native apps make all the money?

So before we get into all of that, I'm Perttu.

I'm a developer advocate at RevenueCat, where I help people, developers, mostly make money with their apps.

You can find me on X with that handle

and you can also find all that and the materials actually for the slides from my website, which is just myfirstname .dev.

So, React Native apps make all the money.

And what that means, earlier this year, RevenueCat, we analyzed all the apps that we have on our platform, so we do app monetization,

And that ended up being like 75 ,000 apps making over $10 billion in revenue.

And we compared the different, like, because you can use RevenueCAD on different technologies, so native apps, Swift and Android,

React Native, Flutter, and then all the other, for example, Cordova and whatnot.

And we compared those apps, like, which one of those apps, like, make a lot of money,

which make less money, which monetize better, which monetize the best.

And it turns out that

React Native actually wins in almost all of these categories,

which is a might be surprising and certainly something that gets all the native developers very angry.

So first, if we take the download to page,

so how many apps when they're downloaded from the app actually end up being paid for by the customers, React Native wins in that,

like clearly, as you can see.

It not only wins over Flutter and other, but also the native apps.

Same goes when you're comparing how much money per install of the app makes.

React Native still wins.

Then also if we look at the lifetime value per customer of using the app, that too, React Native wins.

So it wins in all of these three categories.

And the only time it loses is when you start to look at the year one retention.

Now you could speculate a lot of reasons why this happens mostly it could be for example

that after users

when they download the app they pay for it they get all the value

they needed it inside of a year

and that's why they don't see value income

and using it after a year but

if there's something to improve this could be the category

that make react native apps monetize also a year after being downloaded and purchased

but then the real question is of course like why does this happen why does react native performs

so much better and there's an interesting article in the pragmatic engineer newsletter about multi platform development

or cross -platform development which basically says that companies are choosing technologies for

which it is easy to hire like really good developers

and turns out

that in most cases that's actually react native it is way harder to hire good developers in same amount of quality,

for example, to Flutter and Swift.

So there must be also a reason, like, why is React Native then the technology chosen for this?

Well, it's all about, like, it being basically a tool set for speed.

So great apps are about delivering value fast to the market because being the time on market beats timing the market.

And in order to also, like, deliver value fast, you need to learn fast.

With React Native, that means you have, for example, cross -platform reach.

So you get iOS, Android, web, whatever you're building for.

Basically supporting everything that you need to have apps in.

And also the native feel.

So apps built in React Native for iOS actually feel like iOS apps.

Same goes for Android.

They feel like Android apps.

And if you're building for web with React Native, that feels like an actual web app and not just some bundled together hack of a mess,

like, for example, Flutter for Web tends to be.

And then this then leads to faster development and time to market.

And of course, there's then the last point, the single code base, which allows you to get feature parity.

You don't end up spending a lot of time developing individual features for different platforms in separate teams.

but you can actually have one single team building multiple different platforms.

Which then brings like monetization priority.

So when you have all the features being same on all the platforms, you can way easier monetize that app,

put subscriptions on it, put ads on it, whatever is your monetization strategy.

So it unlocks like a whole new level that would have not been previously possible if you had been building apps

with different technologies for different platforms.

But how do you then make it so that your apps makes money.

Simple as that is like use RevenueCat.

So we provide everything when it comes to subscriptions and in -app purchases as a service, so back in a box.

We started out with in -app purchases for iOS and Android, but you can now use us in web as well.

So that means that under the hood, we use either

Stripe or Battle to handle the payments, and then you just get the subscription management.

We have SDK for all the major platforms.

We handle the store quirks and validation of receipts.

And then on top of that, we provide stuff like paywalls to monetize better.

We have analytics.

We allow you to target different customer groups and experiment.

And we bring all that together, allow you to optimize, build things that, well, developers might not appreciate as much,

but definitely the people in business appreciate being able to do all kinds of experimentation with the pricing.

And it's all displayed in a very nice looking UI, where you can see how your revenue goes to the moon.

With Expo, if we want to look at what this means in practice with Expo,

the value promise could be said that you can build three platforms with a single code base.

Well, with RevenueCat, you can now monetize three platforms in a single code base.

And it's actually pretty simple.

So you take, for example, an existing Expo app, Expo React Native app, and you just do NBX Expo install

React Native purchases, which is our React Native purchases SDK.

In code, the setup is, I would call, annoyingly simple, because there's not actually much to show.

You initialize the SDK, you connect the platforms you're going to use, so iOS or App Store Connect and Google Play Console

and Stripe, for example and we give you a specific platform API key for those, which you then initialize in the client SDK.

Then you purchase a subscription, either using our paywall or with this purchase package method that we provide.

And then you check that the user entitlements.

So after users have purchased something, we keep track what they're entitled to based on that purchase.

And we call those in revenue cash as entitlements, which basically just tells us that,

okay, the user is eligible for example pro access encode is pretty simple

so you call use effect for example at the root of

your application with the specific uh platform keys for different platforms

you can use for example the platform os to check that you're which platform you're using the key for

100

and that's all that's required at

101

that point we will start running the native code required for ios

102

and android and also the web code required for example stripe stripe billing and then when When you make a purchase,

103

you can either call the purchase package and show those packages or products that you have in your app by yourself,

104

check that user successfully purchased that and show the UI based on it.

105

Or you can call the RevenueCat UI library with the present paywall,

106

which will show this nice -looking paywall that you can actually customize in our dashboard.

107

It has over 30 example paywalls and you can also build a custom paywall completely in the web UI,

108

and it's rendered natively.

109

And once you've purchased or the customer has purchased something, you could just call purchases get customer info to get what this specific customer purchased.

110

And we keep track of all the customers, so we have the data for that,

111

to tell that, okay, this user on this device is actually the same user that is also using the web application.

112

So then if you have a user using your app, your product, on web, iOS,

113

and Android, just giving us the user ID that you use, for example, that user will allow RevenueCAD to tell you what the user has purchased.

114

And in simplicity, that's it.

115

You can find an example project and a tutorial on how to do

116

that at revenuecat .com and all the other information also from that QR code.

117

Thank you.

下載應用

流利口語所需的一切

AI 發音評分逐句打分

音標練習掌握每個音

詞彙學習建立你的詞庫

詞彙遊戲邊玩邊學

掃碼

Download on theApp Store Get it onGoogle Play

同頻道

React Conf 2025 React Native Keynote

Daily ConversationUniversity StudentsWorking Adults

FOR YOU

本課的詞彙與口語要點

這節口語課以影片“Why React Native apps make all the money”為素材。影片中反覆出現的詞有：app, native, react, platform, example。這段影片共有 117 個句子、1556 個單詞可供跟讀。講話部分時長為 9:14。說話人語速自然，每分鐘約 169 個詞，接近日常對話。 84% 的單詞屬於英語最常用的 3,000 詞，其餘的詞建議在練習前先學一下。

影片中的重點詞彙

影片中 15 個值得學習的單詞，附發音和釋義：

單詞	發音	釋義
android 名詞	/ˈænˌdɹɔɪd/	人形機器人 /人形機器人, 仿生人
subscription 名詞	/səbˈskɹɪpʃən/	訂閱 /訂閱, 預訂 /預訂
stripe 名詞	/stɹaɪp/	條紋 /條紋
package 名詞	/ˈpæk.ɪd͡ʒ/	包裹, 包
compare 動詞	/kəmˈpɛɚ/	比, 比較 /比較
hire 動詞	/ˈhaɪɹ/	租借, 出租
connect 動詞	/kəˈnɛkt/	連線 /連線
install 動詞	/ɪnˈstɔl/	安裝 /安裝
custom 名詞	/ˈkʌstəm/	習慣 /習慣, 習俗 /習俗
priority 名詞	/pɹaɪˈɒɹɪti/	優先權 /優先權, 更重要的事
sudden 形容詞	/ˈsʌd.ən/	突然, 急劇 /急劇
lifetime 名詞	/ˈlaɪf.taɪm/	一生, 一輩子 /一輩子
experiment 名詞	/ɪkˈspɛɹ.ə.mənt/	實驗 /實驗
slide 名詞	/ˈslaɪ̯d/	滑梯
twist 動詞	/twɪst/	扭, 搓

影片中出現的短語動詞

單詞	釋義
end up 動詞	到達
turn out 動詞	原來 /原來

影片中的語法

說話人最常用的結構，並附上影片中的原話：

結構	影片中的用法
現在完成時 have/has + 過去分詞 — 過去發生但與現在仍有關聯的事	have purchased · you've purchased · has purchased
被動語態 be + 過去分詞 — 強調發生了什麼，而不是誰做的	being paid · being downloaded · could be said
定語從句 who / which + 從句 — 補充說明人或事物	people who mostly · website, which is · purchases, which is

需要注意的發音

說話人用了 15 次縮略和弱讀形式，例如 you're, I'm, don't。請按聽到的簡短形式來說。

“sh” 和 “zh” 音: subscription /səbˈskɹɪpʃən/, retention /ɹɪˈtɛnʃən/, validation /ˌvæl.əˈdeɪ.ʃən/, monetization /ˌmɒnətaɪˈzeɪʃən/, initialize /ɪˈnɪʃəlaɪz/
長單詞——注意重音位置: developer /dɪˈvɛləpɚ/, entitlement /ənˈtaɪtəlmənt/, successfully /səkˈsɛs.fə.li/, priority /pɹaɪˈɒɹɪti/, experiment /ɪkˈspɛɹ.ə.mənt/

中文母語者容易讀錯的音：

/v/ — 不要讀成 /w/，上齒輕觸下唇: developer /dɪˈvɛləpɚ/, advocate /ˈæd.və.kət/, validation /ˌvæl.əˈdeɪ.ʃən/, natively /ˈneɪtɪvli/
詞尾子音 — 要讀清楚，後面不要加母音: react /ɹiːˈækt/, android /ˈænˌdɹɔɪd/, stripe /stɹaɪp/, package /ˈpæk.ɪd͡ʒ/, connect /kəˈnɛkt/
/æ/ — 嘴張大，不要讀成 /e/: react /ɹiːˈækt/, android /ˈænˌdɹɔɪd/, package /ˈpæk.ɪd͡ʒ/, advocate /ˈæd.və.kət/, analyze /ˈæn.əˌlaɪz/

如何用這段影片練習

先完整聽一遍影片，不要開口，記下不認識的單詞。
先用 0.75 倍速逐句跟讀，熟練之後再回到正常速度。
錄下自己的聲音並與原聲對比，特別注意 android, subscription, stripe 這類單詞。

什麼是跟讀法？

跟讀法 (Shadowing) 是一種有科學依據的語言學習技巧，最初開發用於專業口譯員的培訓，並由多語言者Alexander Arguelles博士普及。這個方法簡單而強大：您在聽英語母語原聲的同時立即大聲重複——就像是一個延遲1-2秒緊跟說話者的影子。與被動聽力或語法練習不同，跟讀法強迫您的大腦和口腔肌肉同時處理並模模擬實的講話模式。研究表明它能顯著提高發音準確性，語調，節奏，連讀，聽力理解和口語流利度——使其成為雅思口語備考和真實英語交流最有效的方法之一。

影子跟讀法: 閱讀完整分步指南 →

跟讀練習: Why React Native apps make all the money - 通過影片學習英語口語

選擇練習模式

下載應用

同頻道

React Conf 2025 React Native Keynote

推薦影片

The Only SaaS Moats Left in 2026

Is React Native Dead? Shopify Is Leaving

The future unfolds! How to optimize Android apps for adaptive layouts

My 4.9-Star iOS App Is Actually a Website: Here’s How I Built It

10 Essential React Native Tips Every Developer Must Know

Did Anthropic Kill Git?

The hottest programming skill in 2026

Video

The plan to break apart Google... RIP Chrome

Red Note Q&A - Half a Million Followers and Monetizing

How I deploy serverless containers for free