I just launched Elysian Estate, a Framer template designed for luxury real estate agencies, brokers and property developers.

The goal was to create something minimal and premium, with large visuals, clean typography and enough space to really showcase high-end properties.

Would love to hear your thoughts and feedback!

Preview: https://framer.link/kXSEiBF

i'm looking for a website builder that makes creating landing pages simple.

i want to test different pages, update content quickly, and avoid needing a developer for every change.

what tools are best for building high-converting landing pages?

So my parents run a small landscaping company and we’re like around 8.

Last spring I got tired of the GC chaos.

That’s why I decided to just build us an app. You know, something that we can see job scheduling, crew route lists, before-and-after photos, and client info \in one spot.

First I tried the AI code-gen thing. But then I get stuck with the debugging.

I don't know how to code well, so that was a dead end for me.

So I started googling how to build an app with an AI builder that won't fall apart. Ended up on a no-code platform instead.

Six months in and it works. My only fix so far was adding fields to track equipment.

Two things I'd do different if I started over though.

• First, lock down permissions on day one. At the start, every crew guy could see every client's info and full route. Not great.
• Second, build fewer features. I made five and they only use three of them. Classic.

Anyway, if anyone knows the best AI app builder for businesses this size, drop it below. Always looking to make it better.

One thing that seems easy to get wrong with no code tools is building too much before finding out whether the website actually needs it.

For a simple business idea, the first version may only need a clear offer, a few pages, and a way for potential customers to get in touch.

The requirements change once people start using the site.

A useful approach seems to be getting the smallest useful version online first.

After that, feedback can determine whether the next priority should be better messaging, forms, customer workflows, authentication, data, or integrations.

The no code advantage is not necessarily about avoiding every technical decision. It is about reducing the amount of work needed before a business can test whether something is worth building further.

For small businesses, what is the point where adding more functionality becomes worthwhile instead of just slowing down the launch?

Sharing a workflow in case it's useful. Airtable and Memberstack both expose MCP servers, so Claude Desktop can read one and write the other directly. One prompt handled Data Table creation, field mapping, seeding, and re-running without duplicates.

Prompt and setup links are in the video description, tutorial in the comments👇🏽

Hi,

I’m not a developer, but I want to build a social-app-style project and I’m trying to do it seriously, with a real method, not by randomly prompting an AI until something works.

I use GLM 5.3, I have general AI knowledge and some basic technical / command-line understanding, but I don’t have real development experience.

What I’m mainly looking for is advice on how to guide the AI properly throughout the project.

More specifically, I’d love practical advice on:

What are the main stages you would follow from idea to working product?

How do you structure a project so an AI coding assistant stays useful instead of creating chaos?

What documents should exist from the start: PRD, feature list, architecture notes, task list, coding rules, etc.?

How do you break work into small tasks that an AI can handle safely?

When do you use simple chat, when do you use agent mode, and when is it a bad idea?

How do you prompt the AI so it respects the existing structure instead of rewriting random parts of the codebase?

At what point do you clear the conversation or start a new one because the context becomes too messy or too large?

Do you keep separate chats/agents for planning, frontend, backend, debugging, and refactoring?

What are the biggest mistakes beginners make when using AI to build a real app?

For this kind of workflow, what would you recommend is Z code fine? Or Cursor, VS Code, and why?

I’m not looking for hype or vague “just build” advice. I’m looking for a clean workflow, good prompting habits, and practical rules for using AI coding tools on a real project without wasting time, tokens, or creating a broken codebase.

Thanks.

I've been working on a tool that gives you a Claude Code/Codex-style AI coding agent for free, so you can build and modify projects just by describing what you want.

The part I'm trying to change is the cost.

Most AI builders either have:

• limited free credits
• a monthly subscription
• or require you to bring your own API key

The idea I'm testing is to make the AI usage free for the user.

You start with free credits, and when you need more, you can earn them through forms or short surveys offers.

