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?

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?

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?

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!

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?

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.

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.

Every time I need a new feature page or landing page I end up spending more time trying to match the existing design than actually building the page so it always feels like I'm recreating the same website instead of extending it.

I didn't expect consistency to become one of the biggest time sinks as projects grew but it's become one of those tasks I always put off because it never takes as little time as I think it will.

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

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

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 👇

If you built your app with an AI tool and you're basically the only one who's ever used it, there's a good chance you can't see the one problem that actually matters. It doesn't show up when you're logged in as yourself. That's the whole trap.

I clean this stuff up for a living, so grain of salt on the sample. A while back I looked at 66 live AI-built apps, just the parts a normal browser already downloads, nothing sketchy, no logging into anyone's account. The same few problems kept turning up across completely different tools and founders.

The big three:

Database left open. A setting called row level security is off, so the data your app loads can be read, sometimes written, by anyone who knows how to ask, not just the user it belongs to.

A secret key shipped to the browser. There's a public key that's fine to expose and a secret admin key that absolutely is not. AI tools sometimes drop the admin one into the code your browser downloads, which hands a stranger full control.

Other service keys sitting in that same code. Stripe, OpenAI, email, whatever got wired in.

If you're on Supabase, a rough 15-minute check:

Open Table Editor and make sure row level security is ON for every table with real user data. On isn't automatically safe, but off is definitely not.

Open your live app in an incognito window, and in another window sign in as a different test user, then try to load the first user's data. If it loads, your rules are too loose.

In browser dev tools, under Sources, search the code for: servicerole, sk_live, sk-, api_key. Seeing your public anon key or a Stripe key starting with pk is normal. Seeing servicerole or anything starting with sk is the fire alarm.

None of this means the app is bad. The demo worked, it shipped, the first customer paid. The hole stayed invisible because you were always looking as the owner, never as a stranger.

spent the last few months watching how people actually find no-code tools and it broke my brain a little. the buyers i talk to don't open google first. they open ChatGPT or Perplexity and type "best tool for building a client portal without code" and then they go try whatever the model named. by the time they'd hit google they've already shortlisted.
so the real question stopped being "how do i rank on google" and became "how do i become the tool the model says out loud."
here's what actually moved the needle for me, none of it magic:
answer-first pages. one page per real question your buyer asks, and the answer sits in the first two sentences, not buried under a story about your founding journey. models lift the clean direct answer.
comparison pages you write yourself. "X vs Y vs us" with an honest table. it feels uncomfortable naming competitors but those pages get quoted constantly because the model needs a structured comparison to pull from and you may as well be the one who wrote it.
FAQ schema on those pages. boring structured data, but it makes your answers machine-readable and they show up disproportionately.
the reason i think this matters for no-code people specifically: a lot of you are building in crowded categories where you'll never outspend the incumbents on ads. but the model doesn't care about your ad budget, it cares about whether there's a clear, well-structured answer it can cite. that's a gap you can actually win.
my own site is sitting around 32,000 google impressions a month now (search console, march) and 8 to 11 keywords on page one, almost entirely from writing pages this way instead of chasing backlinks. the AI-search lift is harder to measure cleanly but the pattern of "where did you hear about us" answers shifted hard toward "ChatGPT mentioned you."
what i'm genuinely curious about from this sub: has anyone tested whether their tool gets named by ChatGPT for their main use case? what did you do that changed it?
disclosure so this is clean: i'm Iris, i make a set of free growth skills for AI coding agents, and yes this whole approach is one of the things they cover. if you want the playbooks they're here, free and MIT-0: https://gingiris.tools/skills

lm Non-technical, comparing options. Im wary about these tools, not the code it generates, rather the last mile, hosting, logins, taking payments etc.

From what I gather Emergent does the deploy/hosting/testing part too, with generated code.

Can anyone who's used it confirm how far it takes you before you're on your own

I spent the last weeks building and launching a receipt scanning app for French freelancers, entirely with AI tools. Some observations that might interest builders here.

Vision models are genuinely production ready for structured extraction. Gemini reads crumpled paper receipts and returns clean JSON with amount, VAT, date and category, with temperature at 0 it rarely hallucinates values, and when a field is unreadable it returns null instead of inventing. The real failures were never the model. They were the plumbing around it: HEIC photos from phones that the API rejects, base64 encoding breaking on large files, timezone math silently dropping receipts dated the 31st from monthly exports.

