Jubal

Build in public

Building Jubal in public, without inflated claims.

Jubal is a small visual clipboard project being shaped around one visitor job: find a useful visual, copy it, and paste it into the place where the conversation is happening.

Quick Answer

Definition

The build-in-public page records what Jubal has shipped, what is limited, and what needs review before stronger claims are made.

Summary

Use this page to check product status, correction posture, source rules, and honest limitations.

Key Facts

  • The current product foundation includes copy actions, WA-adjacent copy, packs, embeds, privacy controls, and launch checks.
  • Popularity and platform claims require evidence before they become public claims.
  • Outside sticker, emoji, or GIF sources require license review before import.

Rules

  • Share implemented behavior before ambition.
  • Record corrections and limitations in public language.
  • Keep monetization, accounts, and submissions unclaimed until they exist.

Thresholds

Claim type Required support Public outcome
Product behavior Working route or test Describe the implemented action.
Platform behavior Documentation or real-device matrix Use cautious language.
Third-party assets Source and license record Publish only after review.

Checklist

  1. State what shipped.
  2. Name what is still limited.
  3. Point to contact for corrections.

Scenario

If a WhatsApp behavior works on one Android device, the build notes should say it was tested there and avoid claiming universal support.

Current status: public foundation, starter asset library, copy actions, WA-specific copy path, packs, embeds, privacy controls, and launch checks are in progress.

Public rule: every asset source, platform claim, analytics choice, and growth experiment must stay traceable.

Build-in-public rule: share what changed, what broke, what was corrected, and what is still uncertain.

What I will share

Useful progress Working packs, copy behavior, launch checks, and product decisions that improve the visitor path. Trust decisions Rights records, consent boundaries, local analytics, and why some tempting shortcuts are delayed. Compatibility notes Where copy and paste works, where browsers block it, and which fallback paths remain available. Corrections A route for rights issues, accessibility notes, copy failures, and product corrections.

What I will not claim yet

No popularity claims until there is enough aggregate, consented behavior data.

No third-party sticker, emoji, or GIF imports until license terms are checked and recorded.

No guarantee that every paste target accepts every image format or sticker path.

No accounts, checkout, premium downloads, or user submissions until those workflows actually exist.