Featured Projects Snippbot is source-available

VideoVulcan, built by a Snippbot Swarm

VideoVulcan was built as a Shipaton project: humans made the product, store, legal, and spend calls; Swarm agents planned, built, integrated, QA'd, and fixed the software toward Google Play internal testing.

VideoVulcan app icon

VideoVulcan

Live on Google Play

Upload 3-8 photos, write one line, pick a style, and mint a short AI-generated movie with a making-of reveal and watermarked share file.

90
tasks planned
86
tasks completed
5
specialist agents
717/717
backend tests passed
2
E2E cycles
v3
live on Play internal testing
VideoVulcan create screen showing cast slots, one-line prompt, style presets, consent, and Mint button VideoVulcan store feature graphic reading Your photos. One line. Your movie.

Phase by phase

The same swarm process, shown with this app's decisions, shipped features, checks, and release evidence.

  1. 1 Brainstorm & Charter
  2. 2 Plan
  3. 3 Build
  4. 4 Integrate
  5. 5 Review / QA
  6. 6 E2E
  7. 7 Release
1

Brainstorm & Charter

The flagship movie-maker was scoped into a tight FTUE and a traceable AI pipeline.

3-8 photos per movie
Users upload a handful of their own photos to cast the movie.
1 line to direct it
One sentence is enough to set the story.
3 style presets
Epic, Noir and Cartoon looks at launch.
VideoVulcan Snippbot Swarm UI during Brainstorm & Charter
  • Locked the simple user promise: photos plus one line become a short movie, not a general video editor.
  • Chose stylize-first portraits so the making-of screen reveals meaningful cast art before render completion.
  • Kept Google sign-in, Mints, watermarking, deletion, and Play docs in scope for an internal-testing release.
2

Plan

The plan divided the app into auth, ledger, render, audio, stitch, store, and release lanes.

90 tasks planned
Sign-in, credits, rendering, audio, store and release, split into owned tasks.
5 specialist agents
App, backend, pricing, art and launch each had their own agent.
VideoVulcan Snippbot Swarm UI during Plan
  • Tasks covered Google Sign-In, Mint ledger, RevenueCat mapping, Claude moderation/script, Gemini stylize-first, Seedance render, Hume audio, stitch, and Play submission.
  • Dependencies kept entitlement, render, and release work tied to the right upstream contracts.
  • Our developers owned product, pricing, store, legal, and spend decisions while the swarm executed the plan.
3

Build

Focused agents built the client, backend, AI workflow, economy, and release assets in parallel.

751 automated tests passing
Sign-in, Mint credits, moderation, rendering and deletion are checked on every build.
100% movies watermarked
Every exported movie carries a visible AI-generated label.
VideoVulcan Snippbot Swarm UI during Build
  • Landed onboarding, create flow, Google Sign-In hooks, Mint ledger, premiere screen, share/save affordances, and account deletion.
  • Backend work connected Claude moderation and script planning, Gemini image stylization, Seedance video rendering, Hume audio texture, and the stitch stage.
  • The stitch stage burns in the VideoVulcan AI-generated mark, adds MP4/XMP provenance, appends the end card, and strips source metadata.
4

Integrate

The app moved from isolated work streams into one integration branch for review.

86/86 tasks merged
Every completed task landed in one shared app build.
10 branches merged
Each agent and reviewer worked on its own branch, then merged into the app.
188 agent work sessions
Short, focused runs: one agent, one task at a time.
VideoVulcan Snippbot Swarm UI during Integrate
  • Client, backend, monetization, store-art, legal, and release evidence landed together for whole-app checks.
  • Integration preserved the finished work while surfacing dependency gaps for owners instead of hiding them in chat.
  • Follow-up commits from QA and E2E loops were reintegrated as the Android release build matured.
5

Review / QA

Independent review checked the release promises against the implemented app and backend.

