Peekling Company guide · v0.1

For product teams

Bring a Peekling into one product moment.

Evaluate and introduce Peekling through a telemetry-free browser runtime that keeps product ownership with your team.

01 · AVAILABLE TODAY

Evaluate Peekling for one real product moment.

Product teams can use this guide to choose where Peekling belongs, assign ownership, and review a small release. Peekling 0.1.0 provides a self-contained browser runtime, developer validation tools, and independently versioned character Packs. Your team chooses the Pack, Plan, resource origin, and product moments where the character appears.

Today, teams self-host or use pinned CDN assets, connect their own product systems at the host layer, and source character artwork independently. The browser runtime and validation tools are inspectable building blocks.

02 · CHOOSE THE RIGHT MOMENT

Start where a small reaction earns its place.

A Peekling works best when it acknowledges something that already matters to the visitor. It might react after a document saves, keep someone company during a bounded wait, or add warmth to an otherwise quiet page.

Give the character clear space around critical controls. Let motion acknowledge a real product moment, keep the shared rest control easy to reach, and make every response easy to understand.

03 · KNOW WHO OWNS WHAT

Separate art, policy, and product logic.

Production ownership

Character Pack
Owns artwork, available States, movement mappings, timing, and license.
Peekling Plan
Owns the baseline and the declared response to supported Events.
Host application
Owns business logic, user data, controls, services, and application Events.
Visitor
Owns whether the character remains visible on that site.

04 · PLAN A ROLLOUT

Move from one prototype to one controlled release.

  1. Prototype the behavior with the real runtime in the playground.
  2. Review the Pack's artwork rights, attribution, and public files.
  3. Pin exact runtime and Pack versions for production delivery.
  4. Validate Configuration and Pack data before the deployment build.
  5. Test CSP, CORS, loading failure, reduced motion, and visitor dismissal.
  6. Verify the real product in Chromium, Firefox, and WebKit.

Begin with one route or product moment. A narrow release makes it easier to judge how the character fits before expanding it across the product.

05 · PRIVACY AND ACCESS

Keep control visible.

The Peekling runtime runs locally in the browser. Services and analytics belong to the host product and follow its privacy, consent, retention, and security policies.

  • Preserve the shared rest menu and a normal "Show again" action.
  • Respect reduced motion and test a stable readable tableau.
  • Keep the character pointer-transparent so focus stays on product controls.
  • Set a density cap when decoded image memory matters on target devices.

06 · EVALUATION SCOPE

Know what each review proves.

Runtime and Pack checks verify accepted shapes, bounded resources, image hashes, lifecycle behavior, and supported browser contracts. Your legal, security, and accessibility reviews cover artwork ownership, regulatory requirements, the complete host product, and its intended audience.

Peekling 0.1.0 is the self-managed browser engine and validation toolchain. Teams own asset delivery, organizational policy, product analytics, and support operations inside their existing systems.

07 · NEXT STEP

Review the implementation

Follow the developer path from hatch to teardown.

Open the developer guide →

Trying Peekling on a product? Star the engine repository, contribute one focused improvement, or tell us where your Peekling lives.