I keep noticing this in software teams: a tool starts as one person’s workaround for a small task, then a month later everyone treats it like part of the stack.

Nobody really “approved” it. It just solved something annoying well enough that the old way disappeared.

For your team, what tool became that unofficial workflow tool? And what was the first job it replaced?

I’m especially curious about data collection, reporting, scraping, and automation tools. No pitch here, just trying to understand what actually sticks in real teams.

I do have coding background in the past but lost touch as I transitioned my domain in work.

• Any suggestions on the platforms to build SaaS products?
• Any tips on vibe coding itself?
• What need to consider and what can be ignored?

Context: solo project, small subscription product, using Dodo Payments for checkout. Set up a Make.com scenario that fires on a Dodo webhook and adds the customer as a subscriber in Beehiiv. Works when I test it with a manual transaction but I haven't stress tested it beyond that.

What I'm unsure about: whether webhook retries/failures are handled properly if Make.com is down for a second when Dodo fires the event, whether I need error handling on the Beehiiv side in case the API call fails silently, and generally what a "proper" version of this setup looks like versus what I've cobbled together.

Also currently have zero notification to myself when a payment comes in, just relying on checking Beehiiv manually, which feels like a bad idea long term. If anyone's added a simple "notify me" step to something like this I'd like to know how you did it.

Not trying to over-engineer a two-tool automation, just don't want it to silently fail on a real customer.

Like a lot of people here, I keep spinning up little apps with AI and then losing track of them. So I built a private vault to keep them all in one place: name, cover image, live link, the models and tools I used, a status (planned, in development, released), and a plan box for the ones I have not started yet.

Here is the how, since that is the fun part.

Stack:

• Next.js 16 (App Router) for the frontend and server actions
• Supabase for auth and Postgres, with Row Level Security so the database itself refuses to hand your projects to anyone but you
• Tailwind v4 for styling
• Deployed on Vercel

Workflow:

• I drove the whole build with an AI coding agent, but reviewed each piece instead of letting it run blind. It scaffolded the schema and pages, I checked the security rules and the data flow.
• For the look I went with claymorphism. The soft 3D clay icons and background are AI generated images. One gotcha: they came out on a green screen instead of transparent, so I had to chroma key the green out and remove the green edge halos before they looked right on a dark UI.

A few build insights that actually mattered:

• Row Level Security is what makes a Supabase app safe. The browser only ever holds a public key, and the database enforces who can read what. I ran Supabase's security advisor and fixed everything it flagged.
• Speed: I pinned the server compute to the same region as the database and deduplicated repeated auth checks per request. That took page loads from sluggish to snappy.
• I added a public roadmap where anyone can vote on the feature I build next, with the vote share shown live. Votes are anonymous and stored through a locked down function so raw data stays private. It is open here if you want to try it: https://vibevault-relcapy.vercel.app/roadmap

The live site is https://vibevault-relcapy.vercel.app if you want to poke at it. Happy to go deeper on any part: the RLS policies, the server action setup, the image cleanup, or the voting backend. What would you want to see in something like this?

so i been building little tools for my print shop using bubble and airtable. nothing crazy. just stuff to automate order tracking and customer communication. saves me a few hours a week

feels like cheating sometimes lol. i cant code at all but i can still make functional stuff

im curious what other people are building without code. any interesting projects

also if anyone is looking for a simple way to handle customer uploads, i can share what i built. not selling anything just happy to help

Most people don't know email tracking is happening to them. I didn't either until recently. Here's what's actually going on.

Marketers and sales reps need to know if their outreach is working. Did the recruiter's job offer land in your inbox? Did the sales email get read? Did the marketing campaign convert? Open rates are the metric they use to measure success. So they embed invisible tracking pixels into emails to answer: "Did this person open my message?"

Without tracking, they're flying blind. With it, they know exactly when you opened, what device you used, your approximate location based on IP. They use this data to decide: Should I follow up now? Is this person engaged? Should I keep sending to this email?

Here's how it actually works:

1. A company sends you an email with a hidden 1x1 transparent image embedded in it
2. The moment your email client loads the message, it tries to display that image by requesting it from their server
3. That request is the signal. It tells them: "This person opened the email at 3:14pm on a MacBook from New York"
4. You see nothing. They see everything.

