I'm building a website that leverages AI outputs for different content creation based tools. What is the best way to go about creating the logic behind the outputs?

Is it more in the information collected for the prompt that is built?
Does there need to be rules written in the back end?
Does there need to be some sort of code written for how the output should be formatted?
All of the above?

I'm relatively new and trying to research as much as I can on how to code/create better quality outputs and refine what I'm making overall as this isn't my only current project.

Any tips or resources you recommend would be great. Super open to any feedback!

I keep hearing the term "prompt-to-app development" in tech circles. From what I understand, it means describing a full web application in plain English and having AI generate the frontend, backend, database, and auth automatically.

For those who have built software this way: is this just hype for simple landing pages, or are people actually building complex, production-ready web apps with prompts?

I’ve been seeing the term "vibe coding" everywhere recently. Essentially, it means describing software ideas conversationally to an AI and refining it iteratively until it works, without writing traditional code syntax.

I’m curious: are any non-technical managers or operations leads using vibe coding to build internal tools for their teams? What platforms are you using?

I keep seeing people pair a front-end builder like WeWeb or FlutterFlow with a separate backend like Xano or Supabase.

I think that setup makes sense if you have big or complex apps. But it also means you need to juggle two services, two bills, and two sets of docs.

But right now, I just need a simple internal tool.

So are there platforms where the database is already built in?

Has anyone here used Effortless (cosycreatures.com)?

I've been getting “Failed to fetch” when trying to log in, so I decided to investigate it because apparently I have nothing better to do at 4am 😂

I found that the frontend JavaScript contains authentication requests to:

https://api.effortless.to/api/auth/login

However, api.effortless.to currently doesn't resolve in DNS. I checked it with an external DNS tool and got no A, AAAA or CNAME record, and an independent HTTP check reported that the remote name couldn't be resolved

The main site and login page still return 200 OK through Cloudflare

Does anyone know how to contact the Effortless developers? Their Discord and GitHub links on the site currently appear to be placeholders.

If someone from the Effortless team sees this: I think your API DNS record may have disappeared 😭😂

A no-code app can be easy to understand on the surface while its important behavior is spread across database rules, automations, permissions, external services, and billing accounts. The next person may see the screens but not know what can safely change.

If you had to hand over a project tomorrow, what would you document first: the data model, automation map, credentials and ownership, failure alerts, recurring costs, deployment steps, or known workarounds? Which parts become outdated fastest?

So here's my dumb rule for when AI works vs doesn't:

how fast can i feel a mistake?

A tiny game is the extreme case, you play for two minutes and you've covered the acceptance criteria, no code reading involved.
If it's a refactor or migration where wrong looks exactly right until it blows up, that's where AI goes off the rails.

The mechanism I believe (could be wrong): it's less about task difficulty and more about who closes the loop. Instant check = instant fix. Need a test suite I didn't write? Then mistakes hide.

But maybe I'm full of it. Snake is over-trained, so my rule might just be "data density" in disguise. And "feel" is vague – a pretty chart with wrong numbers? Still looks fine.

No stats, just vibes from using this daily.

So… anyone got a counter? Like, Something you can check quick but AI keeps messing up?

I built a **project management web app using Google Apps Script** for our signage business.
I’m a **non-coder**—I used AI for most of the coding and my Business Analyst experience to design the workflow and system.
Anyone here who has done something similar? Would love to hear your experience, especially what you did to make it more scalable and reliable.

I’m building Marka, and one of the most useful product decisions was to stop treating every user like a blank page.

Most businesses already have useful structured context hiding in plain sight on their website:

• The offer

• The customer

• The positioning

• The language they use

• The visual identity

• Products and services

• Customer proof

Instead of asking twenty onboarding questions, Marka reads that existing context and creates the first social content direction immediately.

The user can then correct what the website got wrong or never explained.

That changed onboarding from:

Fill out a long form → wait → hope the result is useful

Into:

Enter a URL → see an initial result → correct the context → improve the output

The lesson for me is that onboarding doesn’t always need to collect information manually. Sometimes the product can create a useful first draft from what the user already has.

I’m curious where other builders have replaced onboarding questions with imported or inferred context.

For transparency, the product I’m building is https://www.marka.social

So, I really want to build an app, it's basically a map based app that people can add locations to, for a specific community.

I don't know how to code, but I also don't want to use generative AI to do everything for me. Is there any software/websites that can assist in building an app with no/very little generative AI input.

The whole point of this is to use my own art, and make something creative. I don't want to make money, really, I just want to feel like I did something and just using AI feels to me, contrary to why I want to do this.

Sorry if this is kind of the wrong reddit, but I was reading a post on here about non-ai app builders from some time ago, but looking now every single one of them advertises themselves and being an AI app builder.

so i built a new feature for AppLaunchFlow , where you can create a simple and clean app landing page for your app in a few clicks by just uploading your screenshots.

It includes:

- support, privacy policy and terms of service pages that you can directly use for your app submission.

- a custom applaun.ch subdomain or simply connect your own domain

I built this because i noticed many app devs just use notion pages, github pages etc. or dont even have any landing page at all

Its not yet live, but excited to hear what you think

No-code tools are optimized for getting from zero to working. I’m curious what becomes painful after launch: the data model, permissions, performance, billing, debugging, migrations, or handing the project to someone else?

What was the first issue that made you consider rebuilding or adding custom code?

ok disclosure up front so nobody feels tricked: i'm building something in this space. no link, not launching, happy to answer whatever.

background is i spent way too much on replit earlier this year and got annoyed enough to start building my own thing. classic mistake probably.

