Why we ship small products instead of one mega-app

Small is not a branding pose

Zetty Factory ships separate products on purpose: WaveLog for live radio exploration, PodWave for podcast listening with notes, iRing for family school weeks, Walking Story for walk capture and stories, and Bookus for reading-shaped experiments. None of them try to be an everything app with a radio tab, a podcast tab, a parenting tab, and a walking tab stapled together.

That choice is practical. Different jobs have different failure modes, privacy needs, and moments of use. A mega-app forces one navigation model, one account gravity well, and one release train onto lives that do not share a rhythm. Small products let each surface stay honest about what it is for.

One job per product (most of the time)

WaveLog should feel like tuning the world — countries, genres, stations, play. PodWave should feel like attentive listening — feeds, episodes, timestamped notes. iRing should feel like a calm household board for the week. Walking Story should feel like pocket capture that does not freeze when signal dies. When those jobs share one chrome, each becomes a compromised submenu.

Users also arrive with different intent. Someone opening WaveLog on a Sunday morning is not the same mental mode as a parent checking Thursday’s academy pickup. Mixing those intents in one home screen creates noise that no amount of onboarding can paper over.

Build → explore → improve → repeat

Our studio loop, also sketched on the About page, is deliberately boring:

1. Build — turn an idea into something real enough to use.
2. Explore — try adjacent paths without pretending every experiment must become a platform.
3. Improve — change the product based on friction from real use.
4. Repeat — start the next focused idea with what you learned.

Small products make that loop faster. Shipping a fix to WaveLog playback does not require freezing iRing’s school-week work. Exploring a Walking Story sync idea does not demand a redesign of PodWave’s library. Scope stays local; learning can still travel across the studio.

What we reuse (and what we refuse to merge)

Independence does not mean reinventing every bolt. Shared studio pieces — brand voice, design tokens, hosting patterns, legal templates, analytics caution — can be common. What we refuse to merge casually:

• Data models that mix children’s school documents with public radio favorites
• Permission prompts that do not match the moment (location on a walk vs. nothing on a radio page)
• Release urgency that couples unrelated audiences
• “Just one more tab” features that dilute the product sentence

If a feature cannot be explained in one plain sentence that belongs to that product, it probably wants its own home — or it wants to stay an experiment.

Experiments are allowed to stay small

Some ideas become products. Some remain experiments. Some become something unexpected. That sentence is not a slogan to print on a mug; it is permission to stop inflating every prototype into a suite. The experiments area and unfinished edges (Walking Story still marked in development) are part of an honest catalog, not a failure to “go big.”

How small products help users

• Clearer trust. Privacy stories are easier when a family planner is not also a discovery feed.
• Faster comprehension. Landing pages can say what the app does without a feature matrix.
• Less guilt. You can use WaveLog without adopting a whole lifestyle OS.
• Better depth. Focused time goes into playback triage, school-week flows, or local-first capture — not into unifying five menus.

A concrete week inside the studio

Imagine a week where WaveLog needs a clearer error state for dead mounts, iRing needs a supply checklist tweak for PE days, and Walking Story needs a shorter GPS timeout on capture. In a mega-app those three changes compete for the same release branch, the same QA pass, and the same “don’t ship until everything is green” anxiety. In a small-product studio they can move on different clocks. WaveLog can ship a listening fix without holding a family planner hostage. Walking Story can keep iterating on local-first save while PodWave’s note UX stays stable for people mid-season on a show.

That operational freedom is half the reason we stay small. The other half is narrative honesty: each product page can make one promise. WaveLog promises exploration of live radio. PodWave promises attentive podcast listening. iRing promises a calmer school week. Walking Story promises capture that respects a walk. Bookus promises a reading-shaped experiment. When promises multiply inside one binary, marketing copy becomes a list of apologies.

What “small” does not mean

Small does not mean unfinished forever, unserious engineering, or zero ambition about polish. It does not mean we refuse accounts, sync, or sharing when a product genuinely needs them. It means we refuse to grow by absorbing neighboring jobs just because the codebase is nearby. A focused app can still be deep: stream triage in WaveLog, timestamp notes in PodWave, document triage in iRing, local-first capture in Walking Story — each of those deserves real attention.

Small also does not mean isolated brands with no family resemblance. Visitors should still feel they are in a Zetty Factory catalog when they move from Products to this journal. Shared craft is welcome; forced feature merger is not.

How to browse the catalog

Start at Products for the live and in-progress lineup, or About for the studio stance. Use this journal for guides that go deeper than a landing page — adding stations in WaveLog, troubleshooting playback, PodWave streams, iRing school weeks, Walking Story’s local-first save path.

We are not anti-ambition. We are anti-fake scope. Ambition, for us, looks like several sharp tools that respect the moment you open them — not one blunt instrument that claims every moment at once.