Data sources

Apoku combines public store data with its own evidence layer. The two

are never mixed silently: every field on a page is either a store fact or

an Apoku text, and the evidence block says which is which.

Store facts

history, price, ratings, screenshots, privacy declarations.

buckets where Google publishes them.

A store fact is what the developer published. We record when we observed it

and when the store last updated it (`store_updated_at` on each listing).

Summaries, "best for / not for" lists, feature availability, category and

use-case assignments, and the known-gaps notes are Apoku's own information

layer. They never copy the store description. Where we have not verified a

function yet, the page shows "Unknown" instead of a guess.

New apps enter through targeted catalog parses of the two stores. The date

of the last data import is published in

llms.txt together with explicitly named catalog counts. Re-checks of existing

apps run continuously; each page shows the date of its last check.