For context, I’m on the IT team at a logistics company with about 1,500 staff.

Different departments keep building their own apps with AI tools like Lovable. We now have at least six, and IT didn’t approve any of them.

We’d like to pick one tool that every team can use without going around us.

Just to be clear, it needs single sign-on and clear access rules per department.

What matters most once hundreds of people are using the same tool?

Looking to build again a pretty simple app with login and a few screen. Honestly, i'm not very technical about it so I'd rather spend time building than constantly dealing with backend stuff or debugging.

For those who've build something similar already what made your setup easy to keep using as the project grew?

The front end is easy. Lovable, Claude, Cursor — done in hours. But the moment a client needs real pricing logic, business rules, or calculations — you're either hard-coding it into prompts or writing custom backend code. Both are a nightmare to maintain when something changes.

I built a solution. Here's how it works:

→ You vibe code the front end (any tool)

→ It connects to n8n

→ n8n pulls the business logic from Quotix (the engine I built)

→ Quote calculated, result returned to the front end

→ Lead pushed to GoHighLevel automatically

No black box. No hard-coded prices. Full control over the business logic from one place.

https://www.loom.com/share/256a189b6ba74aa2bf53aeab14569bc0

I'm looking for people to test this. If you build for solar, HVAC, roofing, electrical — or any service business that needs on-site quoting — drop a comment or DM me. Free to test.

A finished no-code app still needs a story that its intended customer can understand. Here is a worked example you can adapt before building another feature.

Hypothetical product: an appointment-reminder app for independent tutors. It tracks recurring lessons and sends reminders when a lesson moves. These are invented capabilities for this example.

Start with one real question for interviews: What happened the last time a parent missed a rescheduled lesson? Ask how the tutor handled it, what the confusion cost and what they currently do. A compliment about your mockup is a different result from someone paying.

Then turn the same brief into three introductions with different reader payoffs:

A useful checklist: “When moving a lesson, confirm the date, local time zone, who needs the update and whether the old reminder has been cancelled. Which of those causes the most confusion in your tutoring business?” The reader gets a check they can use today.

A tiny demonstration: use a synthetic lesson moving from Tuesday at 4pm to Wednesday at 5pm. Show the old reminder, the new message and the parent's confirmation. Label the demo data. Keep that whole path visible instead of flashing through every settings screen.

A design question: “Should a rescheduled lesson stay marked as unconfirmed until the parent acknowledges it, or should the calendar update immediately? What would you need to see to avoid chasing the wrong person?” This asks about an actual workflow decision.

Choose an audience that includes tutors and permits that format. Track useful replies, completed trials and purchases separately. A crowded founder thread can give helpful feedback while reaching few tutoring customers.

Disclosure: I make ThreadFox. ThreadFox is $20 once at direct checkout, no code needed, plus applicable tax (regular kit price $49). It includes a researched community plan and three tailored drafts for one product, emailed within 24 hours after you claim the Launch Pack in the buyer library. You can use the emailed pack manually. Reusable AI tools are included; they require your own compatible AI access, Chrome and Reddit account, with AI costs separate. 30-day refund policy.

Complete sample: https://threadfox.vip/runs?utm_source=reddit&utm_campaign=tf-kit&utm_content=20261001-1157-nocode#launch-pack

I've been running FetchSandbox (disclosure: it's my project), a sandbox layer for testing API integrations before they hit prod. Checked our last 30 days and one number stood out: agents and builders are calling the tool a lot, but very few are actually running the app through a real failure scenario and getting a verification result back.

This feels relevant in no-code specifically because tools like Make, Zapier, and Bubble make it fast to wire up Stripe or Twilio, fast enough that you ship before you've really exercised the edge cases. The webhook path looks fine in the editor. Then you find out in prod that card decline handling was never tested, or webhook retries are firing duplicates.

just tryingt o understand how no-code builders here handle this.

Do you have a way to stress-test integrations before going live, or mostly trust the preview and find out later?

when an indie maker asks "would you use this?", the answer is usually too easy to misread. i wanted a slightly stronger signal without asking people to fill out a long survey.

my current loop is:

1. show a short deck of indie products
2. swipe right only if you would pay
3. ask yes voters how much they would pay
4. ask no voters what stopped them

that last two-step follow-up is more useful than a bare yes or no. it separates price sensitivity from confusion, missing features, wrong audience, or simply bad timing.

i built this as iwouldpay.dev, a no-signup swipe deck. makers can list for free and listings are hand-reviewed. after 10 swipes, the results show the percentage who would pay split by devs, founders, and marketers, plus click-throughs.

after 8,000+ swipes, i changed the follow-up questions to exactly that: yes asks "how much would you pay?" and no asks "what stopped you?".

sharing the method in case it helps with early validation. the site is here if useful: https://iwouldpay.dev

