AI Engineer World's Fair 2026

Why LLM Recommenders Will Be AI's Biggest Consumer App — Devansh Tandon, Meta

Read the talk

Why LLM Recommenders Will Be AI's Biggest Consumer App

Devansh Tandon connects recommendation scaling to a practical recipe: compress a catalog into semantic tokens, teach a model to understand those tokens alongside English, and train it to choose content. The result could make feeds easier to steer—and much cheaper to serve than generating every piece of content.

From a talk by Devansh Tandon

At a glance

Ideas worth remembering

  • Recommendation scaling connects model size, data, and compute to offline quality, then tests whether that quality becomes engagement and revenue.

  • Semantic IDs give content shared, learnable structure and compress it enough to fit longer interaction histories into the model’s context.

  • English-and-catalog pre-training supplies meaning; recommendation post-training teaches selection. A user’s language request can then join their interaction history as a direct input.

  • The economic advantage of a feed comes from selecting pointers to creator-supplied content: the model can enable substantial consumption without generating every token of that content.

Scaling the model changes what the feed can learn

Devansh Tandon, who leads Meta Recommendations Research, opens with two claims: recommendation systems follow scaling curves much like LLMs, and LLM recommenders will become one of AI’s biggest consumer applications. Recommendation, in his view, is still early in its climb. Follow the opening at 0:28.

Source frame: Scaling the model changes what the feed can learn
Source frame: Scaling the model changes what the feed can learn

The starting point is the power-law relationship familiar from language-model scaling: increasing model size, training data, and compute produces a predictable decline in loss. That predictability matters because it gives another training run an economic rationale. A company can estimate how additional compute might improve quality rather than treating each larger model as an entirely new experiment.

Recommendation applies the same idea to a different output. More data, compute, and model capacity improve offline recommendation quality; production launches then test whether those improvements become engagement and revenue. Tandon points to HSTU, a 2024 paper, and a subsequent Meta paper as examples of this scaling behavior. The distinction between offline quality and product impact matters: a better evaluation result is an intermediate step toward a better feed.

For Instagram, the concrete changes included simplifying the ranking architecture so models could scale efficiently, doubling the length of user interaction sequences used in training, and making each interaction richer. Tandon places these changes alongside reported Reels watch-time growth of 30% year over year. That is a product-level figure, not an isolated estimate of how much any one model change contributed.

Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:12 · section reference included

“Tokens in, engagement out” pays for the next model

What connects a scaling curve to a consumer business? Tandon’s phrase is “tokens in, engagement out.” Training produces a model; inference uses it to recommend content; better recommendations draw engagement through daily use and time spent. Advertising or subscriptions turn that engagement into revenue, which pays for another training run. Each successful move up the scaling curve completes another circuit. Follow the flywheel at 4:59.

Source frame: “Tokens in, engagement out” pays for the next model
Source frame: “Tokens in, engagement out” pays for the next model

How does the next training run connect to the one before it? The loop below makes the funding path visible: recommendations lead to engagement, engagement leads to monetization, and revenue returns to training. The return arrow is what turns a sequence of model improvements into a repeating business loop.

How it fits togetherHow does recommendation improvement fund more training?

Train the recommendation model for the next turn of the loop.

The business loop turns model improvements into engagement, then revenue that supports another training run.

Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

4:59 · section reference included

Four recommendation paradigms can advance together

The next question is what gets scaled. Tandon organizes recommendation into four S-curves, each with a different source of improvement. These are overlapping approaches: companies can keep improving established systems while exploring models that understand language or agents that coordinate multiple recommendation steps. Follow the four paradigms at 5:39.

Source frame: Four recommendation paradigms can advance together
Source frame: Four recommendation paradigms can advance together
  • Traditional recommendation: Feature engineering and user and content embeddings do much of the work. Two-tower models and sparse rankers belong here. Tandon expects this approach to persist, with agents potentially taking over more feature engineering and research work.
  • LLM-inspired recommendation: Models borrow the scaling approach of LLMs, ideally learning end to end. HSTU is one example. Tandon places leading industry systems largely on this curve.
  • LLM-native recommendation: An existing base model brings language understanding and reasoning, then adapts to recommendation tasks.
  • Agentic recommendation: An LLM coordinates a loop that plans, retrieves, ranks, critiques, and refines recommendations before delivering them.

