Progress by Uriel Bitton
Working on an exciting new feature for Buildside!
A 3D globe that will let founders discover each other around the world. Will release a beta version tomorrow. Follow Buildside (on Buildside) for more updates !
Public archive
Original, substantive public posts from SaaS founders. Personalized feeds and private activity are never included.
Progress by Uriel Bitton
A 3D globe that will let founders discover each other around the world. Will release a beta version tomorrow. Follow Buildside (on Buildside) for more updates !
Launch by Uriel Bitton
🚀 Welcome to our early founders: @Lee Harding @Moshe Siegel @Alexander Rabin @Hammond Burke @James Hansen @Matthias We're adding a lot of new features to help you grow your products, stay tuned ! Looking forward to seeing you grow and build in public here.
Progress by Moshe Siegel
We have the same vision. Students lead the learning. Students should be creative. Schoolwork should revolve around collaboration as that's what real life revolves around. The principal thought her teachers could find plenty of use cases for chaverola.com and she said she'd show it to her teachers.
Lesson by Lee Harding
I've been refining and expanding the "story" of UDP Gateway for months now. Distilling it, finding where it's still diluted, and at the same time deepening the substance. It's never done, and honestly not always better from day to day, but overall feels right in conversations these days. It's not about putting aside what the platform can do, just leading with speaking to the pains people are feeling right now.
Experiment by Uriel Bitton
I built Apptruth because my users were always finding issues with my apps before i did, and that was obviously a big problem. Apptruth doesn't scan for security issues - there's already tons of apps that do this. It scans for logical issues like: - a public post can be seen by a user if they do this... - users can be charge twice if this happens... - actual real flows and features that shouldn't be possible and can cause serious damage. So far i've tested it in beta with a few users and its counted 35 issues in total across all users. I asked each user to confirm if these issues were real (they asked their claude/codex that has all the context) and they all confirmed each of the 35 found issues. This is huge for 2 reasons: - Apptruth lets you find issues your AI agent didn't find - Apptruth acts as a vibe code app launch checklist Apptruth lets vibe coders ship something real. It gives you the confidence to ship working and more reliable apps. It lets you ship apps worry-free. Apptruth is the tool I wish i had before i shipped tons of apps in the past.
Progress by Uriel Bitton
I've fully build out the feed. You can create posts with different styles/flair: 🚀 launches 🎓 lessons 🥇 milestones ❓ questions 🧳 opportunities 🧪 experiments It creates a dynamic place where founders can truly learn from each other, understand what works, learn from failures, lessons and grow faster 🚀 Join us now !
Progress by Uriel Bitton
founder network. e.g. you can: - ask a question and get answers - ask founders for feedback on your app - announce a product launch - share a lesson you learned - announce you hit a milestone (MRR, visitors, etc) The feed isn't just a place where you share posts and doom-scroll, it's a source of knowledge base you can learn invaluable things from successful founders.
Progress by Uriel Bitton
Message is much stronger. And you can quickly add a public repo to try the scan right away! Thoughts?
Lesson by Uriel Bitton
It’s an app that lets people ship real startups. Vibe coding gives you the power to build. But generating an app and confidently shipping it are two very different things. Apptruth succeeded in closing that gap. You describe what the app should do. It analyzes what was actually built, finds mismatches, incomplete flows and launch risks, then shows you what to fix.
Progress by Uriel Bitton
create Github PRs. If you use a npm library on github and it has any type of issue, scan the repo on Apptruth. Apptruth will find the issue and explain exactly: - why it happened - how it happened - where it happened It will then automatically give you the AI prompt to fix it. You can then clone the repo and use the prompt to fix it immediately or submit a PR with the suggested fix.