r/nocode

I recently worked on a project that was for the healthcare world. The project itself was a simple internal management system.

For those that don't know, healthcare applications require compliance with HIPAA. Essentially, make your application secure. I used Bolt for the frontend and Xano for the backend.

We encrypted the db fields that were identified as PHI and we decrypted them when queried. We had RBAC middleware. Audit logs. All the compliance hoops.

It was a lot, but in the age of AI, it's only getting easier to build. What I found interesting is that in the build process, Claude 4.6, while building on Xano, used conditional if statements more than I would have. For the en/decryption aspect, we pass in a string and return the respective value. It's either decrypted and readable, or it's decrypted and needs to be encrypted.

For the individual fields of the records, Claude constructed a system to update the response var property by property. It checked if the title was empty, the name was empty, etc.

Nothing wrong with robust checks. This is is somewhat appreciated. It's just a lot of looping and not wholly necessary.

Instead, I would have just an expression and filters. Regardless, with minor prompting and construction, anything's possible.

We also wrote our own unit tests using CC outside of Xano, although Xano does support testing and test suites of its own.

Let me know if you have any questions on the app build, or what took the longest, etc. Just wanted to share that this was my first HIPAA build that I can now add to the books!

I've been in product management for 20+ years. I've never written production code. I've always been the person who describes what to build, not the person who builds it.

I've been using Claude Code for a while now, and at some point I shifted from playing around to actually building full projects end to end. Here's what the workflow looks like for someone with zero coding background.

The short version: the PM skills I've used my entire career turned out to be the only skills that matter.

The spec is the entire game. Claude Code builds exactly what you tell it to. The problem is that "tell it to" means something very specific. "Build me a client tracker" gets you junk. "Build a Clients database with fields for Company Name (title), Contact Person (text), Email (email), Status (select: Lead / Active / Completed / Lost), Monthly Value (number, currency USD)" gets you something you'd pay for. Writing specs like this is what PMs do every day. It transfers directly.

Plan before build. Claude Code has a Plan Mode where it reads your spec and shows you what it's going to build before touching any files. Use it. I caught major structural problems during planning that would have cost hours to fix later.

Describe what you see, not what you think the code problem is. When something breaks, I say "I clicked this button, expected this, got that instead." Claude Code figures out the fix. Same approach I used giving feedback to engineering teams for 20 years.

Skill files change everything. I write a CLAUDE md file for each project that gives Claude Code the full context - what we're building, who it's for, what phase we're in, what to do and what not to do. The difference between working with and without a skill file is massive.

The build is the easy part. The actual "building" takes maybe 20% of the time. The rest is figuring out what to build, writing the spec, testing like a buyer would, writing the sales page, and packaging it. If you come from a product or business background, you already have those skills.

Anyone else here building with Claude Code? Curious what workflows are working for other non-developers.

For a long time, a lot of our internal processes lived in spreadsheets.

At first that felt manageable. One file for one process, another file for another team, a few manual workarounds, a few things living in email, and somehow it all still worked. But over time it turned into what we started calling an Excel swamp.

The real problem was not that we needed one giant platform. It was that we had too many small but important internal workflows depending on fragile spreadsheets, scattered data, and manual handoffs.

We needed a way to replace those ad hoc Excel-based processes with structured internal apps without turning every small request into a full development project. We had looked at a few options, but eventually landed on UI Bakery because it felt much more practical for lightweight internal tools and easier to roll out across different teams.

What changed for us was not just speed. It was that these processes stopped living in random files and started becoming actual apps with structured inputs, database-backed storage, and group-level access control.

We used it for a mix of internal tools across teams, from simple maintenance flows to more structured company-wide apps, and that helped us get out of the constant temporary-system-that-somehow-became-permanent mode.

That was the real win. Not “we got shiny new software,” but that internal requests stopped depending on one fragile spreadsheet or on waiting forever for central development resources.

Been working on this for a while and finally open sourced it. Every time I start a new chat my AI has amnesia. Cloud memory services charge insane prices for something that should just run on your machine.

modus-memory is a Go binary (~6MB) that gives any MCP-compatible client (Claude Desktop, Cursor, Cline, whatever) persistent memory. Everything stored as plain markdown files you can grep, edit in VS Code, or back up with git. No SQLite, no Postgres, no Docker, no Python.

What’s under the hood:

∙	BM25 search with field boosting and query caching (cold searches in <5ms, cached in microseconds)

∙	FSRS memory decay — same algorithm Anki uses. Stuff you never look at fades. Stuff you keep referencing gets stronger. Keeps the vault clean over time instead of becoming a junk drawer