The distinction between LLM-native and agentic systems resembles the distinction between improving a coding model and improving the harness around it. A stronger model can make a better decision in one pass. An agent can call models again, critique the proposed recommendations, and revise them. Tandon presents that iterative approach as an emerging research direction rather than an established replacement for today’s feeds.

Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

5:39 · section reference included

Give the catalog a compact language

The LLM recommender recipe begins by creating a language for the catalog. Content becomes tokens; a base LLM learns to understand those tokens alongside English; recommendation training teaches it what to select for a user. The eventual output can directly identify items in the content corpus. Follow the recipe at 8:02.

Source frame: Give the catalog a compact language
Source frame: Give the catalog a compact language

Tandon expands this into a five-layer cake: semantic IDs, a base foundation model, pre-training, post-training, and light fine-tuning for a particular product surface. The base can be an open-weights model or an internal model. Most training compute is shared across products, so each surface does not need a model trained from scratch. Surface-specific adaptation sits on top of a common understanding of language and content.

Why use semantic IDs? Two properties matter independently:

  • Learnable structure: An arbitrary hash gives the model an identity to memorize. A semantic representation gives related content shared structure that the model can learn over. Tandon reports that teams have seen benefits even by replacing hash IDs with semantic IDs inside traditional recommenders.
  • Compression: User histories contain many items. In Tandon’s example, representing a three-minute Instagram Reel directly would take roughly 10,000 tokens; compressing it to about 10 tokens leaves room to consider a much longer sequence of interactions. The compact ID identifies the content rather than carrying its full audiovisual detail.

The tennis example makes the structure concrete. Similar Reels share their first three semantic tokens, while a final token distinguishes individual videos. Tandon suggests imagining the first token as sports and the next two as tennis. That is an intuition for the shared prefix, not a claim that every learned token has a clean English label. The useful relationship is that similar items share part of their representation while remaining individually addressable.

Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:02 · section reference included

Teach meaning first, then teach selection

Pre-training bridges the catalog’s semantic language and English through two complementary tasks. Follow the training examples at 10:42.

  • Connect an ID to a description: A prompt associates the semantic ID ABC with a video description, and the model produces text describing an iconic Wimbledon shot. Synthetic natural-language descriptions teach the connection between catalog tokens and content meaning.
  • Predict missing history items: Parts of a user’s semantic-ID sequence are masked. Predicting them teaches the model which videos tend to be watched together and in what sequence.
Source frame: Teach meaning first, then teach selection
Source frame: Teach meaning first, then teach selection

Post-training turns that understanding toward recommendation decisions. In the reranking example, the input includes user information and 30 candidate videos; the model chooses the top five recommendations. Its generated reasoning discusses topic interests such as comedy, food, DIY, and wellness, alongside engagement style and affinity for particular creators. Selection therefore combines several kinds of user evidence rather than matching only a topic label.

A bilingual model can express a rationale in English while selecting catalog items. That makes its stated reasoning inspectable: a developer can read how the model describes the user and compare that description with its choices. The example establishes access to generated reasoning; it does not establish that this text faithfully explains every internal cause of the ranking decision.

Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

10:42 · section reference included

A new interest can become an explicit recommendation input

Once English and catalog tokens share a model, language becomes a way to steer the feed. Instagram’s Your Algorithm example lets a user inspect the interests the system associates with them, add or remove interests, and communicate in natural language while consuming Reels. Likes and comments still supply behavioral evidence, but a user can also state a goal directly. Follow the steerable-feed example at 12:18.

Source frame: A new interest can become an explicit recommendation input
Source frame: A new interest can become an explicit recommendation input

The concrete change is an added interest in following the FIFA World Cup. The model receives both the existing user history and that new input, then decodes personalized recommendations; Tandon’s example points to a Messi clip. The new interest supplements the history rather than replacing it. This is how an explicit, timely request can change what the recommender selects while keeping personalization.