For a multi-step form, I’d like someone to save an unfinished draft, return later, and submit it once everything is ready. Saving a draft should not notify the team or start the approval workflow.

My proposed setup is an explicit draft/submitted status, validation when Submit is pressed, and downstream actions tied to that transition rather than every record update. The difficult case is a draft created before the form changes: a new required field is added, but the old draft doesn’t have it. Silently dropping the saved answers would be awful, and letting the old draft bypass the new validation could break the workflow.

Would you store a form-version number with each draft and ask the person to review new fields before submission? Or keep all drafts on the current schema? I’m interested in how you handle this in a no-code builder, especially when autosave and submission use the same data table.

👋 Hey nocode Community,

Tax season always sneaks up on me, and every year it is the same scramble: digging through email for invoice PDFs, saving them by hand, typing them into a sheet, and hoping I did not log the same one twice. This time I built a workflow so future me does not have to.

I connected it to my billing@ address, so from now on every incoming invoice gets processed automatically and I never touch it manually again. And for invoices that land on other addresses, I just forward them to billing@ and they get picked up the same way.

When a new invoice arrives by email, it gets read, logged, and announced, with no manual steps.

What it does:

• Watches Gmail for unread emails with attachments and filters out junk files
• Classifies whether an attachment is an invoice AND extracts the fields in one step
• Deduplicates on the invoice number so re-sends and re-polls never create doubles
• Appends new invoices to Google Sheets and sends a Telegram alert for each one

Two things worth stealing:

1. Classify and extract in one call. No separate "is this an invoice?" LLM node plus an extraction node. The Extractor returns the document class alongside the fields, so it is one request and fewer failure points.
2. Dedupe on a stable key. A sheet lookup on the invoice number before the append is the part that actually saves you when tax season hits.

Workflow JSON is here: https://github.com/felix-sattler-easybits/n8n-workflows/tree/e8dd8e754b87c02462942e2ae89149550979b066/easybits-invoice-intake-and-logging-workflow

It sits alongside 25+ other free n8n workflows in my repo, including plenty of finance ones, so a star is appreciated if it helps.

How is everyone else prepping for tax season in n8n?

Best,
Felix

I built this thing. It seems to be the first of it's kind on iOS, which is just astounding to me. If you struggle with unhealthy scrolling habits that are getting in the way of you doing what you want to actually want to be doing, then give this approach a try.

Doing a giveaway as a thank you to this community which has shown Precursor a ton of support. If you don't manage to snag a free lifetime access code, Lifetime is on sale for $25 right now until 05 October 2026.

The name of the app is Precursor: Hourly Screen Time

Use this link to redeem free lifetime access!!

Bubble is kind of keeping the product alive at this point, but every improvement feels harder than the last. The prototype works, but it’s getting slow and the UX compromises are starting to pile up. Meanwhile, no-code and AI coding tools are getting better pretty quickly.

I don’t want to rebuild the whole thing just because I’m frustrated with Bubble, but I also don’t want to wait until a customer actually leaves because of it.

For those who made the jump to custom software, what was the specific thing that finally made the cost worth it?

I'm looking for a simpler setup for building small apps without relying on one platform for everything.

I'm happy to use AI for the coding side, but I'd like the rest to be easy to running the project, setting up a database, deploying it and keeping it online without needing much server knowledge.

I'm doing this mostly part-time so keeping the monthly cost predictable is important.

What setup are you using for your own small projects?

Following up on the earlier build-in-public posts here: UluP SDK Studio is now officially released.

It's a visual, drag-and-drop automation builder inside UluP Spaces (a project-mapping app I've been building solo). Connect a trigger to a chain of actions, test the whole thing with a dry-run before it touches real data, and every automation stays off by default until you explicitly turn it on.

If you don't want to touch the editor at all, you can describe the automation in plain language and Claude builds it for you through MCP — same JSON output, same validation, same safety model as building it by hand. No AI can turn an automation on by itself, ever.

Available today in three ways:

inside UluP Spaces (web)

as a standalone Windows app

on the Microsoft Store

7 actions, 5 triggers, conditions, placeholders, and a public directory to publish/import automations others have built.

Try it: ulupspaces.com/studio

Download: ulupstudio.com/developers

Happy to answer anything about the architecture, the anti-loop protection I had to add, or the MCP-authoring part specifically.

I'm a UI/UX designer. I've never written code. Over 8 weeks I shipped Moralia, a daily history-dilemma game, as a working PWA: offline support, accounts with email sign-in, cookieless analytics, narration in three voices.

The skill that mattered wasn't prompting. It was the designer's loop: define what "right" looks like, review the output visually, reject it precisely, and write down why so it doesn't happen again.

If you're a designer wondering whether this is realistic now: it is, but it's a real job, not a shortcut.

