THE ‘I HAVE NOTHING TO POST’ LIST
30 Things to Post About Your App (Without Repeating Yourself)
8 minute read
You do not need thirty announcements. You need thirty different ways to show the same product: the problem, the decisions, the work, the people using it, and what you are learning.
Use these as prompts, not scripts. Add a screenshot, screen recording, photo, diagram, or honest opinion wherever it makes the post clearer. One useful detail from your actual experience will beat a perfectly polished generic tip.
01 /
Start with the problem
People understand a product faster when they recognise the irritation that caused it to exist.
- The annoying momentDescribe the exact moment that made you think this app should exist.
- The old workaroundShow the spreadsheet, notes app, manual process, or questionable life choice you used before building it.
- The expensive alternativeExplain what people currently pay—in money, time, or attention—to solve the same problem.
- The problem in one sentenceWrite the clearest, least clever explanation of the problem you can manage.
- Who feels it mostDescribe one very specific person and the situation in which they need your app.
- A myth about the problemChallenge a common assumption that leads people toward the wrong solution.
02 /
Show the product
A product post does not have to announce a feature. Let people see the thing doing its job.
- The ten-second demoRecord one complete task from start to finish. No cinematic trailer required.
- Before and afterPut the old process beside the new one and make the difference visible.
- One small featureShow a detail that will matter disproportionately to the right user.
- The first screenWalk through what a new user sees and why you chose that starting point.
- An unexpected useShare a way someone used the app that you did not originally design for.
- The boring bitShow the unglamorous reliability, privacy, accessibility, or performance work that makes the product better.
03 /
Open the workshop door
You are allowed to talk about the work before it becomes a triumphant launch announcement.
- Today’s decisionExplain one choice you made and the trade-off behind it.
- A feature you removedTalk about what you cut and why the app is better without it.
- A bug with a personalityShare a bug, what caused it, and what you learned while fixing it.
- The ugly first versionCompare an early screenshot with the current product.
- A tiny improvementShow the sort of detail nobody notices until it is missing.
- What you are stuck onAsk a focused question that people can answer from experience.
04 /
Use what users give you
Real questions and behaviour make better material than brainstorming in an empty document.
- A real questionAnswer something a user or potential user has asked you.
- A tiny winShare a concrete outcome, with permission and without turning it into a miracle story.
- A surprising objectionRespond honestly to a reason someone gave for not using the app.
- A support lessonExplain something you changed after watching a person get confused.
- The words users useShare a phrase that changed how you describe or design the product.
- A requested featureExplain whether you built it, rejected it, or are still thinking.
05 /
Have an opinion
The product is evidence that you believe something could work differently. Say what that belief is.
- Your unpopular preferenceExplain a product or industry convention you deliberately ignored.
- What should be simplerPoint at a process with too many steps and explain your alternative.
- A tool you admireBreak down one detail another product handles especially well.
- What you got wrongShare an assumption that did not survive contact with real users.
- Your current betState what you think will matter next and how you are testing it.
- Why you are still buildingGive the honest reason this product continues to deserve your time.