∙	Cross-referencing — search for “authentication” and it also surfaces related facts, entities, and notes that share subjects/tags even if they don’t contain the keyword

∙	If you run llama-server or any OpenAI-compatible endpoint locally on port 8090 it’ll use your model for query expansion. Completely optional

There’s a free tier (1K docs, full search) and a $10/mo tier that unlocks the decay, cross-refs, and unlimited docs. Honestly still figuring out the right split so I’m open to opinions on that.

Also built a Khoj importer for anyone affected by their cloud shutting down on the 15th. One command converts your export into searchable markdown.

Happy to answer questions about the implementation. The BM25 and FSRS stuff was the most interesting part to build if anyone wants to nerd out about that

Hey everyone,

Lately I’ve been diving deep into automating workflows for my projects, and n8n has honestly made a ton of things way easier. From client onboarding to internal task flows, I’ve set up multiple automations that used to take hours manually, now they run almost hands-free.

I just want to know what’s your go-to tool for automation these days? Do you stick with n8n, Zapier, Make, or something else? Any tips, favorite setups, or lessons learned would be amazing to hear.

I’d love to see how others are streamlining their work and maybe pick up some ideas for my next projects.

Thanks!

**I spent a week brainstorming app ideas that actually solve real problems. Here are 50 of them. Steal one.**

Most app ideas are either "Uber for X" or another to-do list. I wanted ideas that feel genuinely useful — civic tools, community apps, business ops, and personal life stuff. None of these exist in a good form yet (that I know of).

Feel free to build any of these. I just want them to exist.

---

## 🏙️ CIVIC APPS (your city, but functional)

1. **Street hazard reporter** — Snap a photo of a pothole or broken light, app auto-routes it to the right city department. You get notified when it's fixed.

2. **Smart parking rules** — Point your camera at any street sign and instantly know if you can park, for how long, and when street cleaning hits.

3. **City lost & found** — Report lost items or pets with location tagging, matched digitally with found reports across the city.

4. **Waste & recycling guide** — Search any item to know which bin it goes in. Pickup reminders by address.

5. **Noise complaint logger** — Timestamped audio clips submitted directly to code enforcement, with a case tracker so it doesn't just disappear.

6. **Local permit tracker** — Apply for permits, track approval status, get notified when documents are ready. No more calling the office.

7. **Public transport live map** — Real-time bus/tram positions, delay alerts, and crowding levels. (Yes these exist. No, none of them are good.)

8. **Restaurant inspection scores** — Scan a QR code at any restaurant and instantly see its latest health inspection report.

---

## 💼 BUSINESS / FIELD WORKER APPS

9. **Field worker task manager** — Offline-first task dispatch, GPS check-ins, and photo proof-of-work for field crews. Built for people who don't sit at desks.

10. **Local permit tracker (business side)** — Contractors managing multiple sites track all permit statuses in one place.

11. **Field service invoice builder** — Generate and send invoices on-site with digital signature capture and a payment link. No laptop needed.

