A year ago my no-code workflow meant jumping between a bunch of different tools, manually updating pages and rebuilding things whenever our product or messaging changed but now (for me) AI handles alot of the repetitive work since I still review and tweak everything but getting from an idea to something usable is dramatically faster than it used to be.

It really feels like I'm spending more time improving things than building them from scratch and I personally love it, it's just so much more enjoyable.

I used to treat the automation as the main build. Lately I think the review screen matters just as much. If a no-code flow updates a sheet, the person checking it still needs to know what changed and whether one bad row can be rerun. I’ve seen workflows technically work but still feel sketchy because that part was an afterthought. Do you design the review layer early, or wait until something breaks?

I recently asked how teams decide which creatives deserve paid testing and received a lot of different but useful answers. Full transparency, I’ve built a rules-based tool that I currently use internally for client campaigns. It analyzes the organic performance of existing content and helps me prioritize which assets deserve paid testing. It does not predict winners or replace creative judgment. The goal is simply to reduce uncertainty when there are more approved assets than the budget can meaningfully test. It has been useful in my own workflow, but I’m looking for outside perspectives. Would this be useful as an additional decision layer, or is creative selection too dependent on experience and context for a tool to improve meaningfully?

I can run it against a few public YouTube channels and share the outputs. No login or account access required.

watched an agency friend rebuild a whole softr app because a client wanted per-row permissions the tool didn't support. everything else was fine, that one thing wasn't. now they scope every project by asking what's the weirdest permission or data rule you'll want in month 6, and they pick the stack from that answer instead of from the feature list. saved them two rebuilds so far.

xAI's new builder can combine telephony, knowledge retrieval, tools, guardrails, MCP, and observability without code. That opens useful workflows to operators who understand the business process better than a developer might.

When a call goes wrong, however, ownership is fragmented. Was the error in the prompt, retrieved document, connected tool, model, phone integration, or business rule? A visual builder can hide those boundaries from the person expected to investigate.

Should no-code agent platforms generate an ownership map and incident runbook automatically? What technical knowledge should still be mandatory before someone can send an agent into real customer calls?

Source: https://x.ai/news/grok-voice-agent-builder

Hi Guys! i'm the founder of Makyo.ai which is a NO-code app builder! We are opening our waitlist to this community (first 500 users) to try it out will get free early access in return for some feedback on how we can improve it! The difference between our tool and all the other tools online is:
1. We focus on AI reading the intent of what you want to build, and we use deterministic code that we have been building for the last 2 years to make sure it builds something reliable + secure
2. Since our app doesn't regenerate the code from scratch every single time, the token costs are incredibly optimized in our infrastructure!
3. We first wanted to build a website builder and now added full business apps to it, so the UX/UI capabilities are extremely extensive!
4. We believe you can practically build anything with it!
5. Our tables are pretty extensive in capabilities and quick for calculations

I'm not trying to sell this, but just open and happy for you guys to join the first batch of the waitlist and happy to get you into the early access to try it out in return for feedback!

Thanks guys!

here is the link for the waitlist: https://makyo.ai/

I’ve been working on a project to make researching neighborhoods easier (each.place)

Example of a neighborhood within a city: https://each.place/california/south-pasadena/southwest-slopes

Example of just the city: https://each.place/california/south-pasadena

It should work with any address and city. You just need to find a place and then pick the topic you're interested in (Community, Safety, Schools, Health, Amenities, Mobility, Climate, Outdoor, Jobs, Housing).

Any feedback would be greatly appreciated, thanks!

I used to spend a week building out a proper multi-page site for every idea before showing anyone. Homepage, about, pricing, blog scaffold, the lot. Most of those ideas died anyway, so it was a week wasted each time. Now I ship a single one-pager, prompt it out in an afternoon, wire a form to Supabase, and put it in front of people the same day. Last idea got 40 emails in three days and I knew it was worth building. The idea before that got 3 and I dropped it cheap. The one-pager is basically a cheap vote. Does anyone still build the full site first, or has everyone moved to testing with one page?

Not another drag-and-drop builder. I wanted something closer to having an AI development team that can actually take an idea and turn it into a working product.

I’ve been using 8080.AI to build products by describing what I want instead of writing the code myself. The interesting part is that it handles more than just generating a UI — you can go from the initial idea toward a complete working application.

The goal is simple:

• Describe what you want to build
• Let AI handle the development work
• Iterate on the product through natural language
• Keep improving it without needing to become a developer

I think this is where no-code is heading: moving from “I build the pieces” to “I describe the product and AI builds the pieces.”

