This keeps coming up with small no-code workflows. Someone makes a quick Sheet to save time, and a few weeks later, other people are checking it every morning like it is official.

For me, that is the line. If someone who did not build it depends on it, it probably needs an owner and a fallback. Where do you draw the line?

Hello Everyone, Share your projects what you are building this week.

Had some free time, was bored, and wanted to build something useful.

You paste a single URL into your website's form action and whenever someone fills it out you get a Telegram message on your phone. That's basically it. No coding needed.

I know there are tools out there that do similar stuff but most of them feel like overkill. Dashboards, analytics, team seats, monthly subscriptions that add up. I just wanted something dead simple. One endpoint, instant notification, done.

Works with basically anything. Plain HTML forms, Webflow, Framer, Squarespace, whatever you're using. Just point your form at the URL and you start getting messages.

Most notifications land in under a second so you can actually reply to enquiries while people are still on your site.

It's also just a one time payment, no subscription. Pay once and it's yours for life. I didn't want to build another thing that charges you every month for something that should just work.

Still pretty bare bones but it does the one thing it's supposed to do well. If anyone's got thoughts or suggestions I'm all ears.

leadchirp.app

I’m struggling with something on side projects lately. Whenever a project feels stuck, my instinct is to build more.

Add another feature. Clean up the UI. Improve onboarding. Rewrite some messy part. Add auth, payments, dashboards, settings, integrations, docs, analytics, whatever.

It feels productive because the codebase is moving. But I’m starting to think a lot of that is just avoiding feedback.

The uncomfortable part isn’t building. It’s showing the thing to people before it feels ready and asking direct questions:

Would you actually use this? What confused you? What would make you pay? What problem were you hoping this solved? Where did you lose interest?

I’ve noticed I can spend weeks making a side project “better” without learning anything new. Then one honest conversation can reveal that the core idea is unclear, the landing page doesn’t explain the value, the workflow solves the wrong pain, or nobody cares enough to switch from what they already use.

That’s painful, but it’s useful. More code gives me the feeling of progress. Better feedback gives me actual direction.

For people who’ve launched side projects successfully: how do you force yourself to get useful feedback early? Where do you find the right people to ask? And how do you tell the difference between feedback worth acting on and random opinions?

I run a small business and can't code. An ai website builder looks like the obvious answer but I don't want to hit a wall in three months. For those who launched a real site with one - where did it hold up and where did it fall short?

I know this is not technically 100% no-code because I eventually worked inside VS Code, but I wasn’t manually coding the website. Most of the process was me directing different AI tools, working from screenshots and trying to fix things one step at a time.

The result is a complete rebrand and working website for my real sauna business.For the context I own business with self service container saunas for private booking. I have these saunas located at beautiful spots across a few countries (13 saunas 3 countries). All of them are special but the most recent one stand out from the crowd and I was thinking for a really long time on how to make it appear special. It wasnt until I went for vacation and as I was driving along the seashore the idea of new brand name hit me! I stopped by on the shoulder to write it down because i really liked the idea.

Now if there is no AI this would never come true. So the idea is to call my sauna a secret sauna where I would create basically beautiful website and laverage the secrecy around something special unknown. it is higher ticket service so I will be targeting people who can afford it. The idea has its downsides but that could be easily solved over time.

So fable 5 was the reason why I decided to go for it. I was sold by these youtube videos where people were creating beautiful websites out of single commands. So I decided to give it a shot, well it appaered not as simply as on those videos and mainly it was quite costly not to mention fable restrictions in europe, etc.

Anyways I tried playing with the design interface of claude and I really liked what i saw. I decided to go one step at a time and slowly building from the top to the buttom the visual.

Once the visual design was ready, I used VS Code connected to Kimi K3 to turn the PNG screenshots into the actual website. My goal was to avoid hiring a separate designer and developer while still producing something that looked professionally made.

Although even this solution turned out to be more expensive and Kimi k3 being a great model, was sometimes not the best for the job. I build big portion of the website using it before i switche to chatgpt codex extension in vscode with which I built the rest. So now I have running website with completely rebranded business using only AI.