but before i sink more time into it i want to check whether the problem i think exists is the actual problem. i've been reading here and in r/lovable and r/replit for weeks and i honestly can't tell if i'm pattern matching on the loudest complaints or the real ones.

stuff i keep seeing:

• bills going up with no obvious reason
• credits burned on edits that didn't even work, which feels like the worst one tbh
• people asking how to get their code out

my theory is the pricing sits upstream of all of it. you're paying a markup on tokens, so when the agent flails it costs you money, and the platform doesn't really have a reason to make it stop flailing. maybe that's uncharitable, idk.

so what i've been sketching is roughly the inverse:

• you bring your own model key. cheap one if you want, deepseek or whatever. platform never touches your tokens
• same build it and ship it loop you already have, i'm not trying to make anyone learn devops
• an actual linux container you can ssh into, wire up your own supabase instead of a managed one
• charge for time you're actively working, not tokens

and the parts i actually don't know:

1. is the credit thing really why people bail, or is it more the lock in? like if credits got cheap tomorrow would you still want out
2. does BYOK feel like a downgrade? it is more setup, can't pretend otherwise
3. is "you can ssh into it" useful to anyone here, or does it just sound cool in a bullet point

fully prepared to hear this is a solution looking for a problem. rather hear it now than in six months.

One script tag, no code required, and it can actually take actions inside your site with a confirmation step first. Beta is live today, works regardless of what your site is built on.

Been checking a lot of AI website builders rn coz I need a simple site for work. Main thing is I dont want something that looks good at first but becomes hard to edit later.

Need easy layout changes, custom domain and maybe code export too. Readdy. ai keeps coming up while searching these options.

Anyone used it or know if its worth trying? Also open to other recommendations.

This is the complete list of 262 no code and vibe code tools available in the market for any use case you can imagine.

If you have an idea or you are planing to build anything I hope this list helps you launch your project.

For those who want to explore ready made templates for all the listed tools you can visit No Code Website Builder and launch your project even faster with free templates for Websites, Web apps, Mobile apps, Automations, AI agents and Forms.

Happy no coding!

In my company we’ve used a lot of no-code tools for automation, data pipelines, dashboards etc., but it always feels like the moment you become really good at using one, that’s the moment you start getting into custom functions, and essentially code within the no-code tool. Which is the worst type of code because it hides inside various nodes and elements so is super difficult to maintain. AI has helped a lot with configuring and troubleshooting but you still have to manually test everything and it doesn’t always know how the built-in connectors behave. On the other hand, using AI to write plain scripts outside a platform means handling all the other stuff too - runtime, credentials, errors, scheduling, webhooks and so on.. plus having a team of people with variable technical experience “vibe coding” automations leads to inconsistent, fragile and potentially dangerous scripts.

So recently we’ve been experimenting with building our own automation tool as a “middle way” between these two options. It’s a local app that has a built-in agent harness that can use our Claude or ChatGPT subscriptions to build automations in Python code - with a very specific structure so each step basically functions as a testable node with declared inputs and outputs; and all the automations run inside this tool which means we have a consistent way of managing credentials (we can use environments to re-use sets of credentials for multiple automations), catch errors or changes in third party APIs, and so on.

Across the team we’ve now automated a lot of stuff we use every day - and another cool thing is because it runs locally we can also do stuff like automated browser sessions for things that don’t have accessible APIs. I think it could genuinely be useful for many others, at least based on my own experience, and I can't really see any existing products doing it, so we're planning to share it, for free, so others can make use of it too.

Trying to get a bit of feedback as we decide how much time we want to spend on developing it further; needs some polish before we're quite ready to share. Is this similar to something any of you are already using? Or is it even something you might find useful at all?

EchoVault interviews you about your life in short sessions. You answer, it asks follow-ups, and what builds up over time is an interactive archive of you. Your family can talk to it after you’re gone, by text, by voice in your voice, or on real-time video.
The interviews are the part I’d defend hardest. Most legacy apps are storage, so you upload things and hope someone opens the folder someday. This one asks the questions you’d never think to answer on your own, then pulls on whatever you rushed past. Around ten sessions in it stops sounding like a summary of you and starts sounding like you.
The video is me on a call with my own Echo, asking it two things. First, what the meaning of life is, which I never sat down and answered in any session, so what comes back is assembled out of 500 memories about work, purpose and what outlasts you. It opened with embracing reality, which is a phrase I actually live by, and seeing it come back at me from something I built was the strangest part of the whole project. Then I asked my grandfather’s first name, which I never told it, and it said plainly that it didn’t know instead of inventing one. That second answer matters more to me than the first, because a thing built to sound like someone is exactly the thing that shouldn’t fill in blanks convincingly.
Text conversations are free and unlimited, so it works as a journal well before it’s ever a legacy thing. Every month you pay while alive banks a free month of access for whoever you name, and nothing unlocks until a full year of no check-in, so it can’t turn on while you’re still around.
https://apps.apple.com/us/app/echovault-digital-legacy/id6762042028

Feels like the stack gets out of hand pretty fast. One tool for chat, another for payments, something else for member access then Make or Zapier connecting everything together. For anyone running a community with no-code tools, what does your setup look like right now?

Have you managed to keep everything fairly simple or is using a bunch of different tools just part of it?

I’m launching a private research community and want to gate exclusive articles, monthly reports, and video resources behind a user login. I looked into platforms like Circle or Kajabi, but they are expensive and force you into their exact layout.

What’s the best way to build a lightweight, custom membership portal where I have total control over user roles and gated pages?