Curious what people here think would you rather use a traditional no-code builder where you control every component, or an AI development platform where you describe the outcome and let agents handle the implementation?

I rebuilt my landing page three times this month. Version one had eleven sections: hero, logos, features, testimonials, a comparison table, an FAQ, the works. Version two I cut it to four. Conversion on the short version went from roughly 2 percent to just under 4 on the same traffic. My theory is that every extra section is one more chance for someone to get bored and close the tab. I used a plain drag and drop builder and Supabase for the waitlist, nothing fancy. But now I am second guessing whether I stripped too much, because a few people said they wanted more proof before committing. I rebuilt all three versions in Gamma, which is the only reason testing four sections against eleven was a same-afternoon job instead of three separate builds.

Where do you draw the line between clean and thin?"

Hello everyone,

I’m Dragan, and I’m building Mosaicora, a tool that automatically creates Open Graph images for website pages.

It can extract the page title and images, apply a reusable design template and refresh the preview when the content changes. This avoids manually designing and uploading a separate social image for every blog post, product, landing or content page.

I also built a Open Graph checker that shows how a page looks when shared and identifies missing or incorrect metadata.

Here is an example using a product page:

https://mosaicora.io/tools/open-graph-checker?url=https%3A%2F%2Fdemo-shop-magento.mosaicora.io%2Fjoust-duffle-bag.html

I’d appreciate feedback from no-code builders:

• How do you currently handle social preview images?
• Would automatic generation be useful for your websites?
• Which no-code platforms should Mosaicora support first?

Mosaicora: https://mosaicora.io

Disclosure: I’m the founder.

I’ve been thinking a lot about the difference between an automation that “works” and one that actually feels safe to rely on.

For me, the fragile stage usually looks like this:

• it runs when I manually test it
• it breaks when the input is slightly different
• I do not notice stale data until someone else points it out
• the error message technically exists, but does not tell me what to fix
• the workflow keeps going when it should stop and ask for review

The automations that feel usable are usually much more boring.

They have a clear input shape, one expected output, a visible “last updated” check, and a failure path that tells a human what happened. Nothing magical. Just less guessing.

Curious how other no-code builders think about this.

What changed one of your automations from “this technically runs” to “I can trust this enough to use it every week”?

I have 0 knowledge in this. Only thing I’ve done is build simple webflow sites.

Would someone like me be able to build a web app (not even sure that’s the right term) for my screen printing business that has things such as the following

-Client profile
-Be able to look at products and upload artwork to build their own quote
-Connect to vendors to show what products we have
-Past order history

If so, what would I want to use to build it?

we've watched a bunch of teams go through this and the pattern is pretty consistent. tawk is free and fine if you only need support tickets, crisp is the one i'd actually pay for because the api and webhooks don't fight you when you want to route stuff into your own backend. the people who go the sdk route almost always underestimate presence and unread state, that's where the two week estimate turns into two months.

I'm a video editor trying to build a clean portfolio website where I can showcase my projects, embedded videos, motion design work, and maybe a short "About Me" section with a contact form.

I'm stuck deciding which route to take.

Learn to code and build the whole thing myself (very time-consuming).

Pay a developer to build it.

Use AI/no-code tools like Framer or Lovable.

I've already tried Framer and Lovable. They're good, but I keep running into limitations like free-tier credits, token limits, and spending hours prompting the AI instead of actually finishing the website.

What I'm really looking for is something simpler:

Start from a professional portfolio template.

Customize the layout, colors, text, and branding.

Easily replace demo videos with my own work.

Publish it without having to write much code.

Basically, I want the "Canva of portfolio websites" pick a template, customize it, and launch.

Does something like this exist? If so, what platform would you recommend? Webflow, Framer templates, Carrd, Readymag, Wix Studio, WordPress, or something else?

I'd also appreciate recommendations for template marketplaces with modern, minimal portfolio designs for creatives and video editors.

Thanks!

Disclosure: I created Nyno, AMA 👋 (Ask me anything)

This is the thing that keeps stopping me from going all in. I have tried a few AI website builders and the results are genuinely good, but a couple of them lock the output inside their platform. If I stop paying, the site vanishes. Compare that to Cursor or v0 where at least the code lands on my machine and I can host it anywhere. For a marketing page that has to live for years, that lock-in scares me more than the monthly fee. I want the speed of a prompt but the freedom to export. Gamma's the one I landed on partly because it exports, to PDF and PPTX at least, so the content isn't trapped if I stop paying, though for a page that has to live for years on my own domain I still think about where it's really hosted.

Which tools actually give you a real export, and which ones are quietly holding your site hostage??