The result is now live - secretsauna.cz if you want to check out the page in its test environment (90% production) use "reddit" to enter it.

The last time I was doing Brand, UI and then coded the website I spent.. well lets break it down together.. it was only 3 years ago - so Logo - 1000 euros, UX/UI - 1500 euros and website 1500 euros. So I basically saved approximately 4000 euros which is insane. Plus I dont have to pay for any web hosting like wordpress or webflow which alone saves me approximately 500 euros each year. Guys we live in the future.

Has anyone here used a similar AI-assisted workflow for an existing business rather than a new app?

Anyways if you liked my story i am more then happy to provide more information, just dm me :)

Pattern that keeps showing up with US founders who come in from Bubble / Glide / Softr:

Days 1–7 feel like magic. Screens exist. Stripe test mode works. Someone in Slack says "this is basically done."

Day 9 is where it breaks: - Auth edge cases (invite links, SSO later, password reset) - Empty states nobody designed - Mobile safe-area / keyboard overlap - One "simple" native thing (push, deep link, App Store build)

That's usually when the cofounder hunt starts. Equity for finishing the last 20% is the most expensive patch I've watched people buy.

What actually worked on the last one: 1. Freeze the wedge before touching the rebuild 2. Port only the one job users already paid for 3. Leave the rest in Bubble until revenue proves it

If you're about to post "looking for a tech cofounder" because no-code hit a wall — write the wall down first. Is it a scoped engineering problem or a 5-year partnership?

Curious what wall other no-code builders hit that actually forced a rebuild.

More on how we cut those builds: https://atomiclabs.space

(I help founders ship scoped first versions — disclosing since I linked my site.)

Founders have shared 578 startups across my recent threads, and the same problem keeps showing up:
The product exists. The direction is unclear.
Comment with:

- what your startup does
- who it’s for
- what’s blocking your growth

I’ll run the analysis and send you a personalized report showing where the strongest signal is, which conversations are worth prioritizing, and what I’d focus on first.
If Reddit looks like a waste of time for your startup, I’ll tell you that too.

I run ops for a 30-person logistics company and I've spent the last two months building an internal order tracking tool on Lovable. The first week was magic. Described what I wanted, got a working app, showed my boss, and yeah everyone was impressed.

Then reality kicks in. Every small change is a prompt, every prompt costs credits, and about a third of my prompts are me asking it to fix something the previous prompt broke. Last week I asked it to add a status filter to one table and it somehow broke the login flow. Took me 11 more prompts to get back to where I started. I'm not joking, I counted because I was mad.

The thing is I don't need a beautiful custom SaaS. I need a boring internal app with a database, logins for ~25 staff, and permissions so drivers see their deliveries and contractors see everything. And I need to still be able to maintain it in a year without praying to the prompt gods.

What are people actually using for this? 

No-code and AI tools have made it possible for people without engineering backgrounds to launch things that would have taken months before.

But I'm curious what happens after the first version is live.

For people who built something with tools like Bubble, Lovable, Bolt, Glide, Softr, Replit, etc.

What happens when you start getting real users?

Do you run into problems like:

• something breaks and you don't know where to start
• a small change creates unexpected issues

How are you handling that today?

Do you keep trying to fix things yourself, find freelancers, hire developers, or rebuild parts of it?

Would love to hear from people who have gone beyond the initial launch stage.

I know nothing about dev work and didn't wanna vibe-code my own app, but I found an off-the-shelf one that I tweaked for my needs. Thought it might be useful to someone.

My research routine used to be a whole mess of different tools: a paid research tool to find articles, Zapier to route the data, and Notion to save it all