The AI coding tool experience is more mixed. It builds impressive UI fast, but it constantly drifted from my actual database schema, inventing column names that did not exist. I would estimate half my debugging time was schema mismatches between generated code and the real database. The workflow that ended up working: ask the tool to list every column its code expects, then align the database manually with SQL.

Biggest surprise overall: the model was the most reliable part of the whole stack. The hard parts were boring engineering problems that existed long before LLMs.

Happy to go deeper on any of this if useful.

There is a new approach I started using in my web agency that completely changed my results. For years, I did what most people tell web designers to do. Go on Google Maps, find businesses without websites, and contact them.

What I started doing differently was targeting businesses that already had websites.

The reason is simple. If a business already has a website, it means they understand the value of having one. You do not need to convince them why a website matters because they have already paid for one before. The market for businesses with outdated, broken, slow, or poorly designed websites is also massive, and selling becomes much easier because they are already familiar with the process.

My biggest issue was figuring out how to send mass outreach to these businesses without sounding generic. I did not want to send thousands of emails saying, “Hey, your website needs a redesign,” and just assume that every business needed one. I wanted to send emails at scale while still telling each company exactly what was wrong with their website.

A little over a year ago, I watched a YouTube video from Nick Saraev where he built a workflow that analyzed business websites and turned issues with design, SEO, layout, speed, and mobile optimization into personalized outreach emails. Each company received a professional email that made it clear someone had actually taken a look at their website.

The idea was great, but building and maintaining the workflow took a lot of time. I still had to find the leads myself, the messages were not always consistent, and the automation kept breaking.

But it worked.

I was getting more clients than ever before, at one point around 10 websites a week, while my business partner focused on building the websites as quickly as possible.

I started searching online for a tool that could do everything in one place, and a few months later I found Swokei. It did exactly what I was looking for.

It lets you find businesses with websites, add them to campaigns, analyze and score each website, and set a quality threshold so websites that do not need fixing are automatically skipped. It then turns problems with design, layout, speed, mobile optimization, and SEO into personalized outreach emails.

You can also set up follow ups, manage replies through your own inbox, and organize leads inside the CRM without moving between five different tools.

I switched over and scaled even harder.

Sometimes the fastest way to grow your agency is not building every workflow from scratch. It is finding the right tools and using your time to focus on sales, clients, and growing the business.

Kind of want to start getting into this thing,

don’t know where to start, but because I have been using ChatGPT, I feel codex would be much easier for me to get used to.

mainly looking for vibe coding projects

Hi everyone!

I’ve been working on my photography portfolio in Framer and wanted to create a more immersive way to showcase my work. I just finished this "scroll-triggered" animation that expands the grid and reveals project details as you scroll.

I’m really happy with how it turned out, so I decided to share it as a free component on the Marketplace.

Feel free to use it for your own sites or let me know what you think! I’m always looking to improve the interaction design.

Link to component: https://www.framer.com/community/marketplace/components/scroll-animation/

Curious to hear your thoughts or any feedback on the animation flow!

https://reddit.com/link/1v1wo23/video/sr6tt9fzzfeh1/player

A month ago I started asking solo founders one simple question . The question was :

what's the most frustrating part of building alone?

I expected answers like , hard to get users.

Instead, almost everyone said some version of the same thing :

"I don't know what I should be prioritizing."

Not because they were lazy. Not because they lacked ideas. But because they were jumping between building, marketing, validating, and mvp etc.. all in the same day with no real sense of what phase they were actually in. It's context switching

Building features and don't even know your users .

I realized I was doing the exact same thing. I built a tool to fix this for myself first. Every week it tells me what phase my project is in and what the single most important action is right now.

Not really a to-do list or a roadmap. Just this week, I do this.

Still figuring it out what can make us move the needle , so I would like to get some quick feedback foundersteps

and I am also curious how do you personally decide what to focus on each week?

I’m a small business for a service based company. I’m wondering if I’d be able to make my own working website with no coding or website design experience myself. I just want a clean website with a contact feature where people can put what they are wanting done and send it via text or something to me. Maybe possibly booking as well. Any recommendations for sites or software would be appreciated.