WOODHOUSEThe Loftwah Software Factory

Find a project or subject.

156 pages in the index

Esc closes search ⌘ K or Ctrl K opens it

MoreMenu
Measurement & privacyGames × RadioExplore connected productsEdition discoveryExplore the projects

SHOALSHOT analytics

Play & engagement

Custom dates
UTC · max 90 days
24 Sept 2026 – 23 Oct 2026 · 30 days · Today is partial1/1 reporting projects for this measure · 7/7 sources reporting · Saved snapshot

This report is frozen at 2026-10-23 03:50 UTC. Refresh these dates · Latest 30 days

Game starts · SHOALSHOT

Count per UTC day · gaps mean unavailable

A recorded launch into gameplay. Repeat play counts again. These are browser reports, not verified players.

Game starts
2
Partial coverage
Game completions
2
Partial coverage
Active play time
0m 52s
Partial coverage
1009-2410-0810-23

Inspect a date to see source values. The data table below works without interactive charts.

Chart data & export

These are daily values for game starts. A dash means unavailable. Daily distinct-browser counts must not be added to estimate period-level people.

Game starts· UTC dates ·count
DateSHOALSHOT
2026-09-24—missing
2026-09-25—missing
2026-09-26—missing
2026-09-27—missing
2026-09-28—missing
2026-09-29—missing
2026-09-30—missing
2026-10-01—missing
2026-10-02—missing
2026-10-03—missing
2026-10-04—missing
2026-10-05—missing
2026-10-06—missing
2026-10-07—missing
2026-10-08—missing
2026-10-09—missing
2026-10-10—missing
2026-10-11—missing
2026-10-12—missing
2026-10-13—missing
2026-10-14—missing
2026-10-150partial
2026-10-160clean
2026-10-170clean
2026-10-181clean
2026-10-191clean
2026-10-200clean
2026-10-210clean
2026-10-220clean
2026-10-230partial

Can we compare these dates?

Coverage for the selected measure. Colour describes evidence, not popularity.

Comparable full dayPartial dayLegacy / test riskBounded / sampledNot measured
24 Sept 202623 Oct 2026
SHOALSHOT

The longest available comparable history in this selection is 7 complete daily observations. First collection days and today remain partial. Legacy activity may include tests that cannot be separated.

Have browsers come back?

These are optional browser signals, kept separate for each project. They cannot identify people or establish cohort retention. Daily browser counts do not add up to a period total.

  • SHOALSHOTNot measured for these dates

    DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill. Browser returns are unavailable until this product releases its own optional consent client.

What changed around this activity?

Dated release observations sit beside the collection and comparison boundaries reported by each source. Nearby dates suggest questions to investigate; they do not show that a release caused a change in use.

This is a reviewed selection, not a complete release feed. Notes are frozen with the report and may precede the selected dates; notes after its last selected day are omitted.

Explore 6 dated release and collection notes
  1. SHOALSHOT · Collection began

    First source-reported collection date. Earlier activity is unavailable; the first day may be partial.

  2. SHOALSHOT · Comparison boundary

    The source marks this cutover for comparable history. The first boundary day is excluded from complete-week records; later missing or partial days still matter.

  3. SHOALSHOT · SHOALSHOT · generated artwork and sharing repair

    The readable Share result control opens a reef-backed paper result card. The canonical social preview is 1200 × 630; the transparent wordmark is 1998 × 424 and emblem 1161 × 1161. Public originals are available from the project with A Loftwah Game credit. This is a presentation and local-sharing repair. It does not establish a public result permalink, uploaded score, new listening attribution or physical iPhone/native OS share-sheet acceptance. The original native-sharing evidence remains separately dated and versioned.

    Read release evidence · reviewed 2026-10-12
  4. SHOALSHOT · SHOALSHOT · finished-dive sharing

    Play a dive, open Pause, choose End Dive, then use Share result on the Dive Summary. Save a 1200 × 630 PNG, copy its caption or use your device’s share options when supported. The card includes the actual mode, rules and game version. The result is local and unverified. The card is made inside the game; no public result permalink, uploaded score, account or square/portrait result format is provided. Owning Chromium/WebKit receipts establish downloads and navigation; physical iPhone/native OS sharing remains pending. No listening adoption or popularity is inferred.

    Read release evidence · reviewed 2026-10-12
  5. SHOALSHOT · shoalshot · native result sharing

    The final menu release retains the existing SDK 1.2 integration. Owning production receipts cover the exact source, scoped fresh qualification and native menu click/keyboard/focus journeys, with earlier radio and finished-dive evidence separate. Woodhouse reviewed source and the owning receipts; it did not repeat game playback. Physical phone, human listening and native OS sharing remain separate acceptance. The menu release used the existing fixed presentation/FM qualification scope. The lazy radio adapter visit is not every game landing or a unique person. A measured audience trial has not run.

    Read release evidence · reviewed 2026-10-13
  6. SHOALSHOT · shoalshot · exact radio deployment

    Home and Pause offer six music stations and two presenter shows through the existing audio owner. Manual Shuffle, saved preferences, independent effects and local fallback preserve the fishing atmosphere. Physical iPhone and human listening remain open; narrow 320px dock labels need further composition work. Manual Shuffle is delivered; continuous shared My Mix is not.

    Read release evidence · reviewed 2026-10-11

