This is SSL’s current recommended work order, not a promised release schedule or an approval of every future feature. Each step has a concrete acceptance check.
- 1 · PUBLIC LAUNCH ESSENTIAL
Prove the core site on real phones
Check home, brand guides, equipment selection, manuals, Signal Atlas and the map on iPhone Safari and Android Chrome, plus desktop keyboard navigation. Verify links, readable layouts, zoom, loading failures and usable touch controls.
Ready when: the supported-device checklist passes with no blocking navigation or reading errors. Automated tests alone do not meet this check.
- 2 · BEFORE EXPANDING MEMBER USE
Close privacy, saving and recovery gaps
Verify sign-in, account isolation, saves after reload and another-device access. Add full account/photo erasure, route deletion, access to older records, and a tested backup/restore process. Confirm queued uploads survive connection loss without duplicate saves.
Ready when: controlled test accounts prove the save, privacy, deletion and recovery journeys end to end. Full erasure controls and physical-phone acceptance remain open.
- 3 · ACTIVE REFERENCE WORK
Deepen the brand and model database
Research every represented manufacturer in rotation: detector history, exact models, official manuals, revisions, lifecycle dates, firmware and supported accessories. Resolve broken sources and conflicting documentation first.
Ready when: every added claim has an applicable source and actual review date; unknown dates and compatibility stay unknown. The first brand guides and six model-document links are now included; complete historic coverage remains open.
- 4 · SEARCH DISCOVERY
Make useful reference pages easy to find
Keep descriptive page titles, canonical URLs, an automatically generated sitemap and internal links aligned with the database. Publish substantive model references as research supports them, then verify site ownership and inspect indexing in Search Console.
Ready when: public reference URLs are crawlable and indexing can be monitored. Sitemap and brand-page structured data are implemented; indexing, rankings and traffic gains have not been verified.
- 5 · BEFORE BROADER COMMUNITY RELEASE
Establish moderation and support
Add abuse reporting, blocking and moderator review, sensible upload limits, a usable support route and clear retention/community policies. Exercise recovery and incident handling before inviting wider participation.
Ready when: reports can be handled, abusive content contained and data recovery demonstrated. Existing comments and sharing do not establish a complete moderation service.
- 6 · LATER, SEPARATELY SCOPED RELEASES
Expand only after the core is dependable
Continue sourced map coverage and model documentation. Measured Sound Garden results require actual measurements. Paid certification needs an adopted protocol, reference equipment, costs, service terms and payment setup before it can be offered.
Boundary: Treasure Scan remains paused. PayDirt, full seed/sapling lifecycles, background GPS, offline cold start and phone push are not promised by this release.