Fast answer
The answer before the background
Use this Cafe Panic wiki page as a versioned source directory. The live client owns current recipes, objectives, machine costs and event rules. Apple owns app ID, compatibility, purchases and version history; Google Play owns the Android package, Windows availability, current feature list and offline labels; Boomware owns product and support identity. Facebook and Instagram announce content, but a post must retain its date, platform and version before it becomes database evidence.
Database schema
Store restaurants, recipes and economy as linked objects
- Restaurant row: name, permanent or event status, region, version introduced and level range.
- Recipe row: ingredients, machines, assembly order, restaurant, unlock and reviewed version.
- Machine row: job, capacity, tier, cost labels, affected recipes and measured service change.
- Level row: objective, order pattern, baseline upgrades, failure point, successful change and result.
- Resource row: exact label, icon, acquisition, spending destination, platform and event scope.
- Source row: official URL or screenshot, date, locale, client version and verifier.
Count conflicts
Preserve both official snapshots instead of inventing one total
Apple's visible description says 700+ levels and 360+ recipes, while Google's newer English copy says 40 cafes, 800+ recipe combinations, 480 machines and 100 outfits. These may reflect copy freshness, counting method or platform timing. Record both with source and date rather than averaging them.
Apple was at version 14.0.1 during this review and highlighted Back to School content; Google had a July 11 update and Lebanon restaurant details. Current client observation should decide which content is actually available to a given account and region.
Community evidence
Turn a tip or bug report into a reproducible row
A useful report includes device, platform, app version, restaurant, level, objective, machine tiers, network state and exact sequence. A statement such as 'this level is impossible' cannot distinguish a bug, an upgrade gate or a changed recipe.
Use the official Facebook and Instagram links for announcements, not account credentials or file distribution. Do not treat an attached APK, save, generator or purchase workaround as wiki evidence. Keep historical pages dated when the client changes.
FAQ
Common questions
Is there an official Cafe Panic wiki?
No single publisher-maintained public wiki with current values was established during this review.
Where should current recipe values come from?
Use the live client and retain platform, version, restaurant and level.
Why do Apple and Google show different totals?
Store copy may use different dates or counting methods; preserve each sourced snapshot and verify the client.
Which social pages are linked officially?
The store descriptions link Cafe Panic on Facebook and @cafe.panic on Instagram.
Sources
What we checked
Official listings establish current availability and product facts. Community pages are used for mechanics and build history, then labeled separately.