SharetoBoard
Evidence updated July 18, 2026

Release truth, separated by product.

“The code exists,” “automated checks pass,” “a package was built,” “a live workflow passed,” and “a Store approved it” are different claims. This page records the strongest evidence currently available and the exact gates still open.

Overall: documentation and submission copy can be completed now. No product should be represented as publicly released or fully accepted until its remaining live, package, signing, and marketplace gates are recorded.

Product readiness

Candidate · No-Go

SharetoBoard Android v1.2-beta2, Build 4

The invite-only closed-beta candidate can produce an unsigned AAB. Its Play listing, data-safety draft, beta-readiness guide, launch guide, and blocker checklist exist.

  • Still required: exact candidate commit and digest
  • Physical-device matrix and signoff
  • Controlled signing and certificate fingerprint review
  • Final screenshots and Play Console completion
  • Named GO decision

Current public truth: free invite-based candidate; billing, Notion, offline delivery, native media prep, and external image/video/PDF sharing are paused.

Pre-release

SharetoBoard Chrome Free v1.6.0

The free browser-capture build was packaged and recorded with 33 automated checks. It uses board-only setup and no active SharetoBoard backend delivery.

  • Still required: live unpacked and packed Chrome regression
  • Authenticated Poppy board testing
  • Final Store screenshots and promotional assets
  • Publisher dashboard and privacy answers
  • Chrome Web Store review and Store-installed smoke test
Private preview

SharetoBoard Chrome Pro v1.7.0

The Specialist Links feature and public preview materials were merged. A follow-up code correction is open because over-escaped URL-validation expressions in merged v1.7.0 fail the syntax gate. The corrected branch passes 35 automated checks locally.

  • Merge and re-run the syntax/regression correction
  • Pack and inspect the exact candidate ZIP
  • Test private Google, private password, public, and revoked Specialist links
  • Verify iframe and Open Full Poppy fallback behavior
  • Capture Store evidence and complete dashboard review

Boundary: no API key, backend, MCP, Tentaclaw, prompt auto-fill, or auto-send.

v0.3.0 release candidate

Tentaclaw MCP Server + first-party skills

The v0.3.0 release candidate includes six MCP tools, a local stdio server, stronger request controls, four first-party skills, setup guides for four MCP clients, extensive manuals, reproducible packages, and security documentation.

  • Complete live Poppy testing for all six tools
  • Validate Codex, Claude, OpenClaw, and Hermes individually
  • Complete final package and security review
  • Approve the release artifacts and checksums
  • Publish the public source and release packages

Automated checks: formatting, 24 tests across Python 3.10-3.12, the production dependency audit, clean installation, package builds, skill bundles, software bill of materials, and checksum verification have passed. Live Poppy and client testing remain separate requirements.

What can be made submission-ready before final testing

Can be completed

  • Store names, short and detailed descriptions
  • Permission and data-flow justifications
  • Privacy, support, terms, security, and deletion guidance
  • Manuals, troubleshooting, tester scripts, release checklists
  • Screenshot shot lists and dashboard answer sheets
  • Package-content allowlists, SBOM instructions, checksums, and release-note templates

Cannot be pre-claimed

  • Physical-device success
  • Private/public Poppy access behavior
  • Chrome iframe compatibility
  • Exact signed package digest and certificate
  • Marketplace approval
  • Cross-client Tentaclaw acceptance
  • Live Poppy API compatibility for every tool

Release rule

We call a product ready only after the final build passes its automated checks, required live workflows, privacy and Store review, package inspection, signing or checksum verification, and final approval. A promising design or passing mock is not treated as a completed release.

Open manualsSee pricing and availability