What does Paywall Breakpoints and Unlock Interfaces conclude, in numbers, about “The Truncation Breakpoint: Which Screen, Which Pixel”?
Answer: A breakpoint is a hazard problem. p20's open cohort measures with the product-limit estimator how fast readers leave screen by screen; the naive count treats lost beacons as exits and understates reach at the end of screen 6 by 0.103. p21 multiplies reach, curiosity and locked value and, under Starbalance's settings, finds an optimal breakpoint at 2.75 screens with a flat top from 2.50 to 3.50 screens; locking on screen 1 earns only 0.696 of the optimum, so hiding more does not always sell more. p22 turns screens into pixels: the same content boundary sits deeper on 360×780 than on 390×844, and only the boundary after section 3 falls inside the flat top on both phones, so the breakpoint is defined by content and accepted on the smallest viewport. p23 shows that which sections go before the breakpoint matters more than its position: the best choice is 1.147 times report order, and the two constraints "include a strength, do not end on the weakest" cost only 0.0126. p25 shows that cutting again inside paid content may earn more on paper but buys a multiple of dissatisfied buyers, and should be ruled out as a hard constraint. p24 insists that the denominator be the result viewer: at Starbalance's traffic, breakpoint differences inside the flat top cannot be measured within a year, and test traffic should be kept for changes with large differences, such as content choice. The next chapter turns to an earlier stretch of the road: the progress readers see while answering the questionnaire.
Scope of the numbers: It is not legal advice; pricing economics is left to earlier volumes. Marked boxes separate published evidence, runnable calculations, classical sources and the author's hypotheses, each stating what would refute it; the "hook and clamp" of the Guiguzi chapter Feiqian is examined in Chapter 1.
Data table
The numbers below are printed verbatim by the chapter's Python program and can be reproduced by running it. standard-library Python onlyprinted values that match the answer: 2.50, 20, 21, 22, 360, 390
| viewport 390x844: 22 glyphs per line, chart 268 px, visible content 716 px | ||
| note: how to read ends at y = 516 px = 0.61 screens ( 5 text lines) | ||
| s1 cash turnover | ends at y = 1,102 px = | 1.31 screens (15 text lines) |
| s2 customer mix | ends at y = 1,688 px = | 2.00 screens (15 text lines) |
| s3 quoting habits | ends at y = 2,300 px = | 2.73 screens (16 text lines) |
| s4 time allocation | ends at y = 2,860 px = | 3.39 screens (14 text lines) |
| s5 repeat buying | ends at y = 3,446 px = | 4.08 screens (15 text lines) |
| s6 channels | ends at y = 3,980 px = | 4.72 screens (13 text lines) |
| s7 team load | ends at y = 4,566 px = | 5.41 screens (15 text lines) |
| s8 margin | ends at y = 5,126 px = | 6.07 screens (14 text lines) |
| s9 peer bands | ends at y = 5,730 px = | 6.79 screens (10 text lines) |
| s10 90-day plan | ends at y = 6,898 px = | 8.17 screens (42 text lines) |
| s11 download card | ends at y = 7,186 px = | 8.51 screens ( 2 text lines) |
| s12 advisor note | ends at y = 7,756 px = | 9.19 screens (19 text lines) |
| viewport 360x780: 20 glyphs per line, chart 246 px, visible content 652 px | ||
| note: how to read ends at y = 542 px = 0.69 screens ( 6 text lines) | ||
| s1 cash turnover | ends at y = 1,180 px = | 1.51 screens (17 text lines) |
| s2 customer mix | ends at y = 1,818 px = | 2.33 screens (17 text lines) |
| s3 quoting habits | ends at y = 2,482 px = | 3.18 screens (18 text lines) |
| s4 time allocation | ends at y = 3,094 px = | 3.97 screens (16 text lines) |
| s5 repeat buying | ends at y = 3,732 px = | 4.78 screens (17 text lines) |
| s6 channels | ends at y = 4,318 px = | 5.54 screens (15 text lines) |
| s7 team load | ends at y = 4,956 px = | 6.35 screens (17 text lines) |
| s8 margin | ends at y = 5,568 px = | 7.14 screens (16 text lines) |
| s9 peer bands | ends at y = 6,150 px = | 7.88 screens (10 text lines) |
| s10 90-day plan | ends at y = 7,396 px = | 9.48 screens (45 text lines) |
| s11 download card | ends at y = 7,684 px = | 9.85 screens ( 2 text lines) |
| s12 advisor note | ends at y = 8,280 px = 10.62 screens (20 text lines) | |
Show the full program
# Chapter 2. p22: From screens to pixels: where each section boundary of the Starbalance report lands.
# Report structure from chapter 1: a reading note, sections 1-8 (indicators), 9 peer bands, 10 a 90-day plan,
# 11 a download card, 12 the advisor's note. Text: 16 px CJK glyphs, line height 26 px, 16 px side gutters.
# Indicator sections carry a 120 px gauge; section 9 a chart 0.75 of the content width tall. Heading 44 px,
# gap 32 px, hero (brand bar and total score dial) 310 px. Sticky top bar 56 px, sticky unlock bar 72 px.
# Character counts are fictional settings. The band 2.50 to 3.50 screens is the quarter-screen band of p21.
import math
VIEWPORTS = [(390, 844), (360, 780)]
GUTTER, GLYPH, LINE, HEAD, GAP, TOP, BOTTOM, HERO = 16, 16, 26, 44, 32, 56, 72, 310
SECTIONS = [ # (name, paragraphs of CJK characters, fixed blocks in px, charts)
("note: how to read", [110], [], 0),
("s1 cash turnover", [330], [120], 0),
("s2 customer mix", [330], [120], 0),
("s3 quoting habits", [352], [120], 0),
("s4 time allocation", [308], [120], 0),
("s5 repeat buying", [330], [120], 0),
("s6 channels", [286], [120], 0),
("s7 team load", [330], [120], 0),
("s8 margin", [308], [120], 0),
("s9 peer bands", [200], [], 1),
("s10 90-day plan", [300, 300, 300], [], 0),
("s11 download card", [40], [160], 0),
("s12 advisor note", [400], [], 0),
]
BAND = (2.50, 3.50)
TEASER_LINES, FADE, LOCK_CARD = 2, 96, 200
def layout(width):
per_line = (width - 2 * GUTTER) // GLYPH
chart = round(0.75 * (width - 2 * GUTTER))
y, ends = HERO, []
for name, paras, blocks, charts in SECTIONS:
lines = sum(math.ceil(c / per_line) for c in paras)
y += HEAD + lines * LINE + sum(blocks) + charts * chart + GAP
ends.append((name, y, lines))
return per_line, chart, ends
if __name__ == "__main__":
tables = {}
for w, h in VIEWPORTS:
per_line, chart, ends = layout(w)
tables[(w, h)] = ends
print(" viewport {}x{}: {} glyphs per line, chart {} px, visible content {} px".format(
w, h, per_line, chart, h - TOP - BOTTOM))
for name, y, lines in ends:
print(" {:19s} ends at y = {:5,d} px = {:5.2f} screens ({:2d} text lines)".format(
name, y, y / h, lines))
print(" cut after a section: screens on 390x844 / 360x780; inside {:.2f}-{:.2f} on both?".format(*BAND))
for i, (name, *_) in enumerate(SECTIONS[:9]):
s = [tables[v][i][1] / v[1] for v in VIEWPORTS]
ok = all(BAND[0] <= x <= BAND[1] for x in s)
print(" after {:19s} {:5.2f} / {:5.2f} {}".format(name, s[0], s[1], "inside" if ok else "-"))
w, h = VIEWPORTS[0]
_, _, ends = layout(w)
for y_px in (2 * h, round(2.75 * h)):
prev = HERO
for name, y, lines in ends:
if y == y_px:
print(" pixel cut at y = {:,} px on {}x{}: at the end of {}".format(y_px, w, h, name))
break
if y > y_px:
print(" pixel cut at y = {:,} px on {}x{}: {} px into {} (its heading is {} px)".format(
y_px, w, h, y_px - prev, name, HEAD))
break
prev = y
print(" whole report on 390x844: {:.2f} screens; sections 1-8 end at {:.2f} screens".format(
ends[-1][1] / h, ends[8][1] / h))
teaser = HEAD + TEASER_LINES * LINE
for w, h in VIEWPORTS:
vis = h - TOP - BOTTOM
print(" {}x{}: teaser {} + lock card {} = {} px of {} visible ({:.3f}); bars take {:.3f}".format(
w, h, teaser, LOCK_CARD, teaser + LOCK_CARD, vis, (teaser + LOCK_CARD) / vis, (TOP + BOTTOM) / h))
for fade in (FADE, TEASER_LINES * LINE):
print(" fade band {} px spans {:.1f} text lines of the locked section".format(fade, fade / LINE))Single source and citation
Fan, Y. (2026). Suspense Breakpoints in Multi-Tier Diagnostic Paywalls, Sunk-Progress Ratchets and Frictionless Unlock Interface Design (Version 0.1.0), Chapter 2: The Truncation Breakpoint: Which Screen, Which Pixel. 5D Library. DOI pending
DOI pending · monograph page goes live after publication · 5DL-B-139 · v0.1.0 · CC-BY-NC-ND-4.0
BibTeX
@book{fan2026139,
author = {Fan, Yafu},
title = {Suspense Breakpoints in Multi-Tier Diagnostic Paywalls, Sunk-Progress Ratchets and Frictionless Unlock Interface Design},
year = {2026},
publisher = {5D Library},
edition = {0.1.0},
note = {DOI pending}
}Other chapter answers in this book
- Chapter 1 · Method: Four Interface Variables, Four Indicators, Evidence Grades and Honest Previews
- Chapter 3 · Endowed Progress: Where the Bar Starts, What It Counts, How Fast It Moves and Whether It Tells the Truth
- Chapter 4 · Sunk-Progress Ratchets: Saved Progress, Personalised Results and the Ethical Edge of the Ratchet
- Chapter 5 · Previewing Locked Content: Blur, Truncation, Card Titles, Sample Sections and the Truth of "Already Computed"
- Chapter 6 · One-Screen Checkout: Fields, Wallets, Trust Marks, Error Messages, Latency and the Edge of Dark Patterns
- Chapter 7 · The Paywall Playbook: Pages for Four Report Tiers, Honest Status Labels and the Distillation Spec for the Four Kits
- Chapter 8 · Practice: Starbalance's Unlock Page from Audit to Rebuild and a Pre-Registered Test