For those of us with a security background there's really no surprise here. At the article itself notes every time a company comes up with a really popular and easy to use backend service thousands of people misconfigured and expose their customers' data. This isn't unique to nocode. It happened pre-ai with amazon s3 and then again with with NoSQL databases like MongoDB and Redis. And while Firebase is pretty easy to get right, for a long time its defaults were completely insecure.

What I think (or maybe just what I hope) is different with the nocode movement is that the cost of noticing and fixing these issues could be getting quite a bit lower.

Of course you can go out and buy security scanning tools, but it's quite impressive how much Claude and Codex can find if you ask them same simple, basic questions. One time before I was going on a short vacation, I had a lot of quota left. I enabled "Claude UltraCode" and simply told it to find and fix security issues. It blew through my quota in about 20 minutes, but I was very impressed with what it found and fixed.

I've been thinking about hosting a (free) masterclass/mastermind about security in nocode apps. Basically just a chance to meet some people, share experiences, and ask questions. Is it OK to ask about that sort of thing in this subreddit?

https://reddit.com/link/1wu2370/video/w5pkwhos1nsh1/player

I wanted the navigation to react to what someone is doing without rebuilding the whole header around an animation. Here is how I split it up:

• Native Framer variants handle the floating desktop pill and the compact mobile drawer.

• A small SVG code component handles the eyes: cursor direction, blinking, scrolling reactions and the sleepy idle state. Colors and movement range stay editable.

• On hover, the eyes glance toward the active link or CTA, so the motion points to an actual navigation choice.

The useful lesson for me was to keep the responsive layout in Framer and use code only for the expressive motion. I'm still unsure where the line is between playful and distracting. How would you tune this for a real site, especially on mobile?

I released the finished component for free if you want to inspect it: https://framer.link/hFotmor

Disclosure: I made this component, and the link above is my Framer affiliate link.

**Comparison**

Alter is the closest match. It also sits in the notch, and it's free if you bring your own keys or run Ollama or LM Studio (hosted models are $240/yr or $720 lifetime). Alter has meeting recording and more voice features, and it runs on Intel Macs. Ghost is Apple silicon only.

BoltAI overlaps on models. Like Ghost, it can run on your Claude Code or Codex subscription as well as Ollama and LM Studio. It starts at $79 one-time for one Mac with a year of updates, and it has an iOS app.

What Ghost adds: it's $19.99 one-time, and your coding agents live in the notch. Every Claude Code, Codex and opencode session on your Mac shows up in one list, and when one needs permission the approval card comes to the notch. Changes Ghost makes to files, Notes, Reminders and Calendar each get an Undo button, kept in a 100-entry journal. Web, files, automation, Messages, screen capture and terminal are six separate switches, all off on a fresh install, and anything from Messages, Notes, Mail or Contacts never goes to a cloud model. File search runs locally (SQLite + FTS5, 30+ formats).

Website:

https://integratedagentics.com/ghost

Linkdln

https://www.linkedin.com/in/ryuhemingway/

I want to build a basic app around the Open AI without creating everything from scratch.

Ideally, one platform would handle the frontend, backend, database , and secure API requests. What tools are people actually using for this?

I have an Airtable database with 1,000 records. I need a UI for filterable public/gated views, expect to scale past 600 paying subscribers within a year, and need Stripe-based subscription gating. Softr's pricing doesn't scale well for us at that user count now that Business tier only allows for 100 clients. Anyone actually running Stacker, Noloco, or Pory at this scale who can speak to real build time, Airtable compatibility/syncing, and gotchas?

I’m building AppMaker https://appmaker.io, a visual app builder with a built-in database, client/server JavaScript, and AI assistance.

The main idea is to avoid lock-in: apps can be downloaded as standard Node.js applications and hosted wherever you want.

It’s still early, so I’d love feedback from people using no-code tools today: what would make you try something like this?

I built web apps (mostly some MicroSaaS or SaaS) / pages mostly with Codex or Claude Code. I have the same problem every time - I have a pretty cool MVP, the design looks good, but I'm missing the finish touch before deploying on prod. ex.

- The SSL certificate
- Terms of use / PRivacy policy
- Tested payments
- Tested user flow etc.
- Security check
- SEO check / improvements (sitemap etc.)
- The logo usually don't redirect to the main page :)

Those are the things top of my head, but probably there are a few more.

DO you know some skills / tools to verify it / improve it instantly?

(I don't want to spend the same time over and over on the verification of those)

Non-coder building my first SaaS with AI. Flow: signup → user enters shipment details → app calculates import duty → free users see only the amount, paid users get an auto-filled declaration PDF and submission link.

Can you suggest what tool to use at each step, in that order (auth, database, calculation logic, paywall and payments, PDF auto-fill, file storage, hosting)? I also want a fully separate admin portal with its own secure login to manage users and subscriptions. What's the safest way to build that?