Day 5 — Operations, legal and cost limits are set

What you have afterwards: Legal pages, publishing details and cost limits are prepared.

Goal

You clarify what can cost you money, time or trust after publishing.

Understand briefly

A login is not cost control. Anything that triggers a paid feature needs a server-side approval first: request → check → reserve budget → start provider → record usage. Remote config may hide buttons, but it is never the security boundary — the server always makes the final call. And a single “AI on/off” is too coarse: switch individual capabilities separately and keep the free manual route available when you pause the expensive one.

Follow along

Paste this prompt into the AI tool you work with:

My app does: [SHORT DESCRIPTION]. Paid or external calls: [LIST OR “none”]

1. List which legal texts, support routes and data declarations my release goal requires.
2. Propose a separate switch plus daily and monthly limit for every paid feature.
3. Describe a server-side kill switch that also stops an old app version.
4. For each point, tell me how I can tell it actually takes effect.

Explicitly mark anything you are not sure about.

Build it yourself

Write your legal and support pages, create icon, splash and description texts, and set a hard cap for every paid feature.

Verify

Only tick a box once you have really checked it. These criteria are the only way to finish this unit.

Privacy policy, imprint and a reachable support route exist.
Icon, splash, screenshots and a truthful description are ready.
Every paid feature has a limit and a reachable kill switch.

0 of 3 confirmed

Still open: 3 criteria

Self-check

Three questions about decisions you made today. There are no points and no grade — only the why. Every answer can be changed.

1. Your app triggers a paid function. What protects you from a surprise bill?

That only logged-in users can trigger itA server-side approval before every callA switch that lets me disable the function remotely

2. What is remote config good for — and what not?

As a security boundary, to lock featuresTo hide buttons — the server makes the decisionFor both, if the switch is well secured

3. You are writing the description for your release. What do you hold to?

What the app will soon be able to doWhat it demonstrably does todayThe terms people search for

0 of 3 answered

Next step

Tomorrow you build the state you would actually ship.

Next: Day 6 — A real release candidate