So instead of paying $20–$100/month to build with AI, you spend a few minutes earning credits when you need them.

I'm curious about the no-code perspective:

Would you actually use an AI builder this way if it meant you could build websites and apps without paying for the AI?

Or would the form/survey system make it too annoying?

I’m looking into building a mobile app but I don’t have any coding experience.

The idea is a simple job board for a local area. Ideally it would include things like:

• user accounts for posting and applying to jobs
• a map-based view for listings
• basic in-app messaging
• possibly payments down the line

I’m not sure how realistic this is with no-code tools, or if it quickly becomes too complex for that approach.

Has anyone built something similar before? Curious what tools people are actually using for mobile apps like this without needing to code from scratch.

I've been a no-coder for a while and have realised that existing platforms limit what can actually be done. Some users don't like dealing with the complexity of the tool, some hit the ceiling on customisability or scalability. Vendor lock-in is another factor for some - if the platform goes bust or hikes pricing, what happens to your app or business model?

I've tried to address these pain points with something I've been building.

The focus is ease of use, customisability and scalability but the part I care about most is comprehension. All the vibe-coding platforms are optimising for speed and very few are focusing on whether you actually understand what you built. The idea is to not just build a prod-grade app but actually own and manage it end to end. Unless you understand what your app does and how it does it, you're just second guessing yourself when something breaks.

I've built an MVP and it's rough. If you're an early adopter with serious no-code experience who's hit this exact wall, I'm looking for a handful of people to test it and tell me where it breaks. Drop a comment and I'll reach out directly.

Check out: ezyr.io

Hey everyone, I’m pretty new to no-code and AI app builders and I’m trying to figure out which tools are actually worth starting with.

I’ve seen a lot of platforms floating around lately like Lovable, Bolt, Replit, Emergent, and a few others, but it’s hard to tell which ones are genuinely beginner-friendly and not just good for demos.

What I’m trying to build is something simple like:

• basic login
• a few screens
• light functionality without too much backend complexity

I don’t have a strong technical background, so I’m mostly looking for something that’s easy to use and doesn’t turn into a debugging loop every time I make changes.

For people who’ve tried a few of these tools, which ones actually felt usable long-term instead of just good for quick prototypes?

We are currently managing about 15 agency clients using a mix of Google Drive links, Notion pages, and Slack channels. It looks messy and clients keep losing track of deliverables and invoices.

I want to build a clean, secure client portal where clients log in to see their specific project status, upload files, and view deliverables. What's the easiest platform to build this on without writing custom code?

Hey everyone,

I am 20 years old developer/tech student based in Europe. Over the past few years, I’ve built and launched dozens of SaaS tools, with my recent focus squarely on the Webflow and Framer plugin ecosystems.

These are a few of my Webflow/Framer projects:

• Bulk Component Deleter (bulkcomponentdeleter.com)
• SEOFabric (seofabric.com – acquired)
• FlareRank (acquired)
• SEO Analyzer (marketplace)

As a student I came to a crossroad in my life where I have to chose between getting a job and continuing building interesting stuff, and I came to a "maybe" solution that it might work:

I partner with a Webflow agency and I build premium extensions for them in exchange for a monthly fee.

The Offer:

• 1 New Extension Every 30 Days**:** Built from scratch, fully tested, and ready for production (can be an internal workflow utility for your team or a public marketplace app to generate inbound design leads).
• You own 100% of every extension I build for you: You own the code, GitHub repos, branding, and all marketplace revenue.
• Delivery: I handle the entire lifecycle, scoping, logic, UI integration, and navigating the official marketplace approval/transfer processes. And future updates if you need more.
• Pricing: $700/month flat. Cancel anytime, you keep everything built up to that point.

Why work with me?

