Checked platform limits
Platform limits
- Post text limit300 graphemes (user-perceived characters) (official source, checked 2026-11-21)
- Attached imagesUp to 4 images per post (2 MB max each, with alt text) (official source, checked 2026-11-21)
Copyable template
Post 1 (under 300 graphemes, attach 1 screenshot or short demo clip with alt text): I just shipped [Product Name]: [plain one-sentence description of what it does for whom]. Built it because I got tired of [specific everyday annoyance]. Try it here: [Product URL] #[relevant community tag] Reply 1 (under 300 graphemes, attach a second screenshot of the core screen): How it works in practice: 1. [Step one] 2. [Step two] 3. [Immediate output] Pricing is [free / one-time / monthly price]. No [friction point, e.g., credit card or account wall] to test it. Reply 2 (under 300 graphemes): Tech notes for curious builders: built with [stack] over [timeframe]. Still early, so if [edge case or missing piece] would make this useful for your workflow, reply below and I will look at it this week.
When to use this template
Use this template when announcing a new v1, open beta, or side project to Bluesky's builder, open-source, and design communities. Because Bluesky runs on chronological following feeds and topic-specific custom feeds rather than an aggressive engagement algorithm, clarity and genuine community context matter far more than viral hooks.
Keep the opener self-contained inside the 300-grapheme cap so someone seeing only Post 1 in a custom feed understands the product, sees a crisp visual, and has the direct link right away. Add Replies 1 and 2 immediately after publishing so anyone who clicks into the thread gets the workflow and builder backstory.
How to fill each placeholder
- [plain one-sentence description]: Spend your 300-grapheme budget on concrete nouns and verbs. Tell people what the app does on their machine or in their browser rather than describing how it makes them feel.
- [specific everyday annoyance]: Name a relatable friction point in ten words or fewer. Personal frustration feels human on Bluesky and stands out from automated promo posts.
- #[relevant community tag]: Pick one or two tags that actually feed a Bluesky custom feed, such as #buildinpublic, #indiedev, or #webdev, instead of stuffing six generic hashtags.
- [Step one / two / output]: Show the shortest path from opening the app to getting value. Pair this reply with an uncropped UI screenshot and descriptive alt text.
- [edge case or missing piece]: End with a grounded invitation for feedback. Bluesky replies often turn into early bug reports and reposts from peers when you sound approachable.
Filled example (made-up product)
Example using a made-up Mac clipboard utility called ClipShelf: Post 1: I just shipped ClipShelf: a local-first Mac clipboard manager that strips tracking parameters and saves code snippets with syntax preview. Built it because I kept losing terminal commands between deploys. Try it here: https://clipshelf.example #buildinpublic #macdev Reply 1: How it works in practice: 1. Press Option+V anywhere to search your last 500 copies 2. Auto-detects JSON, SQL, and shell commands with clean formatting 3. Everything stays in an encrypted local SQLite file, zero cloud sync Pricing is $14 one-time. Free 14-day trial with no account required. Reply 2: Tech notes for curious builders: built in Swift and SwiftUI over 5 weekends. Still early, so if Raycast import or custom ignore rules for password managers would make this fit your setup, reply below and I will look at it this week.
Mistakes to avoid
- Skipping alt text on attached screenshots. Bluesky users care deeply about accessibility, and many people will pass over or mute product posts that upload unlabeled images.
- Hiding the product link in Reply 4 like an X growth hack. Bluesky does not penalize links in the first post, so putting the URL upfront respects your readers.
- Writing a ten-post thread full of vague hype. Three tight posts with real product screenshots give followers everything they need without cluttering timelines.
- Posting from a blank profile with zero prior replies. Spend a few days joining conversations in your niche feeds before launching so people recognize your handle.
Related tools and guides
Free tool
Launch Post GeneratorDraft your launch posts for X, Show HN, Reddit, Indie Hackers and LinkedIn, with each platform's limits.Free tool
UTM Link BuilderBuild a tagged link for every place you launch, so your analytics shows what each one sent.Founder guide
How to Launch a SaaS With No Audience (2026)A practical playbook for solo founders and independent developers who don't have a big following.Founder guide
How to Track Where Your Launch Traffic Comes From (UTM, ref and Referrers)Why launch traffic shows up as “Direct”, how UTM and ref tags fix it, and why a launch board's numbers never quite match your analytics.More templates
Pritam Ghosh runs Hauntboard and maintains these templates.
Published · Updated
Ready to put your launch in front of real visitors?
A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.