You don't need a finished product
People relate to progress more than polish. “Week 3 of our clinic queue app: the queue screen finally updates live” is a complete post. You're sharing what changed, not claiming it's done.
Show one thing: a short screen recording of the main flow, or one clear screenshot with sample data. Hide real names, phone numbers, and client details.
Use a four-line caption
Line 1: what it is and who it's for. Line 2: the one thing you're proud of this week. Line 3: what was hard or what you learned. Line 4: a question for readers.
Example: “Clinic queue app for our barangay health center. Live na yung queue updates. Hirap ng real-time sa free tier, natutunan ko yung polling vs websockets. Ano mas okay sa inyo?” Write in the language you think in. English or Taglish, both work.
Handling comments
Thank people for specific feedback and answer real questions. You don't owe a reply to rude comments. If someone spots a bug, that's free QA: note it and say when you'll look at it.
Post again next week. Showing up matters more than a perfect first post, and each one gets easier.