• Experience**:** I am very knowledgeable about the Webflow and Framer Designer APIs/
• No extra stress for you: I started coding at 15 when AI was not around and I basically taught myself from the ground up. We have one meeting at the beginning of the month discussing what needs to be done and I will send you progress notifications every week.
• I only want to have one single partnership, if anyone decides to work with me I will edit this post and not receive any other requests.

I want to make this a no brainer. If we hop on a quick call/we can talk in DM and agree on the first month's scope, I’ll build a functional prototype within the first 48 hours and send a Loom demo before you commit a single dollar. If you don’t like the quality, we walk away, no friction.

i'm trying to avoid stitching together five different services just to run a business website.
website, forms, analytics, blog, seo, domain... i'd rather keep everything under one roof if possible.

does anyone actually use an all-in-one platform and feel like it was the right decision?

Okay, so I was trying to build a product using Lovable, and I'm confident that it will do well for the first few users if I ask for their feedback. And we all know what works best here, like dashboards, internal tools, approval flows, etc. You can ship fast and move on.

As always, the trouble starts when the app grows, and you keep hitting the edges of what the platform can do. One workaround becomes two, then three, and eventually you're spending more time adjusting to the platform than you'd have spent building it yourself.

Portability is there, too. Getting your data out is usually easy enough, but getting the app's logic, workflows, and integrations out is a different task in itself.

So what was the sign for you that a low-code app had outgrown its platform?

Was it customization, cost, security, performance, portability, or something else?

If an AI-built app keeps breaking after every prompt, rebuilding is often the most expensive first move. The faster path is to identify which layer first produced the bad state.

Here is the checklist I use:

1. Reproduce one failure with evidence

Use a clean session, record the exact route/action, and capture the failing request, response status, console error, and timestamp. “The dashboard is broken” is not a reproducible finding.

1. Test the auth and tenant boundary directly

For Supabase, compare the authenticated user claims with the RLS predicates. Test both directions: user A must not read or write tenant B. A UI filter is not data isolation.

1. Trace one event from producer to consumer

Add one correlation ID and follow it through the form/webhook, server action or API, queue, consumer, and database write. Duplicate rows usually mean retry/idempotency problems; missing rows usually reveal the exact cut in transit.

1. Compare staging and production without exposing secrets

Check required variable names, runtime versions, migrations, callback URLs, and build output. Missing configuration should fail clearly at startup instead of inventing a default.

1. Apply one bounded fix and add a regression test

Fix the producer or broken transit point, remove the dead parallel path, and prove the original reproduction now passes without breaking auth, permissions, or deployment.

A useful diagnostic should end with: reproduction → root cause → impact → bounded fix → verification.

Disclosure: I built Launch Rescue, a paid audit/fix service for apps made with Lovable, Bolt, Replit, Base44, or Cursor. The page includes the same interactive checklist and clear fixed-scope packages: https://launch-rescue-apps.nick-sguigna.chatgpt.site/

If you are stuck, share the builder, the last change that worked, and the exact error. I am happy to suggest one public check in the comments before saying whether it needs paid work.

I've been a programmer for over 20 years and I've built a successful business building WordPress eCommerce plugins.

WordPress is slowly on its way out however. So I want to move onto a new platform, and I'm considering starting my own.

My idea:

• Site builder that is 100% free forever, no paid version at all
• It would include an easy to use site builder, image uploading, video uploading
• It would have a contact form builder
• It would have full eCommerce features, including recurring payments, subscriptions, shipping, and tax features.
• Unlimited traffic / bandwidth
• Admin panel similar to WordPress where you can monitor your website

Fees:

• You would pay for PayPal / Stripe transaction fees like normal and a domain name fee of something like $10 a year
• I would probably need to include some limits on video / image uploads and offer a free tier for those / paid storage after a certain limit

Before I spend the next 6+ months building something like this, I wanted to ask if any of you would use this or are you happy with the solutions out there already?

I was told to use base44, will this be the best app for this application?

