SpeakLocal is trying to feel like a useful field guide, not a generic content farm. This page explains how the website starter layer is chosen, when site audio appears, what “updated” means, and where the app takes over.
We keep the site aligned to selected starter modules from the live pack, publish site audio only where the export says it is ready, and leave deeper search, saved phrases, offline use, and wider coverage in the app.
The website is the public front door for SpeakLocal. It is meant to help a traveler get the first phrase right, understand the shape of a destination pack, and decide whether the app is worth carrying before the trip gets live.
We do not build separate website-only phrase libraries just to make the site look bigger. The public website uses selected starter preview modules from the live pack through the website-safe export seam.
Site audio is not a blanket claim. A module gets site audio only when the export for that module says the clips are ready for the site-owned audio path. If a phrase is text-only on the website, it should stay labeled that way instead of hinting at audio that is not actually published there.
Page-level updated dates mean the article copy or route changed. Module-level freshness comes from the export itself, so the phrase cards can show when that export was generated instead of relying on softer “recently updated” language.
Destination usefulness matters more than phrase volume. A smaller module that helps with airport pickup, wrong totals, SIM trouble, or clarification help is usually more valuable than a bigger archive that never gets a traveler through the next interaction.
The cleanest way to improve trust is to keep corrections easy. If a phrase feels off, a clip is missing, or a destination need is under-covered, use the feedback route so the next export or page pass can be grounded in a real traveler gap.