Makers build in public but their dev logs get nobody's attention
Problem Breakdown
Build-in-public is the standard advice: share your progress on X and it compounds into an audience. In practice, most makers post screenshots of their code and stats into silence, because nobody follows a stranger's changelog.
What actually works is narrative: the struggle, the decision, the result. But makers are builders, not writers. They don't know how to turn "fixed the onboarding bug" into a story people engage with, and they give up on build-in-public after a month of shouting into the void.
Consistency is the second killer. Build-in-public only compounds with months of regular posting, and manual posting dies in week two.
Solution Architecture
Build a build-in-public narrator. The maker connects their GitHub and their product's analytics. Every day the tool sees what actually happened: features shipped, users gained, revenue moved, problems hit. It drafts a daily or weekly update that tells the story, not the changelog: "Spent all day on onboarding, lost two users to it, here's the fix and what I learned."
It maintains the narrative thread across posts (ongoing sagas, past milestones) so followers get a story to invest in, and it schedules everything automatically.
Your Build Prompt
You are an experienced full-stack developer. Build a complete, working version of the following tool. Do not ask questions, do not leave placeholders, do not write TODOs. Make real, working code that runs on the first try. TOOL: Makers build in public but their dev logs get nobody's attention WHAT IT MUST DO: Build a build-in-public narrator. The maker connects their GitHub and their product's analytics. Every day the tool sees what actually happened: features shipped, users gained, revenue moved, problems hit. It drafts a daily or weekly update that tells the story, not the changelog: "Spent all day on onboarding, lost two users to it, here's the fix and what I learned." CORE FEATURES TO BUILD: 1. Connect GitHub activity, Stripe revenue, and basic product analytics 2. A daily digest of what actually happened across all sources 3. A story-first post drafter that turns events into narrative updates 4. An ongoing narrative memory so posts reference past milestones and sagas 5. Automatic scheduling to X and LinkedIn 6. A weekly recap generator with metrics woven into the story TECH STACK: Next.js, TypeScript, GitHub API, Stripe API, OpenAI API RULES: - Use strict TypeScript everywhere. Define proper types and interfaces. No any. - Validate all user input with a schema library (Zod or equivalent). - Handle errors cleanly: show a clear message to the user, log the detail for the developer. - Handle loading and empty states in every view. - Make it fully responsive: mobile, tablet, and desktop. - Keep the design clean and professional: clear typography, good spacing, real icons (Lucide), smooth hover states. SETUP: Start from a fresh Next.js (App Router) TypeScript project and build the features above one by one, verifying each runs before moving to the next. Finish with a short summary of what was built and how to run it.
Resource Grid
Before you build, use the complete kit.
Beyondkitter is a complete app development kit with everything you need to plan, build, and ship your tool faster.
Open BeyondkitterBuilt the fix already? Get it verified and showcased here