The Developer's Dilemma

You build a mobile game. You ship it to the App Store. Then you pray someone finds it.

This is the standard playbook for indie game studios — and it's broken. Apple's 15M+ apps make discovery a lottery. UA costs are through the roof. And your beautifully crafted Cocos Creator game sits in a sea of clones.

At CCFish, we asked a different question: what if we stopped treating distribution as a marketing problem and started treating it as an infrastructure problem?

The answer became the PlayableTon pipeline.

What Is the PlayableTon Pipeline?

The PlayableTon pipeline is a fully automated deployment chain that takes a Cocos Creator game build and turns it into a distributable Telegram Mini App in under 60 seconds:

```bash

Step 1: Build Cocos Creator for web-mobile

cocos compile -p web-mobile

Step 2: Inject Telegram Mini App SDK

cat > game/index.html <<'HTML'

<script src="https://telegram.org/js/telegram-web-app.js"></script>

<script>

Telegram.WebApp.ready();

Telegram.WebApp.expand();

</script>

HTML

Step 3: Deploy to Cloudflare Pages

npx wrangler pages deploy . --project-name playableton-ccfish

Step 4: Bot auto-picks up the new URL

(already in prisma/seed.ts)

```

Why This Matters for Distribution

Traditional mobile game distribution looks like this:

- Build game → Submit to App Store → Wait for review → Run paid UA campaigns → $5-7 CPI → Pray

Our Telegram Mini App pipeline looks like this:

- Build game → Deploy to Cloudflare Pages → Bot serves it instantly → Users discover via Telegram → $0 distribution cost

The key insight: Telegram has 900M+ monthly active users and a built-in mini app platform. By deploying CCFish as a TMA through the PlayableTon bot, we turned a developer CI/CD workflow into a zero-cost distribution channel.

The Architecture

| Component | Tech | Cost |

|-----------|------|------|

| Game Engine | Cocos Creator 2.4.15 | $0 (open source) |

| Hosting | Cloudflare Pages | $0 (free tier) |

| Bot | grammY + Prisma | $0 (serverless) |

| Database | Cloudflare D1 | $0 (5GB free) |

| Discovery | Telegram WebApp SDK | $0 |

Total infrastructure cost for CCFish TMA distribution: **$0/month**.

The Dev-to-Marketing Feedback Loop

Here's what makes this approach powerful from a marketing perspective:

**Every CI/CD deploy IS a content update.** When we ship a new CCFish build, the PlayableTon bot serves the latest version instantly. No App Store review, no staged rollout, no version fragmentation. Users always see the latest game.

**Every bot interaction IS a marketing impression.** The `/start` command shows a portfolio of games. Each game has a thumbnail, description, and play button. The bot itself becomes a discovery engine.

**Every game session IS analytics data.** Cloudflare Workers capture play events, retention, and sharing behavior. This data feeds back into the game design and marketing decisions.

How We Built It

The PlayableTon bot (grammY + Prisma) manages game entries:

```typescript

// prisma/seed.ts — game portfolio entry

{

name: 'CCFish',

slug: 'ccfish',

description: 'Classic crypto fish game — catch, collect, and compete!',

thumbnailUrl: 'https://playableton-ccfish.pages.dev/thumb.png',

gameUrl: 'https://playableton-ccfish.pages.dev',

active: true

}

```

The bot's `/play` command presents an inline keyboard with all games. When a user taps CCFish, Telegram opens it as a fullscreen mini app via the WebApp API.

For the TMA integration itself, only three lines of JavaScript are needed:

```javascript

Telegram.WebApp.ready();

Telegram.WebApp.expand();

Telegram.WebApp.enableClosingConfirmation();

```

That's it. A complete distribution channel ready in under 50 lines of orchestration code.

The Results So Far

- Zero distribution cost per install (vs. $5-7 CPI on Facebook)

- Instant updates — no App Store review cycle

- Cross-game promotion built into the bot's command structure

- Full analytics pipeline via Cloudflare Workers

- 5 games in the portfolio: CCFish, Casino Slot, SlotX, Crisis Empire, ChezBot

The Takeaway

The line between developer infrastructure and marketing has disappeared. A CI/CD pipeline isn't just for shipping code anymore — it's your go-to-market strategy. The same Cloudflare Pages deployment that engineers use for preview builds becomes the infrastructure for user acquisition.

For indie studios like ours, this isn't just clever — it's survival. When you can't spend $50k/month on UA, you need every tool in your stack to pull double duty. Your build pipeline should also be your distribution channel. Your deployment should also be your launch. Your bot should also be your storefront.

That's what Hybrid Dev+Marketing looks like in practice. And it costs $0.