Where does the user’s request enter the recommendation path? The diagram shows the two inputs meeting at the model. The important change is that the user no longer has to communicate an interest only by accumulating interactions. A language input can join the history immediately. Tandon connects this direction to prompted playlists from Spotify, custom feeds from YouTube, and Ask DoorDash.

How it fits togetherHow does adding a World Cup interest change the input?

The evidence already available for personalization.

Existing history and an explicit new interest jointly condition the recommendation; the example output is a personalized Messi clip.

Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

12:18 · section reference included

Decoding a pointer costs less than producing the content

The ending returns to the business loop, now comparing content feeds with AI chat apps. Both invest in training, serve inference, earn engagement, and monetize it. Two questions determine how well that loop works: how effectively does training compute improve the model, and how effectively do inference tokens turn into engagement and revenue? Follow the economics comparison at 14:03.

Source frame: Decoding a pointer costs less than producing the content
Source frame: Decoding a pointer costs less than producing the content

The key economic difference is what the model must output:

  • Content feeds: The output is a semantic ID that points to an existing item. Creators have already supplied the video or other content. Model inference selects an address, and that selection can lead to a substantial period of consumption.
  • AI chat apps: The model generates the content itself. In Tandon’s comparison, a turn produces a few thousand tokens, each generated at inference time.

Model size adds another difference. Tandon describes feed models as using roughly 1–10 billion active parameters and chat models as using 10–100 billion. Together with the shorter output, this supports his estimate that content feeds can spend up to 100 times or more less on inference per hour of consumer engagement. The recording does not supply a benchmark methodology for that ratio, and its scope is inference cost—not the full cost of operating a feed, hosting media, or sustaining a creator ecosystem.

This is the basis for the title’s forecast. Tandon’s closing comparison places content feeds in four of the ten most-used apps by daily active users: recommendation already operates inside enormous consumer products. LLM recommenders could improve the engines behind those products while adding steerable feeds, explanations, and more direct user control. His expectation of new consumer and recommendation agents over the following year remains a forecast; the concrete opportunity is to combine language-based direction with the token efficiency of selecting existing content.

Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

14:03 · section reference included

Resources

From the talk

