STUDIO PRODUCT · LENARD DESIGNS (OWN PRODUCT)

Studio Product / React analytics SDK

Tracky

Our own React analytics SDK: opt-in event tracking that batches to an endpoint you control.

7 · Initial primitives

Tracky analytics SDK diagram: a React component sending a named event through the SDK in batches to a developer-owned endpoint.
OWNERSHIP
Studio product
CLIENT
Lenard Designs (own product)
OUR ROLE
Product design and SDK engineering
STATUS
v0.1.0, not published

Not on npm yet and no hosted dashboard. The playground is shown on request until the package is published.

01 · Problem

Product teams had to choose between a hosted platform and hand-built instrumentation.

React teams wanted to understand page views, feature usage and conversion flows. A hosted platform would own the data path; hand-rolled tracking drifts across pages and is easy to get wrong, especially around what must never be collected.

  • 001Hosted tools own the event data and the endpoint
  • 002Hand-rolled tracking drifts across pages and features
  • 003Automatic capture can leak field values and secrets
Tracky playground: activating the Button sends one component_interaction event to the event stream while page capture stays off.
Tracky playground: the Input and Textarea components report no event, and typed values are never read.

02 · Idea

An SDK that measures the app without owning the data.

Tracky pairs an AnalyticsProvider and a useAnalytics hook with independent, opt-in capture switches for page views, clicks, form submits, input changes, frustration clicks, cursor heat maps and scroll depth. A separate registry ships analytics-aware Button, Checkbox, Switch and Select primitives as source, installed with the tracky CLI, so teams keep and theme the code they use. Events buffer and batch to whichever endpoint the integrator configures.

Opt-in by default: measurement stays explicit, and field values never leave the page.

03 · Result

A working scaffold with the privacy boundaries drawn in.

The SDK tracks initial load and route changes, buffers and retries batches within bounds, and emits documented component actions while every primitive stays usable without a provider. The playground renders the same registry source and intercepts the SDK's request in the page, so each action is visible without being sent anywhere. Tracky is at v0.1.0, is not published to npm, and hosted dashboards and license verification are explicitly out of scope.

Tracky playground: toggling the Checkbox and Switch streams component_interaction events while field values stay unread.

7

INITIAL PRIMITIVES

Counted from the v0.1.0 package manifest

4

DOCUMENTED COMPONENT ACTIONS

Listed in the published SDK documentation

HOW THESE NUMBERS WERE MEASURED

Both counts come from the v0.1.0 package manifest and the SDK documentation in the repository. Tracky is an internal product, not client work, and is not yet published to npm.

Next project

Zizi

PropTech / Real estate platform for diaspora buyers