12. **Fleet fuel tracker** — Log fuel stops, mileage, and maintenance per vehicle. Flags anomalies (someone's gaming the fuel card).

13. **Shift swap marketplace** — Employees post shifts they can't cover, colleagues claim them, manager approves in one tap. Kills the group chat chaos.

14. **Contractor timesheet app** — GPS-verified clock-in/out, project tagging, and auto-generated PDF timesheets for billing.

15. **Site safety checklist** — Daily walk-through checklists with photo attachments and incident reporting. OSHA-ready exports.

16. **Delivery proof app** — Photo + GPS + timestamp proof of delivery, signed off by recipient on-screen. No more disputes.

17. **Local supplier directory** — Verified B2B directory of local suppliers with RFQ requests and delivery radius filtering.

18. **Pop-up market organizer** — Manage vendor slots, layouts, payments, and comms for markets and fairs. One app instead of 6 spreadsheets.

---

## 🏘️ COMMUNITY APPS

19. **Neighborhood watch board** — Verified incident reports from residents, visible only to confirmed neighbors in a zone. No randos.

20. **Hyperlocal classifieds** — Buy/sell/free items within a set radius. No shipping — pickup only. Craigslist without the murder vibes.

21. **Community garden planner** — Map plots, assign members, track watering schedules, share harvest logs.

22. **Skill swap network** — Trade skills with neighbors. Plumbing for web design. Babysitting for guitar lessons. No money changes hands.

23. **Block party coordinator** — Polls, RSVPs, food sign-ups, and road closure request submissions. All in one place.

24. **Local sports league manager** — Schedule games, track standings, collect fees, manage rosters for amateur leagues.

25. **Neighborhood book exchange** — List books you're done with. Browse what neighbors have. Coordinate a drop-off.

26. **Tool lending library** — Borrow a drill or lend your ladder to neighbors. Tracks condition, availability, and returns.

27. **Carpool matcher** — Match commuters on overlapping routes. Regular carpools with split-cost tracking.

28. **Community fundraiser hub** — Hyperlocal crowdfunds for real causes — fixing a playground, helping a neighbor after a fire.

---

## 🙋 PERSONAL APPS (that should exist but somehow don't)

29. **Home maintenance log** — Track appliance ages, service dates, and upcoming maintenance. Get reminders before things break, not after.

30. **Subscription tracker** — Every subscription, renewal date, and cost. One screen. "You're paying $340/month in subscriptions" hits different when you see it.

31. **Symptom & medication journal** — Log symptoms, meds, and moods daily. Export a clean PDF to show your doctor. Replaces the "I don't remember when it started" conversation.

32. **Grocery price tracker** — Scan barcodes across stores to track price history and know the best time to stock up.

33. **Gift idea manager** — Store ideas for everyone in your life with budget tracking and purchase reminders. Never panic-buy again.

34. **Habit tracker (no gamification)** — Streaks, flexible scheduling, no-guilt skip days. None of the Duolingo guilt-trip nonsense.

35. **Trip packing checklist** — Destination-aware packing lists. Checks the weather forecast. Remembers what you always forget.

36. **Sleep quality logger** — Bedtime, wake time, quality rating, notes. Surfaces actual patterns over weeks without needing a $400 ring.

37. **Personal finance snapshot** — Sync accounts, see a one-page weekly breakdown of where your money actually went. No budgeting required.

38. **Plant care reminders** — Track each plant's watering and feeding schedule. Includes care guides by species. For people who keep killing their monstera.

39. **Reading goal tracker** — Annual reading goals, book log, notes, reading stats. Goodreads but fast and not owned by Amazon.

40. **Meal plan & shopping list** — Plan the week's meals, auto-generate a grocery list, check off as you shop. Solves the "what are we eating" problem.

41. **Car cost tracker** — Log fuel, insurance, servicing, tolls. See your true per-km cost of car ownership. Most people have no idea.

42. **Language vocabulary drills** — Build custom word lists, drill with spaced repetition. Works offline. No owl.

43. **Utility bill splitter** — Track shared household bills, log who paid, see running balances between housemates. Kills the awkward money chat.

44. **Daily journal with prompts** — Private journal, optional writing prompts, searchable archive. No social features. Just writing.

45. **Password-free secure notes** — Biometric-locked notes for sensitive info that doesn't belong in a password manager — card PINs, locker codes, account numbers.

46. **Workout log (no fluff)** — Sets, reps, weight. PRs and volume trends. That's it. No macros wizard, no coaching upsell.

47. **Personal CV builder** — Guided questions → polished PDF CV. Keeps version history. Useful once every few years but crucial then.

48. **Photo memory yearbook** — Auto-pulls your best photos from each month and compiles a shareable annual album. No effort required.

49. **Elderly check-in network** — Seniors paired with volunteers for daily check-in calls or visits, tracked by family members.

50. **Neighborhood watch (personal alert)** — Opt-in alerts for incidents near your home address. Not the scary Nextdoor version.

---

I'm not building all of these. I'm building one. Which one would you actually download?

A few weeks ago I decided to speed things up by relying more heavily on a no-code backend tool for one of my projects, and at first it felt amazing, faster builds, less friction, everything just worked, and I genuinely thought I had found a shortcut that would save me weeks of work, then I started noticing small changes in the logic that I didn’t explicitly set, and at first I assumed it was just me misconfiguring something, but the more I checked, the more it felt like the system was making decisions on its own, and while nothing catastrophic happened, it was enough to make me pause because in development small unpredictable changes are manageable but in production they become a real liability, and it made me realize that while speed is great, control matters way more once real users are involved, so now I’m rethinking how much I rely on AI-assisted or no-code tools for critical parts of my stack and I’m curious how others are approaching this..

I’ve been noticing a pattern across a lot of no-code tools that offer announcement bars / banners.

Most people add them… but almost nobody uses them well.

After testing this on a few projects, here are the biggest mistakes I keep seeing:

1. No clear intent
A banner saying “Welcome to our website” does nothing.
Users are scanning for value discount, urgency, or relevance.

2. No urgency = no clicks
If there’s no time-bound reason to act, people ignore it.
Simple things like countdowns or “ends tonight” messaging make a huge difference.

3. Too generic
Same message for every visitor = low conversions.
Even basic targeting (new vs returning users) can improve performance.

4. Bad placement + timing
Showing a banner instantly isn’t always the move.
Sometimes delay or scroll-based triggers work better.

5. Overcomplicated tools
This is the biggest one.
A lot of tools try to do everything (popups, funnels, forms, etc.), and setting up something simple becomes unnecessarily hard.

That friction is why most banners never get optimized.

I ran into this myself and ended up building a small tool to keep things focused just announcement bars, countdowns, and website banners without all the extra noise.

Not trying to pitch here just sharing what I learned after seeing how underused this space is.

Curious how others here are using announcement bars are they actually converting for you or just sitting there?

Just a quick warning : I do not recommend using Xano at all, especially for production.

Their AI assistant can behave unpredictably and introduce unwanted changes, which makes the platform dangerous to rely on in a live environment.

I’ve reported this multiple times with no real fix so far ( the team behind Xano seems to don't really care about feedbacks btw ) so be very careful if you’re considering using this no code tool who can create major security issue for your app and your customers.

I've spent the last few weeks talking to people who build apps with tools like Lovable, Bolt, and Cursor. The number one complaint isn't the AI quality or the code it generates, it's what happens AFTER you build.

The story is always the same:

• Build something cool in 20 minutes
• Try to deploy it
• Spend 3 days learning about build commands, environment variables, DNS records, SSL certificates
• Either figure it out with a massive headache or give up entirely
• Run into "production" issues after finally figuring it out

I've seen people call this the "Technical Cliff" and honestly I think it's holding back the entire no-code/AI builder movement. The tools for CREATING software have gotten insanely good. The tools for DEPLOYING that software still assume you're a developer.

Vercel, Netlify, Railway are all great platforms, but they're built for people who already know what they're doing. The UX assumes you understand what a framework is, what "dist" means, why you need environment variables, etc.

For context I'm a CS grad so this stuff is second nature to me, but watching non-technical coworkers try to deploy a Lovable app made me realize just how massive this gap is. One person literally gave up after few hours of trying to get their portfolio site live. A STATIC SITE.

I'm actually building something to try to solve this (warpship.ai if you're curious) but more than anything I want to know: is this actually the biggest pain point you run into? Or is there something else about the build-to-launch-to-scale pipeline that's even worse?

I'm the head of ops at a 35-person startup. we sell a SaaS product and we have a bunch of internal workflows that require someone to look up customer data, update records, issue refunds, manage feature flags, and pull reports. for the first year our engineers built quick admin pages whenever ops needed something. it worked but every request meant pulling an engineer off product work for a day or two.

retool changed that. I'm not a developer but I can build in retool. it connects to our postgres database and our APIs, and I drag and drop components to build the interface. need a table that shows all customers with overdue invoices? 15 minutes. need a form that lets our support team update a customer's plan tier? 20 minutes. need a dashboard that shows our daily signups and churn? maybe 30 minutes with a couple charts.

the biggest internal tool I built is our customer lookup page. support reps paste in a customer email and it pulls their account info, subscription status, usage data, recent support tickets from intercom, and payment history from stripe. all on one page. before this our reps were switching between 4 different tabs to answer basic questions. the lookup tool cut our average ticket resolution time by about 40%.

I've built maybe 12 internal tools in retool over the last 10 months. our engineers have built zero internal admin pages in that time. our CTO told me retool paid for itself in the first month just from the engineering hours saved.

the workflow automations are useful too. I set up a flow that checks for customers whose trial is expiring in 48 hours and adds them to a list in hubspot for the sales team to follow up. that used to be a manual process someone did every morning.

for documenting what each tool does and how to use it (so new hires can figure things out), I keep a guide in notion. when I build a new tool I'll walk through how it works by talking through it out loud and dictating through willow voice. "this tool pulls customer data by email, the refund button in the top right issues a prorated refund through stripe, only ops and support have access, do not use the delete button unless you've confirmed with the account manager." quick and easy to capture while I'm still looking at the tool.

the pricing is per user so it gets expensive if your whole company needs access. we only give access to ops and support (8 people) so it's manageable.

other ops people at startups, are you using retool or something similar? I've heard good things about appsmith as an open source alternative but haven't tried it.