Read the complete timestamped transcript
  1. 0:01

    [music]

  2. 0:12

    Welcome everyone. Thank you for coming

  3. 0:14

    out to the LM Rexus track. Um I'll be

  4. 0:19

    sharing the first talk. Uh my talk is

  5. 0:22

    titled tokens and engagement out

  6. 0:24

    training LM recommenders. Um, and I want

  7. 0:28

    to make two big arguments today. The

  8. 0:30

    first is that recommendation systems

  9. 0:33

    scale just like LMS do and that the

  10. 0:35

    field is very early in that scaling

  11. 0:37

    curve. Um, and the second is that the LM

  12. 0:40

    recommener is going to be one of the

  13. 0:42

    biggest consumer applications of AI.

  14. 0:47

    Um, okay. So, quickly about me. Uh, I

  15. 0:50

    currently work at Meta on research and

  16. 0:52

    product. Uh I lead a team called Meta

  17. 0:54

    Recommendations Research uh which is

  18. 0:57

    this group that's training frontier

  19. 0:59

    models, LLMs and recommenders that power

  20. 1:02

    Instagram, Facebook ads, the meta family

  21. 1:05

    of apps. Uh before this I was at Google

  22. 1:08

    for a long time uh working on a lot of

  23. 1:11

    the key ML teams including deep mind and

  24. 1:13

    YouTube. Last year I gave a talk at AI

  25. 1:16

    engineer called teaching Gemini to speak

  26. 1:18

    YouTube about two ideas semantic IDs and

  27. 1:22

    generative retrieval which we also wrote

  28. 1:25

    two papers about which I've linked here.

  29. 1:27

    Um it was really fun and it led to a lot

  30. 1:29

    of discussions and collaborations. Uh

  31. 1:31

    the ideas behind semantic ID and

  32. 1:33

    generative retrieval have really taken

  33. 1:36

    off in the industry over the last year.

  34. 1:38

    Um and they've moved from more research

  35. 1:41

    to now scaled production systems. And

  36. 1:43

    I've seen exciting launches and papers

  37. 1:46

    from YouTube, Meta, Spotify, Door Dash

  38. 1:50

    across the industry. And we have a

  39. 1:51

    couple of examples of that later today.

  40. 1:55

    This year I want to talk about four uh

  41. 1:58

    sections. Recommendation scaling curves,

  42. 2:01

    a framework of four, recommendation

  43. 2:04

    paradigm scurves that we are climbing as

  44. 2:06

    an industry. um sharing the recommener

  45. 2:09

    recipe and finally this consumer AI app

  46. 2:13

    framework.

  47. 2:15

    Um let's start with scaling curves. So I

  48. 2:17

    wanted to start with this landmark

  49. 2:19

    scaling curve paper from 2020 which

  50. 2:22

    feels like a lifetime ago. This is when

  51. 2:24

    Daario was still at OpenAI and Anthropic

  52. 2:26

    didn't exist yet. But the core idea that

  53. 2:28

    this paper shared is the power law of

  54. 2:30

    scaling. As you increase model size,

  55. 2:34

    data, the amount of compute flops

  56. 2:37

    trained uh for model training, the loss

  57. 2:40

    falls on this log linear scale. And this

  58. 2:43

    clean and predictable curve is what

  59. 2:45

    really set off the race for the AI

  60. 2:47

    frontier because you can forecast what

  61. 2:49

    model quality and capability

  62. 2:51

    improvements will look like. And this is

  63. 2:53

    what's underwriting the massive capex

  64. 2:56

    investments and the AI buildout today.

  65. 2:59

    It turns out that recommendation systems

  66. 3:01

    follow a very similar scaling law. In

  67. 3:04

    fact, before this wave of LLMs, Rexs

  68. 3:07

    were the largest production ML models in

  69. 3:09

    big tech companies. And they're still

  70. 3:11

    some of the largest models that are

  71. 3:13

    served at a scale of a billion plus

  72. 3:15

    daily active users.

  73. 3:17

    And they follow this similar power loss

  74. 3:19

    scaling curve. On the x-axis, you have

  75. 3:21

    data, compute, and model size. And on

  76. 3:24

    the Y ais you would see falling loss or

  77. 3:27

    in this chart uh an improvement in

  78. 3:30

    recommendation quality. In offline evals

  79. 3:33

    it's net entropy or AU gains and then

  80. 3:36

    when it's translated to a real

  81. 3:38

    production launch it's engagement impact

  82. 3:41

    revenue impact at some of the biggest

  83. 3:43

    consumer app scale.

  84. 3:46

    Here's a real example from Meta that

  85. 3:49

    demonstrates these power loss scaling

  86. 3:51

    curves. uh there's a paper the first is

  87. 3:54

    a paper HSTU from 2024 and the second is

  88. 3:59

    a followup from this year both

  89. 4:01

    demonstrate that as we scale model size

  90. 4:04

    compute and data we see this clear

  91. 4:06

    improvement in offline eval of

  92. 4:08

    recommendation quality

  93. 4:11

    scaling curves aren't just academic

  94. 4:13

    research they're driving real product

  95. 4:15

    impact at scale for some of the biggest

  96. 4:17

    consumer businesses in the world here's

  97. 4:20

    a couple of examples I have from Meta's

  98. 4:21

    recent earnings reports. Um, Instagram

  99. 4:24

    reels had a strong quarter, 30%

  100. 4:26

    year-on-year watch time. And,

  101. 4:30

    uh, the optimizations we made to improve

  102. 4:33

    the quality of recommendations included

  103. 4:35

    simplifying our ranking architecture to

  104. 4:37

    enable efficient model scaling and

  105. 4:40

    longer interaction histories to identify

  106. 4:42

    a person's interests.

  107. 4:44

    uh we doubled the length of user

  108. 4:46

    interaction sequences used for training

  109. 4:48

    Instagram and increased the richness of

  110. 4:51

    each user interaction.

  111. 4:53

    So these are direct parallels to the

  112. 4:56

    power loss scaling curves for LLMs.

  113. 4:59

    And I want to introduce this idea of a

  114. 5:02

    flywheel of tokens in engagement out

  115. 5:04

    which is what's powering all of these

  116. 5:06

    Rex model scaling. You train a model.

  117. 5:09

    You then run inference on it which is

  118. 5:11

    the tokens in that recommendation model

  119. 5:14

    results in better content

  120. 5:16

    recommendations. It drives consumer

  121. 5:18

    engagement, daily active users time

  122. 5:21

    spent. It translates to monetization and

  123. 5:23

    ads or subscription which pays for the

  124. 5:26

    next model training run. And so every

  125. 5:28

    step on the scaling curve is one loop

  126. 5:31

    around this flywheel. And a lot of

  127. 5:33

    consumer apps are spinning this core

  128. 5:35

    flywheel at the heart of their business.

  129. 5:39

    So we have a long way to scale these

  130. 5:40

    recommener systems. I want to talk about

  131. 5:42

    the four paradigms that I see the

  132. 5:44

    industry progressing through. The first

  133. 5:47

    scurve was more traditional Rexus where

  134. 5:50

    this scurve focused more on feature

  135. 5:52

    engineering and user and content

  136. 5:54

    embeddings. Most production systems are

  137. 5:56

    still sitting on this curve. they're

  138. 5:58

    running some type of two tower sparse

  139. 6:00

    network rankers scaling the embedding

  140. 6:02

    models. I don't think this curve is

  141. 6:05

    going to go away but model development

  142. 6:07

    here will be accelerated with auto

  143. 6:09

    research and things like feature

  144. 6:11

    engineering will be handled by agents uh

  145. 6:13

    rather than real ML engineers. The next

  146. 6:17

    curve is kind of LM inspired models

  147. 6:20

    where you are scaling models ideally end

  148. 6:22

    to end. HSTU and one wreck papers are

  149. 6:25

    examples in this paradigm. I think this

  150. 6:28

    is

  151. 6:29

    where the leading recommener systems in

  152. 6:31

    the industry are largely operating

  153. 6:33

    today. I think the next scurve will be

  154. 6:36

    this paradigm of LLM native where you

  155. 6:39

    adapt a base model that understands and

  156. 6:42

    can reason uh and adapt it for

  157. 6:44

    recommendation tasks. The tiger and plum

  158. 6:47

    papers are some examples of this

  159. 6:48

    paradigm. And I think the final paradigm

  160. 6:51

    that I start to see emerging is agentic

  161. 6:54

    where LLMs will start to orchestrate Rex

  162. 6:56

    systems in a loop. I think there's a

  163. 6:58

    parallel here with coding agents. So the

  164. 7:01

    LM native models are like improving the

  165. 7:04

    core capabilities of the model going

  166. 7:06

    from opus 45 to 48 versus the agentic

  167. 7:09

    curve will be like improving the coding

  168. 7:11

    harness behind claw code or codeex. Um

  169. 7:14

    and so instead of just having a single

  170. 7:16

    forward pass through the recommener, you

  171. 7:19

    can imagine a loop where agents plan,

  172. 7:22

    retrieve, rank and then critique the

  173. 7:25

    recommendations. They can refine them by

  174. 7:27

    calling models again and finally deliver

  175. 7:29

    the recommendations. This I think is an

  176. 7:31

    interesting area of research. Now

  177. 7:34

    let me jump into

  178. 7:37

    so here here's kind of the framework of

  179. 7:39

    all the four Rex paradigms. I think

  180. 7:42

    companies are scaling across each of

  181. 7:45

    these curves in parallel.

  182. 7:48

    Most of recommendations I think lives in

  183. 7:50

    LM inspired today and is trying to

  184. 7:52

    graduate into LM native. Uh but then a

  185. 7:55

    lot of companies are still using

  186. 7:57

    traditional models uh and climbing that

  187. 7:59

    scurve.

  188. 8:02

    Let me shift gears a bit to share the

  189. 8:05

    recipe of how to actually build a LLM

  190. 8:07

    recommener.

  191. 8:10

    I think it's pretty simple. It's three

  192. 8:12

    steps. Uh you start with tokenizing your

  193. 8:15

    content and creating a language for your

  194. 8:17

    domain.

  195. 8:18

    Then you want to adapt the LLM so that

  196. 8:21

    it understands both English and your

  197. 8:23

    domain language and becomes this

  198. 8:25

    bilingual model. Finally, you can prompt

  199. 8:28

    this model with user information and it

  200. 8:31

    will directly decode recommendations

  201. 8:34

    from your content corpus.

  202. 8:36

    Let's go a bit deeper. This is the LLM

  203. 8:39

    recommener as a five layer cake. Um,

  204. 8:41

    we'll start at the bottom. Uh, that's

  205. 8:44

    semantic ID where you're converting your

  206. 8:46

    content corpus into tokens that the LLM

  207. 8:49

    can understand and reason over. Then you

  208. 8:51

    have kind of the base LLM foundation

  209. 8:54

    model. This can be an open weights model

  210. 8:56

    or an internal first party model. Then

  211. 9:00

    the core training stages. Pre-training

  212. 9:02

    is around bridging English and these

  213. 9:04

    recommener tokens. Post-raining is about

  214. 9:08

    steering the model towards

  215. 9:11

    recommendation tasks like predicting

  216. 9:13

    engagement or reasoning over

  217. 9:15

    recommendations.

  218. 9:17

    And then finally, you can just do some

  219. 9:19

    light surface specific fine-tuning to

  220. 9:21

    deploy it on a product surface. The

  221. 9:24

    exciting thing about this paradigm is

  222. 9:26

    most of the compute is shared across all

  223. 9:28

    of the product surfaces. So you don't

  224. 9:30

    have to train individual models from

  225. 9:32

    scratch for every product surface.

  226. 9:36

    I'll go a bit deeper into each stage for

  227. 9:38

    semantic ids. I think this has seen

  228. 9:40

    incredible adoption. A lot of teams are

  229. 9:42

    just replacing their hash ID with the

  230. 9:45

    SID in traditional models and seeing

  231. 9:47

    good impact. I think there's two big

  232. 9:49

    reasons to tokenize content. The first

  233. 9:52

    is it gives you the stable

  234. 9:53

    representation for models to learn over

  235. 9:56

    rather than a constantly shifting hash

  236. 9:58

    that the model can only memorize. And

  237. 10:01

    the second is compression. You want to

  238. 10:03

    be reasoning over these long sequences

  239. 10:05

    of user interactions. And if you don't

  240. 10:08

    compress the content, for example, a

  241. 10:10

    threeminut Instagram real video would be

  242. 10:12

    10,000 tokens and it will just fill up

  243. 10:14

    the content context window too quickly.

  244. 10:17

    So you have to to compress it into about

  245. 10:19

    10 tokens. And so here I have some

  246. 10:22

    examples of Instagram reels about

  247. 10:23

    tennis. You can see that the semantic

  248. 10:25

    token shares the prefix of the first

  249. 10:28

    three tokens because they're very

  250. 10:30

    similar reels. You can imagine the first

  251. 10:32

    token representing sports um and the

  252. 10:35

    second two tokens representing tennis

  253. 10:37

    and then the final token making these

  254. 10:39

    videos individual.

  255. 10:42

    Once you have a semantic ID, you can

  256. 10:44

    train it to understand both English and

  257. 10:48

    semantic ID. And so the task I have on

  258. 10:51

    the left for pre-training here is an

  259. 10:52

    example of where you prompt with a video

  260. 10:55

    with semantic ID ABC has the description

  261. 10:58

    blank and the output is a shot that was

  262. 11:00

    instantly iconic from Wimbledon. Here

  263. 11:03

    you're teaching the model to connect

  264. 11:04

    these semantic tokens with synthetic

  265. 11:08

    English natural language text. The

  266. 11:10

    example on the right is about reasoning

  267. 11:12

    over sequences of semantic IDs. And so

  268. 11:15

    in a user's interaction history, you can

  269. 11:17

    mask some parts of the sequence and the

  270. 11:20

    model learns to predict them and

  271. 11:22

    understand what videos are watched

  272. 11:25

    together in sequence.

  273. 11:27

    Here I have an example of post training

  274. 11:29

    where we're teaching the model how to

  275. 11:31

    rerank content. So the input is a bunch

  276. 11:33

    of user information and 30 candidate

  277. 11:36

    videos that are then ranked to be the

  278. 11:39

    top five recommendations from this LLM

  279. 11:42

    ranker. What's really interesting here

  280. 11:44

    is that you can see the chain of thought

  281. 11:47

    reasoning of this model. And because

  282. 11:49

    this model knows both English and

  283. 11:51

    recommendations, you can simply just

  284. 11:54

    inspect the model and understand why it

  285. 11:56

    made the decisions that it did. In this

  286. 11:58

    example, the model understands the

  287. 12:00

    user's topic interests like comedy,

  288. 12:03

    food, DIY, wellness. It understands the

  289. 12:06

    engagement style and what creators this

  290. 12:09

    user has an affinity towards.

  291. 12:12

    and then it reranks the content based on

  292. 12:15

    this chain of thought reasoning.

  293. 12:18

    I think this is super exciting because

  294. 12:20

    once you have a model that can

  295. 12:21

    understand both English and

  296. 12:24

    recommendations, it opens up new product

  297. 12:27

    surfaces and new experiences where users

  298. 12:30

    can steer their feed. Here's an example

  299. 12:33

    from your algorithm on Instagram where

  300. 12:36

    users can talk to the algorithm while

  301. 12:38

    they're consuming content. It's a

  302. 12:41

    screenshot from scrolling through reels

  303. 12:43

    or when you click in you can understand

  304. 12:45

    what the Instagram algorithm thinks

  305. 12:47

    about you and your interests and then

  306. 12:49

    you can add or remove interest and talk

  307. 12:51

    to it in natural language. And so we're

  308. 12:54

    going to see this shift I think from

  309. 12:56

    blackbox recommendations algorithms to

  310. 13:00

    giving users more control over their

  311. 13:02

    algorithm and algorithms becoming more

  312. 13:04

    interactive and steerable.

  313. 13:06

    I'm really excited that users can direct

  314. 13:09

    it towards their own goals that's

  315. 13:11

    expressed in language rather than just

  316. 13:13

    likes or comments. Um, and I think this

  317. 13:17

    can this foundation model can also start

  318. 13:20

    to explain its recommendations.

  319. 13:23

    And so for this example, I've added an

  320. 13:26

    interest that I want to follow the FIFA

  321. 13:27

    World Cup at this time. And the model

  322. 13:30

    would get both my user history and this

  323. 13:33

    new input and then be able to decode

  324. 13:36

    recommendations that are personalized to

  325. 13:37

    me like this free cake that Messi scored

  326. 13:40

    recently.

  327. 13:44

    I think these interactive recommenders

  328. 13:47

    are going to be a really interesting new

  329. 13:48

    product surface and we're seeing this

  330. 13:50

    across the industry. We have some

  331. 13:52

    examples of prompted playlists from

  332. 13:54

    Spotify, custom feeds from YouTube, Ask

  333. 13:57

    Door Dash, and we'll be hearing more

  334. 13:59

    from speakers about these.

  335. 14:03

    Um, finally, I want to talk about kind

  336. 14:06

    of the framework of tokens in engagement

  337. 14:09

    out this flywheel that I started with um

  338. 14:13

    of model training, inference, consumer

  339. 14:16

    engagement, and then monetization.

  340. 14:19

    This is actually the same flywheel

  341. 14:21

    that's shared by content feeds and the

  342. 14:24

    AI chat apps. And this is a lens that

  343. 14:27

    you can use to evaluate any consumer

  344. 14:29

    app. What'll make an app successful on

  345. 14:32

    the training ROI side is how well can it

  346. 14:35

    translate compute into a frontier model.

  347. 14:38

    On the inference side, how well can the

  348. 14:40

    inference tokens translate into

  349. 14:43

    engagement and then monetization.

  350. 14:46

    And so if you try to compare content

  351. 14:48

    feeds and AI chat apps, I think that LM

  352. 14:52

    recommenders are actually structurally

  353. 14:54

    more token efficient than the AI chat.

  354. 14:57

    So on the left you have content feeds

  355. 14:59

    like Instagram, Facebook, Tik Tok and

  356. 15:01

    YouTube. On the right you have the big

  357. 15:02

    AI chat apps like Gemini, ChatGpt and

  358. 15:05

    Claude.

  359. 15:07

    Content feeds are currently using models

  360. 15:09

    that are around 1 to 10 billion active

  361. 15:12

    parameters. The chat apps are serving

  362. 15:14

    much larger models 10 to 100 billion

  363. 15:16

    active parameters. Um the output for the

  364. 15:19

    content feed is a semantic ID token

  365. 15:22

    which is a pointer or an address to

  366. 15:24

    existing content because the content

  367. 15:27

    supplied on these content feeds is

  368. 15:29

    uploaded by creators. There's a very

  369. 15:31

    healthy creator economy and so the

  370. 15:33

    supply of content is effectively free or

  371. 15:36

    it's uploaded by creators. For the AI

  372. 15:39

    chat apps, they have to decode every

  373. 15:41

    token of content themselves and the

  374. 15:45

    amount of tokens output in every turn of

  375. 15:49

    an LM chat interaction is a few thousand

  376. 15:52

    tokens. Uh, and the the big difference

  377. 15:56

    here is that every token has to be

  378. 15:58

    manufactured by the app at inference

  379. 16:00

    time. And so what that means is if you

  380. 16:02

    compare these two apps on how much

  381. 16:06

    inference cost and compute is spent to

  382. 16:08

    generate an hour of consumer engagement,

  383. 16:10

    there's a huge structural gap where

  384. 16:13

    content feeds are significantly cheaper

  385. 16:16

    up to 100 times or more cheaper than AI

  386. 16:18

    chat apps because they're decoding

  387. 16:20

    pointers to content rather than content

  388. 16:22

    itself.

  389. 16:24

    Um, finally I want to kind of end with

  390. 16:27

    why I think LM Rexus is one of the most

  391. 16:30

    significant consumer AI applications. If

  392. 16:34

    you look at the top apps by daily active

  393. 16:36

    users, these are the top 10 apps. Four

  394. 16:38

    out of 10 of them are content feeds. And

  395. 16:42

    so this is a really significant consumer

  396. 16:45

    uh application. If you look at the

  397. 16:48

    content feeds, almost all of the

  398. 16:50

    consumer app growth on both the

  399. 16:52

    engagement and monetization side is

  400. 16:55

    driven by the recommener and ads models.

  401. 16:58

    And these are going to be entirely

  402. 16:59

    transformed by LLM recommenders.

  403. 17:02

    It's a very large and very token

  404. 17:05

    efficient application of AI for consumer

  405. 17:07

    apps. We're going to see a lot of new

  406. 17:09

    product experiences come through with

  407. 17:12

    steerable and interactive

  408. 17:13

    recommendations, explanation of

  409. 17:16

    recommendations, and just putting more

  410. 17:18

    users in control of their experience on

  411. 17:20

    these apps. I think we're going to see

  412. 17:23

    some really exciting research on

  413. 17:24

    consumer agents and recommendation

  414. 17:26

    agents that come out over the next year

  415. 17:28

    or so. Um and so this is why I think

  416. 17:31

    this is a super exciting area of both

  417. 17:34

    research and product uh at this

  418. 17:36

    intersection of LLM and recommendations.

  419. 17:41

    That's all. Thank you so much.