Follow the numbers to their source

Every measure has a definition, a collection boundary and blind spots.

SHOALSHOT6 measures available

Live aggregate endpoint · generated

Collection began
2026-10-15T00:00:00.000Z
Comparable history from
2026-10-15T00:00:00.000Z
Source revision
Not supplied
  • Exact accepted event counters, not unique humans or anti-cheat proof. Blocking, opt-out, offline play and automated traffic affect coverage.
  • DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill.
  • Current UTC day and collection-start day may be partial. Cross-device retention, cohort retention and acquisition sources are not measured.
  • Browser returns are unavailable until this product releases its own optional consent client.
Visits 8Reported activity
One accepted visit marker per tab session; sessions reset after 30 minutes idle. Reloads in the same session do not add visits. Not distinct people.
Engaged sessions 1Reported activity
One accepted marker per tab session after at least 10 seconds of active product use. Foreground, unpaused and recent trusted input required.
Games started 2Reported activity
Accepted new game/dive start actions; restoring or resuming a saved game does not count. Client reported, not verified human play. Multiplayer tabs report participations, not distinct tables.
Games completed 2Reported activity
Accepted terminal game/result transitions. Client reported; not a validated competitive result. Multiplayer tabs report participations, not distinct tables.
Deliberate replays 0Reported activity
Accepted deliberate repeat new-game actions in the same tab session, after completion or abandonment. Automatic restores/resumes are excluded.
Active time 0m 52sReported activity
Accepted 1–30 second foreground, unpaused activity increments, ending 30 seconds after trusted input. Server bounds total by session wall time. Radio time is excluded.
Reporting browsers —Not measured
Not measured: this product has not enabled optional browser-return measurement. Tab sessions cannot establish returns.
Returning browsers —Not measured
Not measured: this product has not enabled optional browser-return measurement. Tab sessions cannot establish returns.

What am I looking at?

A recorded launch into gameplay. Repeat play counts again. These are browser reports, not verified players.

The chart uses one measure and one unit at a time. Each coloured line belongs to a project; the source totals cover the selected window.

What does it tell us?

We can see when recorded activity occurred and inspect how it is distributed across the selected dates.

No clean growth comparison yet. New collection and legacy test traffic limit the history we can trust.

Last complete week

The most recent complete Monday–Sunday UTC week for each project's own headline measure, against the week before. A record needs exact daily history for two adjacent complete weeks; this is a valid comparison, not only the large movements that raise an operational alert.

No project has two complete comparable weeks yet, so no week-on-week figure is shown. Collection is too recent to compare honestly, and nothing is inferred from it.

Why some projects are not compared (1)
  • SHOALSHOT: Fewer than two complete comparable weeks so far.

If you’re assessing the business

Early product instrumentation, with material evidence gaps.

Usage
1/1 projects reporting this measure. 7/7 sources provide some activity. Reports are not verified people.
Retention
No portfolio cohort-retention evidence. Returning browsers, where available, are a narrower signal.
Commercial proof
Revenue, paying customers, acquisition cost and customer value are not measured here.

Use this to ask better product questions. It cannot establish product–market fit, market demand or an investment case.

Read the product dossiers

Report details

Snapshot
1608c4f4231d301093e4605e
Captured
2026-10-23 03:50:27 UTC
Dates
2026-09-24 – 2026-10-23
Time zone
UTC; dates may differ from your local day
Tracking, retention & privacy choices