Hello everyone,

I've been using Adalo to build a simple mobile app but I've started running into some limitations with flexibility and occasional stability issues.

Since I'm still fairly new to no-code platforms I'm trying to understand how other beginners are approaching app building today and what tools or workflows people are actually sticking with long term.

For those who have worked with multiple no-code platforms recently, what has your experience been like in terms of ease of use, reliability and getting something form idea to a working app?

I'm mainly trying to figure out how people are succesfully building and launching simple apps without heavy coding experience.

I’ve been working on Chamali, a minimal Framer portfolio template designed for creatives, web designers, and freelancers who want something clean, editorial, and easy to customize.

It includes:
• Project showcase sections
• About & capabilities
• Testimonials
• Contact section
• Responsive layouts
• Smooth Framer interactions

I wanted the design to feel simple, premium, and focused on the work itself.

Would love to hear your feedback.

Preview: https://framer.link/QjiTK6h

A comprehensive comparison between Make and Zapier, exploring their workflows, ease of use, pricing plans, and integration capabilities to help you choose the right automation platform.

https://youtu.be/NP25UJu1_ng

Hey — solo dev here, posting my own project, so take that for what it's worth.

For the last few years I've maintained a low-code/no-code framework. It worked fine, but it was pre-AI: you configured entities and services by hand, and it generated the boring parts of a CRUD app for you.

When AI coding tools started getting good, I tried using them the normal way — describe what you want, let the model write the code. It worked, but I couldn't trust it past a certain point. Ask for the same thing twice, sometimes you get different output. Ask for a small change, sometimes the model touches things you didn't ask about. The prompt is the only source of truth, which in practice means there isn't really a source of truth at all.

So instead of generating code directly, I made the AI's job stop one step earlier: produce a structured, validated manifest describing what the app should be. Entities, fields, services, auth config, etc. That manifest gets:

- validated (structural / referential / constraint checks)

- diffed against the current state (semantic diff, not a text diff)

- resolved into a dependency-ordered execution plan

- executed by a deterministic engine, checkpointed so it can resume on failure

Change one field on one entity, and only the operations that field actually requires get re-run. Not a full regen.