81 issues caught before release
Reviewers filed each with evidence and routed it to the owning agent.
VideoVulcan Snippbot Swarm UI during Review / QA
  • Review covered auth, Mint grants, render contracts, watermark/provenance, deletion, Play docs, and release-build evidence.
  • The stylize-first work passed 79 focused tests, then the backend suite passed 717 tests in the integrated codebase.
  • Findings were routed back to owners as concrete work instead of becoming a single overloaded agent’s unchecked TODO list.
6

E2E

A release-configured Android build was installed and walked through the first-movie flow.

2 end-to-end test rounds
The signed release build was installed and walked through the first-movie flow.
0 crashes in the final test
Launch, sign-in and the create flow ran cleanly on version 3.
VideoVulcan Snippbot Swarm UI during E2E
  • The emulator walkthrough covered onboarding, create, first Mint, making-of, premiere, and Android share sheet.
  • The run confirmed the Hermes Intl.PluralRules crash stayed fixed in a release-configured build.
  • The share sheet received a real MP4 named for the VideoVulcan movie, proving the client produced a file rather than only in-memory state.
7

Release

The swarm prepared the Android package, store surfaces, and public proof for internal testing.

v3 live on Google Play
Testers install it from Google Play internal testing.
5 days kickoff to version 3
The swarm started Sept 23; version 3 reached testers Sept 28.
VideoVulcan Snippbot Swarm UI during Release
  • VideoVulcan was prepared for Google Play internal testing with launcher icon, feature graphic, Play docs, data safety, and deletion flow.
  • The project page uses the real store feature graphic rather than an internal placeholder reel.
  • Our developers made the product, pricing, store, legal, and spend decisions; the swarm did the rest.

Inside the swarm

Profile Design Specialist avatar
Profile Design Specialist

"Stylize-first accidentally fixed the weakest part of the reveal... The board reveals actual stylized portraits - pop, done."

Profile Design Specialist avatar
Profile Design Specialist

"The store outputs are clean, professional, no debug text, honest, and on-brand; the feature graphic and screenshots render at the required dimensions."

Steven avatar
Steven

"The stylize-first stage already exists in the integrated codebase... All 79 stylize tests pass... All 717 backend tests pass."

Swarm team

Pam PM / Producer avatar

Pam PM / Producer

plan ownership, store/legal packaging, launch sequencing

Danny Dev avatar

Danny Dev

backend, auth, ledger wiring, API contracts, and release build work

Adam Dev avatar

Adam Dev

systems review, compliance surfaces, E2E artifacts, and integration support

Ada Art avatar

Ada Art

brand, store artwork, screenshots, and visual presentation

Mona Monetization avatar

Mona Monetization

Mint economy, RevenueCat mapping, refund and entitlement rules

Why a swarm beats one do-everything agent

The difference is not just more messages. It is separate context, separate branches, independent review, and a decision trail that survives the whole project.

Specialists keep context sharp

DecorMuse had 6 specialist agents and VideoVulcan had 5, so mobile, backend, design, monetization, QA, and release work could stay focused instead of crowding one context window.

Parallel branches beat one queue

The two swarms completed 67 and 86 tasks while agents worked on their own branches, then brought finished slices back through integration.

Independent review catches more

QA and E2E gates surfaced 13 DecorMuse findings and 1 VideoVulcan E2E finding, then routed fixes to owners instead of asking the author to grade itself.

Integration is auditable

Tasks, branches, findings, gates, release notes, and message ids create a trail from charter to Play internal testing.

Humans stay at the decision points

Our developers kept product, pricing, store, legal, and spend authority while the swarm handled planning, build, integration, and verification.

Snippbot got better along the way

Running two full app swarms in parallel drove real upgrades to Snippbot's swarm engine: smarter conflict recovery that keeps finished work, stricter checks that a task's work actually landed, and safe re-integration of follow-up commits. Those upgrades now ship to every Snippbot user.

More projects