WVW Store Checker
BetaThis tool is in beta. Some features may change or have limited functionality.Check if your apps.json is synced with the World Vibe Web (WVW) aggregated app store. Compare listings, detect missing apps, and see the next build countdown.
How to Check Your WVW Store Sync
- 1
Provide Your Apps.json
Enter the URL to your published apps.json file, or switch to Paste JSON mode and paste the contents directly if your server does not support cross-origin requests. - 2
Click Check Sync
The tool fetches the current WVW global catalog and compares each of your apps against what WVW has. This comparison runs entirely in your browser. - 3
Review the Results
See a summary showing total apps, matching apps, apps with differences, and apps missing from WVW. Click any app to see a field-by-field comparison highlighting exactly what differs. - 4
Take Action
If apps are missing or out of sync, wait for the next WVW build cycle. If issues persist beyond 6 hours, check that your apps.json URL is publicly accessible and correctly registered with WVW.
Common Use Cases
Post-Submission Verification
Debugging Sync Issues
Monitoring Description Updates
Why Check Your WVW Store Sync?
World Vibe Web (WVW) is a distributed app store that aggregates apps.json files from independent developers and tool creators. WVW fetches your apps.json every 6 hours and merges it into a global catalog at wvw.dev.
When you update your apps.json (add new tools, change descriptions, update icons), those changes do not appear on WVW immediately. This checker helps you see exactly what WVW currently has vs. what you have published, so you can confirm your updates will propagate on the next build cycle.
Common issues include missing apps that were recently added, stale descriptions from a previous version, or CORS misconfigurations that prevent WVW from fetching your file. This tool detects all of these.
The WVW Store Checker compares your published apps.json file against the live World Vibe Web global catalog to detect sync issues. WVW fetches apps.json files from registered developers every 6 hours, but delays, CORS errors, or schema issues can prevent your apps from appearing. This tool shows exactly what WVW has versus what you have published, down to individual field differences.
The checker compares app name, description, subtitle, homepage, icon, category, language, platform, and price fields. WVW-internal fields like _source, _owner, and star counts are ignored since those are added during aggregation. Results show matching apps, apps with differences, missing apps, and extra apps, with a field-by-field diff for each entry.
Use this tool after submitting a pull request to wvw.dev to verify your apps appear correctly. Pair it with the WVW Apps.json Generator to create or update your listings, and the JSON Diff tool for detailed structural comparisons between JSON files.
How It Compares
There is no other dedicated tool for checking WVW sync status. Without this checker, developers must manually compare their apps.json against the WVW global catalog by downloading both files and using a JSON diff tool. The WVW Store Checker automates this entire process, fetches the live WVW catalog in real-time, and highlights differences at the field level.
The built-in build countdown timer and report export features make it a complete monitoring solution for WVW publishers. Combined with the WVW Apps.json Generator, it provides an end-to-end workflow for creating, validating, publishing, and verifying app listings on the World Vibe Web.
Store Checker Tips
- Check sync status 6-8 hours after merging your pull request to wvw.dev, since builds run approximately every 6 hours.
- Use the Paste JSON mode if your server does not support CORS. Copy the contents of your apps.json file and paste directly.
- If an app shows as missing, verify your apps.json file is publicly accessible by opening the URL in an incognito browser window.
- Export the JSON report to track sync status over time or share debugging information with the WVW maintainers.
- After updating your apps.json, wait for two build cycles (approximately 12 hours) before investigating persistent sync issues.