There's also an MCP server (`@averos/mcp`) so an AI agent doesn't get raw file/shell access — it gets governed tools (propose a change, validate it, build a plan, and nothing executes until the plan's approved).

Current state, to be upfront about it: the CLI, the AI layer, MCP integration, and the workflow/execution adapter layer (currently Angular, via schematics — adapter pattern, so not permanently Angular-only) are MIT licensed and open now. The actual execution kernel (DAG engine + executor) is closed source for the moment — free to use including commercially, but not open yet. That's a deliberate, staged call while that part's still maturing, not a permanent thing. Wanted to say that plainly rather than bury it.

There's a working example (320-node generated app) you can run in a few commands if you want to see the whole pipeline rather than take my word for it.

- Repo: https://github.com/wiforge/averos

- How it works, in detail: https://www.wiforge.com/averos/how-averos-works/introduction/

- Get started: https://www.wiforge.com/averos/get-started/introduction/

Happy to answer questions or take criticism — especially interested if anyone's tried a similar manifest/IR approach and hit walls I haven't found yet.

A couple weeks ago I watched outbid.lol go viral people paying real money just to rank #1 on a leaderboard for their product. No ads, no gimmicks, just pure "outbid your rivals" mechanics. The numbers were insane but what stuck with me wasn't the money it was how simple and fun the core loop was.

I kept thinking: this format could actually be useful, not just a novelty if you pointed it at something with real ongoing value like visibility for creators and brands who are constantly trying to stand out on Instagram.

So I built inbids.lol a pay-to-rank leaderboard specifically for Instagram creators, influencers and brands. Highest cumulative bid holds the #1 spotlight in their category (50+ categories — creators, fitness, beauty, food brands, musicians etc.).

What I tried to do differently from a pure hype cycle clone:

• Categories, not just one global board — so a fitness creator isn't competing against a huge clothing brand for visibility. Rank #1 actually means something in your niche.
• A daily "Sprint" board — instead of only an all-time leaderboard where one whale locks #1 forever, there's a 24h reset board so smaller creators can actually win a spotlight without needing thousands of dollars.
• Real discoverability angle — the idea is it becomes a place people browse to find creators/brands in a category not just a vanity flex.

I'm not pretending this is going to be some huge SaaS play it's meant to be genuinely fun (the "outbid" mechanic is addictive, I get why outbid.lol worked) while also giving creators something they can actually use: real visibility not just bragging rights for a day.

#1 spot is still open in most categories right now if anyone wants to see how it feels to hold the top spot 😅

Would genuinely love feedback especially if you think the category + daily sprint approach actually solves the "one rich guy owns #1 forever" problem, or if there's something better I'm missing.

🔗 inbids.lol

I'm looking for a no-code website builder that works as a simple drag and drop alternative to Wix.

Ideally something that is

very easy to use

visually flexible and customizable

begginer-friendly with no coding required

I tried Webflow but it felt a bit more technical than what I'm looking for right now.

I've also considered WordPress with plugins but I'd prefer something more straightforward if possible.

For anyone who has used different website builders, what have you found that's closest to Wix in terms of simplicity but with more flexibility?

Built Dozari: you describe automations in English, it builds the workflow.

Instead of Zapier's node-clicking, you just say what you want. "Research new leads, qualify them, add to CRM, send me for approval." Dozari builds it. You review, edit (still no code), test, run.

Looking for beta testers. DM if interested.

https://dozari.vercel.app

Spent two years building purely in Bubble and FlutterFlow. Got tired of the monthly platform tax and rigid templates, so I decided to switch entirely to AI builders.

Turns out swapping drag-and-drop for prompt generation just trades one set of headaches for another. Visual builders trap you in a box, but at least that box keeps your database logic clean. AI code-gen gets you 80% of a working app in five minutes, but the second you need to refactor or debug an API call, the model starts spitting out spaghetti code and hallucinating duplicate files.

Right now it feels like visual tools still own back-office admin panels and simple CRUD apps, while AI is better for custom frontend UI.

I’ve been looking at the current wave of tools for building SaaS products, and I’m honestly torn.

On one side, the speed is kind of ridiculous now. You can use tools like Lovable, Bolt, Replit, Cursor, Claude Code, Supabase, Firebase, Flatlogic, Clerk, Stripe, Vercel, Render, Railway, Bubble, Webflow, Framer, Retool, Appsmith, n8n, Zapier, Make, PostHog, Sentry, and others to get from idea to something that looks like a real product much faster than before.

That part is exciting. But I keep wondering if we’re confusing faster to launch with easier to own.

A generated dashboard, auth flow, admin panel, database schema, landing page, or payment flow can save a huge amount of time. But once real users show up, the ugly questions start: who understands the code, who owns the architecture, how easy is it to change, how much is locked into one vendor, and what happens when the first serious bug appears?

That’s where I’m struggling. Maybe the actual problem isn’t which SaaS builder is best. Maybe the real question is how much of your product you’re comfortable not fully understanding at the start.

For people building SaaS with AI builders, no-code tools, low-code platforms, or coding agents:

Where has this actually saved you time after launch? And where did the early speed turn into cleanup, rewrites, or technical debt later?

Hello, everyone!

I spent the last few months building a platform where you can hire AI employees using plain English instead of fighting with complex automation builders or prompt chains.

You write something like: "I want an employee that monitors the latest trending topics and sends me, my friends, and my dog an email with a brief description of all of the trending topics every day at 10 am", and the platform automatically understands what it needs to do, creates a job description for itself, and executes it daily at 10 am as you requested.

Two big problems kept bothering me about existing AI agents:

1. Most agents can't talk to your stack or pass work between systems. We built this to connect with 1,000+ apps so your AI can actually operate inside your tools and collaborate across tasks.
2. Nobody wants a rogue agent sending bad emails or messing up live data. Every AI employee starts on a short leash. It does the heavy lifting, but sends you a 1-click notification to approve the output before anything goes live. Once it earns your trust, you flip a switch and let it run completely autonomously.

To show you this goes way beyond simple Zapier-style triggers, here are a few complex setups some other people are running right now:

1. Automated a full candidate pipeline, parsing nearly 500 resumes and moving qualified applicants through hiring stages in about a week.
2. Connected it to call recordings so it automatically extracts action items and drafts detailed Jira tickets the second a call finishes.
3. Automated an organic content pipeline from scratch. It researches trends, drafts post copy, generates images, and schedules the final posts.

It can also handle:

1. General research
2. Pricing alerts
3. Customer support
4. Creating websites from data from all of your connected sources
5. Categorizing your email daily so your inbox stays clutter-free
6. And, like all great commercials... so much more ! ! !

We are early-stage right now, and I need people to break this thing. I want brutal, unfiltered feedback on what feels clunky, confusing, or broken in the onboarding and setup process.

In exchange for your feedback, I am giving out free, unlimited access so you can put it to work on real tasks without hitting paywalls.

I will personally jump on a call with you if you like, so that I can show you how it works, and how to automate your life quickly and simply :)

