Operating facts
Public product site is live. iOS and Android store destinations are public. Current screenshots were captured from the public site on July 13, 2026.
LiveBato Labs product
Current screenshots
Public product surfaces captured or sourced from the live product site.
Screenshots are evidence of current public product surfaces and distribution, not evidence of adoption or product-market fit.
Product facts
What the product is now.
| Field | Current answer |
|---|---|
| Intended user | People who want lightweight, intentional presence with trusted relationships rather than a public social feed. |
| Current functionality | Hum's public surfaces describe private presence, lightweight sharing, contact and privacy paths, and iOS and Android distribution destinations. |
| Current status | Live public product surface with App Store and Google Play destinations. |
| Bato Labs role | Bato Labs built and released the public product and distribution surfaces. |
| Role of AI | No public AI capability claim is made for Hum on this page. Hum is used here as product-building, release, and distribution evidence. |
| Live destinations |
Important decisions
Product and technical decisions are part of the evidence.
- Treat private presence as the product boundary rather than a growth-at-all-costs social feed.
- Keep privacy, contact, and legal paths visible on public surfaces.
- Use app-store distribution as release evidence without overstating adoption.
Release evidence
Current operating facts.
Release evidence
Hum demonstrates product packaging, distribution, privacy surface, and mobile release discipline.
Bato Labs product
Read more
What this proves
The proof is useful because it is bounded.
What it proves
Bato Labs can ship and maintain a distinct consumer app surface with public distribution paths.
Bato Labs product
What it does not prove
This does not prove enterprise AI delivery, product-market fit, user scale, retention, or revenue.
Boundary