The pixel is invisible because it's literally 1 pixel by 1 pixel, smaller than a period. It's designed not to be seen.

You have zero visibility into this. You don't know you're being tracked. You don't know when they know you opened it. You don't know they're watching your behavior.

But they do. So recruiters call you 5 minutes after you open their outreach. Sales reps follow up right when they see you engaged. Marketers adjust their strategy based on your open patterns. They're always one step ahead because they have information you don't.

It's not just invasive, it changes how you interact with email. You can't open an email casually anymore without triggering a follow-up. You lose control over when you respond and how you manage your inbox.

Gmail doesn't block it by default. Proton doesn't block it. Encryption doesn't stop it — the pixel fires before encryption even happens, in plaintext as the email loads. Disabling image loading in your email client breaks every legitimate image in your inbox, so that's not a real solution.

Most blocking methods that exist are all-or-nothing and break your email experience. There's no clean, seamless way to block only the tracking pixels while keeping your email working normally.

That's why I built Klopio, a Chrome extension that blocks tracking pixels at the network level. Now you're ahead of the game, and they're flying blind. Most importantly, you get your inbox back.

Does this stuff frustrate you too, or are most people okay with being tracked?

Building a no-code product is fast, but getting your first 100 users is often even harder. I'm making free UGC style promo videos to help you promote your app across social media without relying on generic AI slop. If you're interested, comment with what your app does in one or two sentences, who it's for, and a link to your live project. If your project is a good fit, I'll reach out via DM to get a few details and create a UGC video you can use on TikTok, Insta, YouTube. I'm just looking to support the no-code community while building my portfolio. Drop your app below 👇

Rather than wasting Sunday going through resumes, I decided to make something with it. Interviews were scheduled for Monday after the job posting was created and submissions were reviewed.

Does anyone else automate certain hiring processes? It's pretty great how it manages the tedious portions.

I’m not a traditional developer.

A few months ago, I had a strange idea for a website: a public archive where anyone could leave a message addressed to whatever might exist beyond our known reality.

No accounts, profiles, likes or replies. Each message would simply receive a number and become part of the archive.

I built it by describing what I wanted to Caffeine AI. The application now runs on the Internet Computer, and the first working version came together much faster than I expected.

Then strangers started using it, and building the site stopped being the hardest part.

More than 770 transmissions have now been added.

That forced me to deal with questions the initial build had not prepared me for.

How do you prevent spam without requiring accounts?

How do you create something intended to last while keeping the ability to fix bugs?

How do you make a 3D constellation containing hundreds of transmissions work smoothly on mobile?

How much should you explain before the mystery of the concept disappears?

I also learned that a convincing AI summary is not proof that a feature actually works.

Caffeine could tell me that navigation, performance or validation had been improved, but I still had to test the real behaviour myself.

I started keeping clearer versions, changing one thing at a time and defining the expected result before asking for another modification.

The quality of the output changed significantly when I stopped asking for vague improvements.
“Improve the archive” produced unpredictable decisions.

“The search must use AND logic, ignore capitalization, display 50 results per page and keep the newest entries first” produced something I could actually verify.

The same applied to error messages, character limits, redirects, mobile behaviour, navigation and the way transmissions are numbered.

My biggest lesson is that AI and no-code tools can remove a large part of the implementation barrier, but they do not remove the need for product judgment.

The tool can build the rule you describe.
It cannot decide whether that rule is good, whether it contradicts another rule or whether a technically successful feature damages the original idea.

The project is called Hello Outside:
https://hello-outside.com

Full disclosure: I created the site. Every transmission in the archive was written by a visitor. AI does not generate or modify the messages.

I’m curious about other people building with Caffeine, Lovable, Bubble, FlutterFlow or similar tools.

At what point did you realise that your hardest problem was no longer building the app, but understanding and controlling what the tool had built?

Show me what you are building under this post and I'll check it out and give you some immediate thoughts on it

I built a Python script using Claude Code that uses Selenium and Playwright to scrape sites for specific information, but I can't figure out how to deploy it so others can access it – is there a tool or platform I can easily use?

Ideally without making the code public (nothing sketchy, I just know it's very messy and would rather not have others judge it)

Thanks!