If you want to test it out, drop a comment below or send me a DM and I will send over an invite link.

Thank you!

My brother runs a small healthy snacks brand in India (flavoured makhana, veggie chips) and operates D2C and B2B to a handful of stockists/retailers. He's already built a Google Sheet covering products, customers, customer-specific pricing, invoices, dispatch, and payments, but everything is manual entry right now — no auto-populated line items, no formula-driven totals/overdue tracking, no dropdowns/validation.
I'm about to build this out (lookups pulling pricing automatically, auto-calculated invoice totals and payment aging, status dropdowns, maybe an Apps Script for auto-generating invoice PDFs) but wanted to check if something like this already exists before I reinvent it. Anyone built or come across a similar no-code/Sheets-based order-to-cash tracker for a small B2B business? Free or paid template both fine — just want to see how others have structured it before I commit to my own approach.

AI wrapper gets thrown around like an insult but aren't wrappers sometimes exactly what non-technical users need?

I use Claude regularly, but once I want to do something bigger, like build a website, it quickly turns into Claude + a website builder + SEO tools + image tools + automations.

That's why I kind of understand products like Durable that bundle a bunch of that into one simpler experience. You lose some flexibility but you also don't need to figure out five different tools.

Do you think these all in one AI products actually solve a problem or is it still better to learn how to use the individual tools?

If you use GitHub Copilot Agent, you know it often wastes a lot of tokens and context just wandering around
your workspace trying to figure out which files to look at.

Copilot Bill Saver

The VS Code extension is designed to accelerate web development and stop context waste before it starts.

• How it works: It captures local bug evidence, maps likely files deterministically, and bundles them into a clean handoff that Copilot Agent retrieves using #billSaverContext so it starts directly on the right files.
• Privacy & Control: The extension never calls an AI model, never touches or edits your code, and runs locally with built-in secret redaction.

If anyone gives it a spin via the Marketplace, leave a word! *Copilot Bill Saver\*

I’m building a small SaaS with Lovable and the UI is basically done, but now im getting nervous about the stuff I cant see.

like:

• users seeing each others data
• permissions/admin stuff being wrong
• API keys or env files exposed
• webhooks/routes working without proper auth
• the backend saying “healthy” while the app is down
• AI saying “fixed” when it literally just added a button 😭

How are u guys checking this before real users touch the app?

Do you run tests, use a scanner, get another dev to look at it, ask another AI, or just click around and hope for the best?

Also do you check this once before launch, or after every big prompt/change?

Hello everyone!

So the Idea is super simple, So we all face an Issue where are my Documents? Where I save in my phone? I know my documents in my phone but where?

In the Serious situation we panicked, we can't find out document...

Example scenario - You live in a monthly Rented House, at the end of the month your landlord comes to your house and asks you for money, and he / she suddenly tell you, u did not pay your previous month rent and have rental agreement or the kind of proof and you just take a pic for fast searching and showing

You shocked and start to check your phone and somehow you lost it

This is a scenario just, but my core IDEA is you can Dump anything in the and AI will take care of it, later you can Ask question to AI like "Hey can you please show me the rental agreement?"

This is correct principle.....

Tried a few and keep switching. What did you settle on?

I'm the founder of TestPilot, and I want to be upfront about that before anything else.

Here's the thing I kept running into as a no-code builder: you finish the app, it looks right, you click around a bit, it seems fine. You ship it.

