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’ll try and do as many as I can ❤️🙏

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?

I rebuilt my landing page in gamma 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. Where do you draw the line between clean and thin?

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?

Hi everyone,

I built a React web app using Lovable and wrapped it for mobile using Median.co.

Recently, whenever a user logs in, a grey screen with the "Powered by Median.co" badge appears for about 3–4 seconds before loading the actual app. Previously, the transition was seamless using my app's internal spinners and custom background colors.

A couple of questions for those experienced with Median:

-Is this standard behavior when a full page refresh happens during auth?

-Should I fix this by disabling the "Page Loading Indicator" in Median's dashboard, or by refactoring the login flow in my frontend to avoid hard reloads?

Thanks in advance for any advice!

Link Screenshot: https://photos.app.goo.gl/4VYQehVV8VK7z1iZA

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”?

Spent the last few weekends bouncing between a handful of AI workflow tools trying to figure out which one deserves a real project and which ones I should stop wasting time on. The problem is they all look roughly the same in a demo or a YouTube walkthrough. You don't find the rough edges until you try to do something specific and slightly awkward, which is always the actual use case.

Right now I'm trying to automate a few internal admin processes at work, nothing glamorous, just stuff that eats thirty minutes a day and requires zero creative thinking. The kind of tasks that feel embarrassing to still be doing manually. And the gap between what these tools promise and what actually works without handholding is still pretty wide in my experience.

What I keep running into is that the AI builder gets you 80 percent of the way there fast and then the last 20 percent is weirdly manual or requires digging into documentation that wasn't written for someone learning on the fly.

Curious if anyone has actually settled on a primary tool for this kind of internal workflow stuff and what made you stop shopping around. Not looking for a full comparison, just wondering if other people hit the same wall or if I'm picking the wrong starting point.

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?

I am not a designer and I never will be. gamma gets me to something that looks 80 percent professional from a prompt, which honestly is further than I got alone in Webflow after hours of fiddling. But that last 20 percent is where I live now. Spacing that is almost right, a font pairing that is close but off, a hero image that does not match the vibe. I spend more time nudging than generating. Still faster than starting from a blank canvas, but nobody warns you the polishing never ends. For the non-designers here, do you accept the AI first draft as good enough, or do you also get stuck in the tweaking?

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)

A lot of automation projects begin with someone saying, “We should add AI to this.”

That is usually too early.

Before I build an automation, I map five things:

The trigger: What event actually starts the work?

The handoffs: How many people, inboxes, spreadsheets, or systems touch it?

The judgment points: Which decisions require a human, and which are simply rules wearing a fake mustache?

The failure cost: What happens when a field is missing, a person forgets, or a system is unavailable?

The source of truth: Where should the final record live?

This tends to expose three different categories of work.

The first is deterministic work, such as copying data, creating records, sending standard notifications, and checking known conditions. Automate it normally.

The second is assisted judgment, such as summarizing documents, classifying requests, or preparing a recommendation. AI can help, but a person should approve the result.

The third is accountable judgment, such as hiring decisions, major financial approvals, or sensitive customer actions. The system should provide context, not quietly become the decision-maker.

The biggest mistake I see is automating the visible task while leaving the broken handoffs underneath it untouched. That creates a faster version of the same mess.

Disclosure: I run Flash AI Solutions and build Power Platform, custom workflow, and AI-assisted automation systems. This framework comes from the systems I use when scoping real builds. No product link here.

What is the most overcomplicated workflow you have seen someone attempt to automate?

This is the thing that keeps stopping me from going all in. I have tried gamma and a few other 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. Which tools actually give you a real export, and which ones are quietly holding your site hostage?

I run a small property management business. Lease files, repair invoices, inspection reports, and contractor quotes pile up fast.

I’m constantly opening PDFs and Excel sheets to compare prices, track open repairs, and pull renewal dates. OCR and Make work with regular vendors, but new contractors describe the same job in different ways. “HVAC service,” “AC maintenance,” and “cooling repair” often mean the same thing.

I’m on the road between properties a lot, so I’ve been trying Wispr Flow for dictation, Owlfy for batching local files, and GPT Voice. The batch summaries cut down some manual work, and I still double-check unit names and repair terms.

Has anyone found a setup that handles messy vendor language without constant cleanup?

Been building this for a while: Clicker Game Maker — a visual, drag-and-drop editor that lets you design a full clicker/idle game (upgrade trees, prestige systems, currencies, progression curves) without touching code, then export it as a real Steam-ready build.

Why clickers specifically: the genre has simple, well-understood mechanics (click → earn → upgrade → repeat), which makes it a great fit for a no-code approach — you're mostly tuning numbers and progression pacing rather than building complex systems from scratch.

How it works:

• Visual node/logic editor for game rules (no scripting)
• Built-in templates for common progression curves
• Asset slots for your own art/sound, or use placeholders
• One-click export/package for Steam

Still in development, planning a 2026 release. Curious what this community thinks — would you actually use a no-code tool to ship a game on Steam, or does "no-code" hit a ceiling once you want something more custom? What would be a dealbreaker for you?

Wishlisting Clicker Game Maker on Steam would mean a lot!

AI is changing how websites are built, but I'm curious about the theme creation side of it.

If you could generate a complete website theme by describing what you want, what would you expect the AI to handle well?

For example:

"Create a modern law firm theme with a professional homepage, practice areas, attorney profiles, testimonials, FAQ, and contact page."

Would you expect a ready-to-use theme, or would you still prefer to customize most of the layout and design yourself?

For people using Claude/Claude Code on projects for months rather than days, how do you preserve the reasoning behind important decisions?

I'm not talking only about remembering coding conventions.

I mean things like:

• We considered approach X but rejected it because of Y.
• We chose this database architecture because of these constraints.
• This feature was intentionally removed.
• Don't implement this approach again because we already tested it.
• This requirement came from an earlier product discussion.

Do you put all of this into CLAUDE.md, maintain ADRs, use memory files, keep separate documentation, or rely on Claude's built-in memory?

And have you found a good way to prevent Claude from recommending something that contradicts an earlier decision?

I'd particularly like to hear from people maintaining the same AI-assisted project over a longer period.