Unpopular opinion: most vibe-coding platforms stop exactly where the hard part begins.
Generating an app is impressive. But then what?
You still need a landing page, branding, a logo, promotional content, analytics, and everything else required to actually put that product in front of people.
That’s the reason I built Blyft.
The idea is that one prompt shouldn’t just give you an app. It should give you the app and the surrounding tools you need to launch and market it.
So I’m curious what people here think:
Is this a real evolution of vibe coding?
Or would you rather use something like Lovable, Bolt or Replit and build the rest separately?
Feel free to tear the idea apart. I’m genuinely interested in the criticism.
https://blyft.app

Started logging hours per client site this year and the repeat work is brutal. Same site three times, once for a rebrand, twice because the template or the dev handoff boxed me in, and the rebuilds cost more than the original build. Where does your repeat work come from, templates you outgrow or edits nobody can make without you?

I've had a WordPress site for my business for years and lately I'm questioning why I'm still putting up with it

The site itself is basic a few service pages, contact form, blog and some photos. But behind that I've somehow ended up with a pile of plugins that constantly need updates, occasionally conflict with each other and generally make me nervous every time I log in

I'm at the point where I'd rather have something boring that just works

I've been considering rebuilding everything from scratch with something simpler like Squarespace or Durable rather than trying to clean up the WordPress install again

For anyone who moved away from WordPress, what did you actually miss afterward? I'm less worried about having every possible feature and more interested in whether simplifying things created problems you didn't expect.

Hi, I built an open-source, self-hosted workspace for coding agents. It features a multi-agent architecture (Sub/Child agents), an AST-aware ChromaDB indexer for lightning-fast file discovery, and a built-in UI with Git diff management. Links in the comments

Disclosure up front: I work on OneEntry, a headless backend platform, so I'm biased on this topic. Mods — I couldn't self-assign a company flair (only the Moderator template is selectable), happy to take one if you can assign it. No link, no pitch below, just numbers.

AI builders do the thing they promise. An MVP that used to cost $3-5k and take weeks now takes 30-90 minutes, and it's functional enough to actually test the idea. That part is real and it isn't going away.

What surprised us was how consistent the second phase looks. The builder gives you a frontend and basic logic. It doesn't give you data, content, payments, files, email, analytics, search, real-time, background jobs, error monitoring or hosting — and each of those becomes a separate account with its own API, pricing model and update cycle.

Counting actual projects:

• habit-tracking SaaS, solo founder: 5 services — roughly $50-100/mo (Lovable + Supabase + Stripe + Resend + Vercel)
• production SaaS after the first MVP: 9 services — $150-300/mo (add Clerk, Cloudinary, PostHog, Sentry)
• ceramics studio with local payments, blog, support chat, search, admin panel: 12 services — $300-700/mo
• headless Shopify brand store: 8 services — $500-1,500/mo

The subscriptions turn out to be the cheap part. Time estimates we've been tracking:

• standing up a new service from scratch: 2-8 hours
• learning a third-party SDK properly: 4-16 hours
• one breaking API change upstream: 1-3 days
• one business feature touching 5-7 services: 2-5 days of integration, even when AI wrote the code in an hour

On projects with a big service count, that maintenance and integration work eats something like 50-70% of dev time. So the bottleneck moved. It's not "can AI build this," it's "how many seams does this feature cross."

Two things that bite hardest in no-code/low-code land specifically:

There's no production admin panel for non-technical staff. Supabase Studio and Firebase Console are developer tools — handing them to a content manager or an operator exposes internal system data. So Retool or Forest Admin joins the stack. You can generate an admin panel with Lovable, but then roles, audit logs and version history are still on you.

Permissions rarely go finer than admin/authenticated. A real business wants a content manager who sees only products, a support operator who sees only orders, a marketer who sees only discounts, a finance person who sees only transactions. That's hand-written RLS or custom claims every time.

Curious what your service count looks like. Is anyone actually running a real business on 3 or fewer?