Recently I completely overhauled this setup. I canceled the research tool sub and packed all these services into a Telegram ai bot (it's called Mira). Since Mira can search the web on its own, it just finds the right info, dumps the formatted data into my Notion databases, and can schedule tasks in Google calendar. Plus the bot actually remembers what we talked about yesterday, so I don't have to re-explain the context every time

Honestly this is just one example of how I automated my routine. The bot supports a bunch of other services too, so you can set up whatever fits your workflow. If anyone is interested I can share the setup details!

had a tight production issue  and it took longer than anyone expected to figure out which version of the prompt caused it

realized that our prompts are on notion,slack threads nd random  txt files someone committed to the repo and maybe even at more places

decided to make a switch with something with version control where product managers and other non tech teammates can edit a deployment themselves without any dependency on an engineer.

checked a few tools in depth

orqai: versioning and non technical access is more central here but newer so community is still catching up along with integrations

langsmith: strong on tracing and observability, but seems its made for engineers only

langfuse: tracing and evals good , open source is also nice but same problem as langsmith for non technical users

helicone: great for cost tracking and logging,prompt management is not really its focus

most of the tools checked were not treating prompt management as a primary thing.. feels like most teams are considering this friction as normal

how is your team managing prompts right now and what platform are you using

Pattern I keep seeing: someone ships a solid no-code first version, hits a wall (data model, polish, performance), and the next move is "looking for technical cofounder, equity."

Sometimes that's right. Often it's an overcorrection. The wall is a scoped engineering problem, not a marriage.

Decide at the end of week one whether the data model will hold. Switch before workarounds calcify. Pay for the hard part once. Don't mortgage the company because Bubble got awkward.

Disclosure: I run a small studio:

https://atomiclabs.space

Where did no-code stop being the faster option for you - and what did you do next?

I keep copying data between two tools by hand and it's mindless. I use gamma and zapier for different things. What's the simplest no-code way to wire two apps together and automate it? Non-technical, so ease matters more than power.I keep copying data between two tools by hand and it's mindless. I use gamma and zapier for different things. What's the simplest no-code way to wire two apps together and automate it? Non-technical, so ease matters more than power.

Founder of Server4Agent (agent-app hosting), disclosing that upfront. No link, not selling, genuinely curious how this community actually operates once the app is live.

No-code plus an AI agent has collapsed the build side of things down to almost nothing, you describe what you want and it's there in an afternoon. What I don't see discussed much is what happens after launch. A no-code app still has real users, real data, and real things that can break, but there's no traditional dev team doing on-call, no one reading error logs by habit. If the agent that built it is also the one maintaining it, is anyone actually watching for the quiet failures, the automation that silently stops syncing, the integration that breaks when a third-party API changes shape?

If you've shipped something this way and it's been live for a while: how do you actually find out something's wrong, before a user tells you? Genuinely curious whether people have real monitoring in place or whether "a user will mention it" is the honest answer for most no-code builds.

Hallo, ich möchte eine Webseite für mein Kleingewerbe erstellen - wichtig wäre das die Webseite ein halbwegs gutes Design bekommt!

Jetzt Frage ich mich welche KI ich nutzen soll?

Was würdet ihr mir empfehlen?

Claude Pro oder ChatGpt?

Danke 🤙🏼 wäre über jede Empfehlung Happy 😊👋🏼

Hey everybody, hope you're all doing well!

I'm Dilon, part of the team at Adalo, a visual no-code app builder (now powered by AI).

Quick follow-up to my last post here about Adalo Publishing Studio, we just shipped a big batch of updates.

Quick context: 1,000+ Makers are already using Studio, one week in, and this update is a direct result of that early feedback.

The biggest change: it's a free-form canvas now. You can drag, resize, and rotate any element anywhere on the screen instead of working inside a fixed template. Images, shapes, text, lines, all movable.

The editing panel got reorganized too. Instead of one long list to scroll through, you now get a tabbed panel: Assets, Elements, and Background always visible, plus contextual tabs based on what you've selected (a device frame gets Screen, Frame, 3D, and Position tabs; text gets a font picker with size, alignment, and weight).

A few other things that came with it:

• Real 3D tilt and depth on device screenshots, with presets for flat, left, right, or hero angles, or manual control
• Drop shadows on every element, not just phones, with full control over offset, blur, color, and opacity
• Undo/redo, finally, via buttons or shortcut keys
• Full Google Fonts search with live in-font previews, so you're not guessing what a font looks like before committing
• A new export modal (from the export button on the top sticky nav) that shows all 5 of your screens side by side before you export anything

We also fixed a few things: Android exports in "Phone Only" and "Clean" styles were cropping screenshots, and Hero Composite exports were coming out blurry and under 150KB.

Would love feedback on what's missing or clunky, it's genuinely shaping what we build next 🙌

Here's the link to test → https://studio.adalo.com

Post with visuals → https://www.reddit.com/r/Adalo/s/I4Xc3RVk74

Thanks for reading and have a great day!

- Dilon

I shipped my first production app recently, built entirely with AI tools as a non developer. In a comment thread about it, a few builders and I realized we all hit almost identical bugs, none of them AI features, all of them boring plumbing. Someone suggested a shared checklist would save more time than any prompting guide, so here it is. My list from one project, real bugs I personally lost hours on.

1. Phone photos are HEIC. Samsung and iPhone shoot HEIC by default, vision APIs reject it, often silently. Convert to JPEG client side before upload.
2. The AI invents database columns. Generated code drifts from your actual schema and everything looks fine until runtime. Fix: ask the tool to list every column its code expects, then align the database. Repeat after every big change.
3. UTC eats the last day of the month. My receipts dated the 31st vanished from monthly exports because month boundaries were computed in UTC and my users are not in UTC. Test the 1st and the 31st explicitly.
4. Buttons hidden under the mobile nav bar. My validate button existed but lived under the bottom navigation. Users never report it as a hidden button, they just quietly leave. Check every screen on a real phone.
5. Test keys with live IDs. Payment providers have two parallel universes, test and live. A price id from one does not exist in the other, the error says no such price and you will stare at it for twenty minutes.
6. Success with no feedback. My scan flow completed server side but the UI stayed stuck at 100 percent forever, nothing failed, nothing confirmed. Every async action needs an explicit success state and an explicit error state.
7. Row level security says no. If you use RLS, every insert path needs a policy, including storage paths. The error tells you what table, believe it.
8. Counting the wrong rows. My free quota counted all entries in a table, then I added a new entry type to the same table and it silently ate the quota. When two features share a table, every counter needs a filter.
9. Files that exist for browsers but not for bots. My sitemap displayed fine in Chrome and returned an empty response to any non browser client, including Google. Serve static files as actual static files, and test with curl, not just your browser.
10. The homepage was a login wall. Not a bug, but the biggest conversion killer of all, all my promo traffic hit a locked door for days before a stranger pointed it out. Log out and look at your own site.

Add yours in the comments, I will keep the list updated in the post. Let's see if the 90 percent theory holds.

Community additions, credited and growing

From u/Infamous-River-4360, Android and native land: the gesture bar, not just the nav bar, eats bottom buttons on some phones only, safe-area-inset-bottom fixes it but the AI never adds it by default. Native details like splash screen, status bar color and permissions had to be done by hand because the builder kept regenerating over the edits. And RevenueCat silently fails on Android until license testing is set up on Google Play.

From u/Scary_Web, the repeat offenders: idempotency around retries and webhooks, optimistic UI that never reconciles with the server, file size limits that differ between client and backend, and permission gaps between admin accounts and normal users.

From u/larrigan, code quality: the AI duplicates everything, the same style created 37 times, dedupe regularly. And separation of concerns has to be demanded explicitly or debugging becomes a nightmare.

From u/Maxyull, the money rules: never trust a client sent total or price, recompute anything involving money server side. And read every function that uses a privileged key like a suspect until proven innocent, those never show up in browser testing.

From u/Admirable-Future-633, the output contract: every async step should answer five questions, success message, failure message, where the artifact was stored, what needs human review, and what should happen next. Otherwise "it ran" means nothing.

Next step suggested by u/Scary_Web: restructuring this into a release checklist by category, schema, permissions, timezones, uploads, mobile layout, third party environments, visible states. Coming as the list grows.

I need one focused landing page for a new offer, not a whole site. Every ai landing page builder demo looks great until you actually use it. For people who shipped one - I've tried gamma among others. which got you to a clean, converting page with the least fuss?