WVW Store Checker

Yes, the WVW Store Checker is completely free with no account required, no login process, and no limits on how many times you can check your sync status. The entire comparison runs locally in your browser by fetching the public WVW global catalog and comparing it against your apps.json data. No data is stored on any server and no authentication tokens are needed. You can check sync status for unlimited apps, export full comparison reports as JSON, copy text summaries for team sharing, and monitor the next build countdown all without paying anything. Unlike proprietary app store management tools that charge monthly fees for listing monitoring and sync verification, this tool provides dedicated WVW sync checking at zero cost. Whether you maintain a single app listing or manage dozens of tools across your apps.json file, every feature works identically without restrictions, usage quotas, or premium upgrade prompts.

Changes to your apps.json file typically appear on World Vibe Web within six to twelve hours after you publish the updated file to your domain. WVW runs automated GitHub Actions builds approximately every six hours, during which it fetches all registered apps.json files from developer domains and merges them into the global catalog at wvw.dev. If your update was published right after a build completed, you may need to wait up to six hours for the next build cycle to pick it up. The Store Checker displays the estimated next build time and a live countdown so you know exactly when to expect your changes to propagate. If your changes have not appeared after two full build cycles, approximately twelve hours, check that your apps.json URL is publicly accessible without authentication, returns proper JSON content type headers, and does not block requests with CORS restrictions or IP-based rate limiting that could prevent the WVW build system from fetching your file.

The checker compares nine specific fields for each app entry: name, description, subtitle, homepage, icon, category, language, platform, and price. These are the fields you control as a developer and that directly affect how your app appears in the WVW catalog to users browsing the store. The comparison intentionally ignores WVW-internal fields that are added during the aggregation process, including _source, _owner, _developer, _store, stars, and forks. These internal fields are managed by WVW itself and would always show as differences if included in the comparison. For each app where differences are detected, the checker shows a field-by-field diff highlighting exactly what your version says versus what WVW currently has. This granular comparison helps you distinguish between intentional updates waiting for the next build cycle and unexpected discrepancies that might indicate a sync problem, stale cache, or formatting issue in your apps.json file.

Several common issues can prevent an app from appearing on WVW despite being present in your published apps.json file. First, if you recently added the app, it may simply need to wait for the next WVW build cycle, which runs approximately every six hours. Check the countdown timer in the tool to see when the next build is scheduled. Second, verify that your apps.json URL is correctly registered with WVW by checking that your pull request to the wvw.dev repository was merged and that the URL in their registry matches your current domain exactly. Third, ensure your apps.json file is publicly accessible without authentication by opening the URL in an incognito browser window. Fourth, check that your JSON syntax is valid since a single misplaced comma or missing bracket can cause the entire file to fail parsing during the WVW build. Use the JSON Formatter tool to validate your syntax before publishing any updates to your apps.json file.