Methodology

Apoku is an evidence-first catalog of mobile apps. Every page shows what

we know, how we know it, and when we last checked. When a fact is unknown,

the page says so — we do not invent data to fill a card.

Evidence levels

Each app page carries an indexability state that describes its publication

coverage; it is not a rating of independent product verification:

• S0 — not yet indexable. The store listing is missing or the record

lacks basic unique fields (name, developer, store URL). The page exists

but is excluded from search indexes.

• S1 — live store listing. At least one active App Store or Google Play

listing with complete identity fields.

• S2 — editorial summary published. An Apoku summary describes what

the app does, who it is for and who it is not for. This label does not

mean the whole product or every claim received an independent review.

Publication gates

Category and use-case pages go live only when they pass a quality gate:

enough indexable apps, a real definition, and declared evaluation criteria.

Pages below the gate stay visible but are marked `noindex` — thin pages do

not enter the sitemap.

Freshness

Store facts carry the date the store published them. Our checks carry

`last_checked_at` — the time of Apoku’s latest listing check.

Apps that disappear from both stores move through a two-step lifecycle

(missing once, then orphaned) instead of vanishing silently; an orphaned

page keeps its data, shows a banner and leaves the search index.

What store checks mean here

Store text is a claim made by the developer. Apoku summaries, feature

checks and category assignments are separate information layers; their

scope and evidence are shown on each page. A successful parse does not

independently verify every claim. If you spot an error, every app page has

a correction link.