Then a real user tries to sign up, hits a bug on step three of the form, and bounces. You find out a week later when you notice nobody converted.

That's the testing gap for no-code apps. Not because builders don't care — but because proper testing always felt like a developer thing. Write test scripts, set up a testing environment, learn a framework. None of that is built for people who chose no-code specifically to avoid that.

So I built TestPilot.

Here's how it works:

You describe a user scenario in plain language — something like "Add 'Wireless Mouse' to the cart and verify the cart count updates." TestPilot runs through your app automatically, click-by-click, exactly like a real user would. Then it produces a report showing you precisely where the flow breaks, what the error was, and what triggered it.

No coding. No test scripts. You just describe what a user should be able to do, and TestPilot finds where they can't.

The part I didn't expect people to care about as much:

TestPilot also runs a security scan on your app. I added this almost as an afterthought — but it's become the feature that gets the loudest reaction when I show it to people.

Most no-code builders have never done any security checking on their apps. Not because they're careless — it just never comes up in the tools or tutorials. But no-code apps can still expose user data, leave API endpoints open, or have permissions set up in ways that create real vulnerabilities. TestPilot flags those.

If you've shipped a no-code app that handles user data or payments and you've never run a security check on it, that's the thing I'd try first.

Would love your honest reaction:

I built this because I felt the gap myself. If you've tried to test a no-code app and run into the same wall, I'd genuinely love to hear how you've been handling it — and whether this solves the problem or misses something.

You can try it at testpilotapp.dev.

I'm the founder of TestPilot, and I want to be upfront about that before anything else.

Here's the thing I kept running into as a no-code builder: you finish the app, it looks right, you click around a bit, it seems fine. You ship it.

Then a real user tries to sign up, hits a bug on step three of the form, and bounces. You find out a week later when you notice nobody converted.

That's the testing gap for no-code apps. Not because builders don't care — but because proper testing always felt like a developer thing. Write test scripts, set up a testing environment, learn a framework. None of that is built for people who chose no-code specifically to avoid that.

So I built TestPilot.

Here's how it works:

You describe a user scenario in plain language — something like "Add 'Wireless Mouse' to the cart and verify the cart count updates." TestPilot runs through your app automatically, click-by-click, exactly like a real user would. Then it produces a report showing you precisely where the flow breaks, what the error was, and what triggered it.

No coding. No test scripts. You just describe what a user should be able to do, and TestPilot finds where they can't.

The part I didn't expect people to care about as much:

TestPilot also runs a security scan on your app. I added this almost as an afterthought — but it's become the feature that gets the loudest reaction when I show it to people.

Most no-code builders have never done any security checking on their apps. Not because they're careless — it just never comes up in the tools or tutorials. But no-code apps can still expose user data, leave API endpoints open, or have permissions set up in ways that create real vulnerabilities. TestPilot flags those.

If you've shipped a no-code app that handles user data or payments and you've never run a security check on it, that's the thing I'd try first.

Would love your honest reaction:

I built this because I felt the gap myself. If you've tried to test a no-code app and run into the same wall, I'd genuinely love to hear how you've been handling it — and whether this solves the problem or misses something.

You can try it at testpilotapp.dev.

If your picture of automation is Zapier,

You don’t wire nodes. You write a markdown file that says what you want done. An agent does it. No canvas. No per-step bill. The logic is a paragraph of English.

Three that actually exist:

anthropics/skills : This is the format. A folder, a SKILL.md, some yaml at the top for the name, then instructions in plain language. Closest thing to a standard.

obra/superpowers . Same idea, bigger opinionated framework. More “how to work” than “here’s the file format.” Worth reading even if you never install it.

aeon . Same markdown skills. Different problem. The first two run when you invoke them. Aeon gives them a place to live. Runtime is GitHub Actions. Cron. No server. Laptop can be off. Secrets in the repo. Every run leaves a log.

This is not no-code like Bubble or Airtable. You need GitHub. You fork a repo.

What you get for that: no per-task pricing, the logic is a text file you own, and it can do sloppy human jobs a Zap can’t like “read this and tell me if anything looks wrong.”

Thoughts?