App Composer analytics
App usage & useful outcomes
This report is frozen at 2026-10-23 03:09 UTC. Refresh these dates · Latest 30 days
Completed Link Checks · App Composer
Count per UTC day · gaps mean unavailable
Link Check inspections reported by the owning app after completion. Repeated jobs may count; these are not unique users, outbound clicks or deployment checks.
- Mini-app opens
- 1,294 Bounded count
- Guest postcards received
- 2 Partial coverage
- Completed Link Checks
- 24 Bounded count
Inspect a date to see source values. The data table below works without interactive charts.
Chart data & export
These are daily values for completed link checks. A dash means unavailable. Daily distinct-browser counts must not be added to estimate period-level people.
| Date | App Composer |
|---|---|
| 2026-10-12 | —missing |
| 2026-10-13 | 1bounded |
| 2026-10-14 | 3bounded |
| 2026-10-15 | 3bounded |
| 2026-10-16 | 0bounded |
| 2026-10-17 | 16bounded |
| 2026-10-18 | 1bounded |
Can we compare these dates?
Coverage for the selected measure. Colour describes evidence, not popularity.
No clean full-day comparison is available for this selection in this snapshot. 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.
App ComposerNot measured for these dates
This source does not report browser returns. Tab activity cannot establish a returning audience.
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 4 dated release and collection notes
- App Composer · From a live example to your own starting point
The released demo sends Make this collection to Init’s composition recommendation without overwriting a saved draft. Independent browser interaction checked that explicit Use changes the form while preserving authored settings; the configuration can be downloaded with the two source pins. The live reference explains where to find its fictional sample and links back to the original guestbook item. This demonstrates the available configuration and handoff, not a new creator deploying a production collection or independent adoption. Source pins, privacy and owning release gates remain in force. Browser QA must use the supported verification header; bounded open counts can include unmarked inspection and are not demand evidence.
Read release evidence · reviewed 2026-10-18 - App Composer · The published pieces keep their own identity
Opaque credential and dotenv-comment regressions plus adversarial archive fixtures fail closed. The exact current production release and a separately bound preview passed negative credential-path and package-content checks. This is actual release-path and artifact coverage, not a guarantee against every secret format or proof that a new creator has completed onboarding. Private account state and migration work remain separate.
Read release evidence · reviewed 2026-10-18 - App Composer · Creator profile and moderated guest path released
Reviewed current canonical source and owning release evidence against the public destination on 16 October 2026. Composer and independently deployed Linkarooie identities agree with the owning release record. Native owner Publish/Hide and Remove-confirm interaction remain partial; API curation and public visual checks are separate evidence.
Read release evidence · reviewed 2026-10-16 - App Composer · Collection began
First source-reported collection date. Earlier activity is unavailable; the first day may be partial.
Follow the numbers to their source
Every measure has a definition, a collection boundary and blind spots.
App Composer5 measures available
Live aggregate endpoint · generated
- Collection began
- 2026-10-13T00:00:00.000Z
- Comparable history from
- Not established
- Source revision
- 158d0617fbb21ecdce9f4d2203c58d7375e031d3
- Daily counters stop at 1000 per app/event/surface and shared per-location rate limits may drop events.
- The first recorded UTC day is 13 October 2026 and is partial; daily counts expire after 35 days. Missing earlier history is unavailable, not zero.
- Optional publishers can lose events during outages. Marked verification probes are excluded; reloads, unmarked automation and bots can count.
- No visitor identity, sessions, return rate, private creator activity or vault contents are collected. Today is partial; these are bounded recorded signals, never lifetime totals.
- App opens 1,294Bounded count
- Successful public mini-app home-page HTML requests across standalone and composed versions. Reloads and bots may count; not people, sessions or conversions.
- Recorded app actions 41Bounded count
- Guestbook contribution-page opens plus accepted completed Link Check inspections. Different action types, not unique people or a conversion funnel.
- Guestbook contribution opens 17Bounded count
- Successful public Guestbook contribution-page HTML requests, including repeated opens; not image downloads, submissions, publications or unique people.
- Completed inspections 24Bounded count
- Link Check inspections counted by the owning app after completion; not clicks, deployment checks or unique users.
- Guest postcards received 2Partial measurement
- New pending guest postcards counted after committed acceptance by Guestbook, across connected standalone and composed routes. Not approvals, publications, unique people or a conversion rate. Before the first retained recorded receipt, history is unavailable. The first recorded UTC day is partial; later zero means no recorded receipt, not proof that nobody submitted. Optional recording can drop events.
What am I looking at?
Link Check inspections reported by the owning app after completion. Repeated jobs may count; these are not unique users, outbound clicks or deployment checks.
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?
App opens show recorded access. Guestbook contribution opens show content being viewed. Completed Link Checks show a specific job finishing. These are different stages of value, measured separately—not a shared conversion funnel.
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)
- App Composer: Mini-app opens is not an exact counter.
Is the app delivering value?
Received guest postcards count contributions accepted as pending for moderation. This is an admission count, not the current queue size. Optional reporting can miss submissions; it does not establish approval, publication, unique people or a conversion rate.
Creator activation, successful publications and outbound Linkarooie interactions remain unmeasured in this public report.
Repeat use, task completion rates and value over time need app-specific outcome definitions and matched observation. Dividing these totals would invent a rate.
If you’re assessing the business
Early product instrumentation, with material evidence gaps.
- Usage
- Bounded access and task counters. Guest postcard receipts, where reported, count submissions accepted for moderation; these signals do not establish users, creator activation or successful publication.
- 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 dossiersTake the evidence with you
Share report
Report details
- Snapshot
- 8496128e32ddfd0bddf8da66
- Captured
- 2026-10-23 03:09:27 UTC
- Dates
- 2026-10-12 – 2026-10-18
- Time zone
- UTC; dates may differ from your local day