I work on OnePassApps, and this post is about our own site's served copy.

Every page we serve ships a fallback block: the prose a crawler, or a reader with JavaScript turned off, sees before the app boots. On our 22 app pages that block always ends with the same kind of section, and the answers split cleanly into two groups.

What the fallback block looks like

On all 22 app pages the block carries the same shape:

  • one h1
  • six paragraphs
  • three sections, headed "What you can do", "Limitations", and a third section whose heading is a question
  • five bullets in total: three in the first section, two in the second, none in the third

The block runs between 1,530 and 1,852 characters of text - a spread of 322 characters across 22 pages. The shortest is ambient-noise-mixer, the longest is movie-tracker. Across all 22 app pages the block carries 36,747 characters in total.

The third section is a cost contract

That third section is the only part of the block that talks about money, and its heading is the app's own free question. Twenty of the 22 app pages ask it in exactly one shape, with the app's display name substituted:

"Is free, and do I need an account?"

Two do not. MovieMatcherAI asks "Is MovieMatcherAI free, and does it use credits?" and NewsFlow asks "Does NewsFlow cost anything or use credits?".

The answers split the same way

The answer is the third of the block's six paragraphs. Twenty of the 22 answers open with the same sentence:

"Yes, it is free."

Each of those 20 then ends with the same clause: "it never uses OnePassApps credits."

The two exceptions are the two apps that call our servers, and they are the only two blocks where the word appears twice: once in the heading, once in the answer.

MovieMatcherAI's answer says browsing and title details are open without an account, that a free account adds the private Tracker, ratings, notes and reactions, and that film analysis and fresh movie data look-ups "run on our servers for your account and use credits from your plan's recurring allowance, which the Free plan includes". It closes by pointing at the plans page: "Plans compares the allowances."

NewsFlow's answer says "Briefs and listening are prepared at no credit cost." Guests read and listen to the public Inbox within shared capacity and usage limits, and signing in with a free account is what lets you change the sources you follow.

What the copy adds up to

Read as a set, the 22 app pages carry 22 cost statements, and they divide by whether the app talks to our servers:

  • 20 browser-local apps: one sentence, one clause, the app's own name substituted.
  • 2 hosted apps: a different question, and an answer that says what the credit buys.

So "it never uses OnePassApps credits" appears in exactly 20 of the 22 answers, and the two answers that do not use it belong to the two hosted apps, MovieMatcherAI and NewsFlow.

More on the apps: https://app.onepassapps.com/?utm_source=devto&utm_medium=post&utm_campaign=cost-answer-layer&utm_content=home-link

The written guide for each app: https://app.onepassapps.com/guides?utm_source=devto&utm_medium=post&utm_campaign=cost-answer-layer&utm_content=guides-link

Limits

One build, one fetch per URL, 9 November 2026, plain HTTPS from one network, no browser and no JavaScript. The 56 URLs are the ones in our sitemap.xml, and the 22 app pages are the /apps/ routes among them. These are the sentences in the fallback block we serve; what the live app shows once it has booted is a different document, and I did not compare the two. I did not sign in, and I did not measure what any app does with a credit. "Credits" is our own word from our own copy - I am reporting what the sentences say, not auditing the billing.

I work on OnePassApps.