r/VibeCodersNest

This is the app (called "LWP+"), and I've shown here the video that I've published there:

https://play.google.com/store/apps/details?id=com.lb.lwp_plus

At first I was happy about what I created on the video, but then I thought that it looks more like a tutorial here, instead of maybe focusing on what's the most interesting. Surprisingly, ever since I've published the video, it actually got quite some views already (29 after 2 days), despite the fact it's a bit of a niche app. Still, I think maybe it can be improved.

I want to know what you guys think about the video (which has audio, BTW).

Here's about the app:

It's a live wallpaper app, that has these features:

1. Allows showing color/image/animation/video as content (users choose the file from the file system). No special effects so some users that complain about the dimming/zooming effects actually like using it. Users can also choose whether it should scroll or the type of automatic cropping.

2. Allows (some) control over the Material-You colors of the OS, as it lets users to choose the colors to report the OS about what's on the wallpaper. This means that like on Android 17, users can choose the colors they want (if the OS supports it) despite the content not matching it.

3. Setting of double-tap to lock the screen. Some launchers don't offer this, so I added it to the app too.

4. Some extra flags that (on some devices) should affect colors further, such as black/white text and/or black/white icons on status bar and/or lock screen and/or launcher.

The app is completely free, ad-based. Users can remove the ads including by just watching full screen ads. Originally it was created to offer dark-theme on devices as it wasn't a toggle on the OS settings, and was based on the colors of the wallpaper.

We started building this about 5 months ago as a task management tool. Got to 200+ signups and 28 paid users, which was great for a v1. But the feedback we kept getting was that people wanted something more like Copilot. An AI that actually works inside their tools and does things for them, not just another app to organize work in.

So we pivoted and rebuilt the whole thing. HealUp became Brevl.

Brevl is an AI agent you talk to in plain English that takes actions across your work tools. It works with Calendar, Docs, Outlook, Slack, Notion, Todoist and more.

Every write action (sending emails, creating events, updating docs) requires your approval before it executes. You see a full preview of what the agent is about to do and confirm or reject it. Nothing goes out without you saying yes.

There's also a built-in doc editor and spreadsheet editor. The agent can create and edit documents or spreadsheets directly, and you can import/export xlsx files.

Free tier if you want to poke around: https://app.brevl.co

100 stars. I know that's nothing by internet standards, but I genuinely didn't expect anyone outside my own GitHub profile to care about this.

Kairo started as a frustration project. I was deep in a coding session, had to context-switch to my task manager, and just... snapped a little. Opened a new Go module that same night. That was a few months ago.

For those who haven't seen it — Kairo is a fully local, keyboard-first terminal task manager. SQLite storage, 32 themes, fuzzy search, natural language deadlines, a Lua plugin system, a CLI API for scripting, and an optional MCP server if you want to point AI agents at your task list. No cloud. No account. No subscription. Just a binary you run in your terminal.

Things I didn't expect when building it:

• That people would actually use the Lua hooks (shoutout to the person who built a webhook notifier with them — genuinely wild)
• That the "32 themes" feature would be the thing people mentioned most
• That u/Tornado300 would show up and fix bugs I'd been avoiding for weeks

What's coming: encrypted multi-workspace support, a sandboxed plugin environment, and smarter task suggestions. I'm building this in the open and taking feedback seriously — if something annoys you, open an issue or just tell me here.

If you've been looking for a task manager that lives where you actually work — give it a shot.

→ github.com/programmersd21/kairo

Thanks for the stars. They matter more than they probably should.

We send ourselves things to “save for later”, and then never find them again.

That's why I built Keepr: https://keepr.website

It's a WhatsApp number that turns your messages into a searchable memory.

• Send it a link, note, voice memo, or half-formed thought
• Ask for it back later in plain English
• Keepr finds the right one and replies with it

No app to install. No folders. No tags.

It lives in a chat you already have open.

Open source: https://github.com/laksh2005/keepr

It's been a little over six months since I launched and it has been quite a journey. No exponential growth or huge user spikes but rather slow and steady growth. But in my opinion that is the best for building something actually valuable because you can react to user feedback along the way and constantly keep improving the app.

It's so crazy, just two weeks ago I was celebrating 2,000 users here and now I have hit another unreal milestone of 2,400! I can't thank everyone enough. I really mean it, so many people were offering their help along the way.

Of course I will not stop here and I am already working on the next big update for the platform which will benefit all the community. More is coming soon.

I've built IndieAppCircle, a platform where small app developers can upload their apps and other people can give them feedback in exchange for credits. I grew it by posting about it here on Reddit. It didn't explode or something but I managed to get some slow but steady growth.

For those of you who never heard about IndieAppCircle, it works like this:

• You can earn credits by testing indie apps (fun + you help other makers)
• You can use credits to get your own app tested by real people
• No fake accounts -> all testers are real users
• Test more apps -> earn more credits -> your app will rank higher -> you get more visibility and more testers/users

Since many people suggested it to me in the comments, I have also created a community for IndieAppCircle: r/IndieAppCircle (you can ask questions or just post relevant stuff there).

Currently, there are 2402 users, 1969 tests done and 587 apps uploaded!

You can check it out here (it's totally free): https://www.indieappcircle.com/

I'm glad for any feedback/suggestions/roasts in the comments.

I've spent the last few months building something and I'm finally at the point where I want to share it properly rather than just quietly hoping people find it.

The idea came from a frustration I kept seeing (and feeling myself): SQL tutorials teach the syntax fine but there's never a reason to care about the answer. You filter a table called employees, get a result, and nothing happens. Your brain doesn't bother keeping it.

I wanted to try a different approach. QueryCase teaches SQL through detective investigations. You get a briefing from Chief Fox (our mascot), a real database to query, and a mystery to crack. The JOIN matters when a suspect has an alibi. The WHERE clause matters when you're trying to find who entered the building at 22:13. The SQL is the tool for solving something, not the point in itself.

Here's what's actually in it:

• A structured learning path across 54 cases, going from Recruit through Rookie, Detective, Senior Detective, and Chief Detective. Each rank has drills and a level exam to pass before you progress.
• Sandbox mode where you can explore real datasets (IMDB movies, Spotify, sports stats, Steam games) and run whatever you want with no pressure and no mystery attached. Just free exploration against actual data.
• Everything runs in the browser using DuckDB WASM so there's nothing to install.

I'm a solo developer and this is genuinely early days. I'm sharing here because this community is exactly the kind of people I built it for, and I'd rather get honest feedback now than find out later I've built the wrong thing.

What's missing? What would make you actually stick with something like this versus what you've used before?

querycase.com if you want to take a look.

Any feedback appreciated!

👋 Hey n8n Community,

A while back I built a purchase order extractor for a friend who was drowning in PO PDFs. It let him batch-upload the documents through a form and pull all the data into a Google Sheet through the easybits extractor. That alone saved him a lot of manual re-typing.

Last week he told me his company is moving onto SAP, and he asked whether the workflow could also spit out EDI files so he can push the orders straight into the ERP instead of keying them in by hand. So I built that in, and while I was at it I made the whole thing a good bit more robust.

How it's set up:

• Batch PDF upload: the form takes one or many PO PDFs at once, and a toggle lets you decide per submission whether you also want EDI files out.
• Extraction: each PO runs through the easybits extractor one at a time and lands in a Google Sheet, one row per line item, with the source document name on every row so you can always trace a row back to its PDF.
• EDI 850 generation (optional): when the toggle is on, each PO is also turned into a valid X12 850 EDI file and saved to a Drive folder, ready to upload into SAP. A separate sub-workflow handles the generation, so the main flow stays clean.
• Duplicate check: after extraction it checks the PO number against what's already in the sheet. If that PO was processed before, it skips it, so you never get double entries.
• Flag summary: the completion screen tells you if any field was missing or looked off in an extraction, and lists any duplicates it skipped along with the PO number.

Short video attached showing a batch run of three POs with EDI generation switched on, then a re-upload of one of them so you can see the duplicate check catch it and report which document and PO number it was.

Both workflows (the main one plus the EDI sub-workflow) and a setup guide are here: https://github.com/felix-sattler-easybits/n8n-workflows/tree/f4dec1bef3561aa9e803bb21b96ebff1ab0dde04/easybits-purchase-order-extractor-v2

You'll also find it alongside 20+ other n8n workflows in my repo. If it's useful to you, a ⭐ really helps other builders discover it too: https://github.com/felix-sattler-easybits/n8n-workflows

Curious how the rest of you are handling the PO-to-ERP step. Are you going through EDI, hitting a direct API, or still uploading into the ERP by hand?

Best,
Felix

Hey folks, over the past months I've been building my own local Lovable for many reasons and the most important are:

- credit systems on app builders make me pay an extra fee to consume token

- vendor lock-in is real

- cloud offers cost a LOT of money. I've seen clients paying more than €100/month on Lovable Cloud for pretty basic websites

I'm a professional web developer for 10y now so I decided to build my own tool to share with my clients.

It's an all-in one app that saves me time in my day-to-day work because:

- I can generate websites from templates and customize them on the fly with integrated asset generation (image, video, sound, 3D assets)

- create github and vercel projects with auto deployment in 2 clicks

- use any AI providers (anthropic, openai, google, openrouter)

- track AI spendings

I've decided to share the app to gather feedback and improve it. Expect rough edges.

Important note: atm the app is available on mac, I'll publish to windows soon.

The app is free and no credit card is required. Tell me what you think: https://capacity.so/desktop

👋 Hey n8n community,

A few weeks back I helped one of our users whose data table extraction kept bleeding cells between rows: 95% of the data came out right, but the last 5% landed in the wrong rows, so he could never fully trust it. The way I fix pipelines like that is I never eyeball the output, I build a testing workflow that scores every extraction against a known-good reference so I can benchmark it and see if my changes actually helped.

I shared a first version of that tester, and a bunch of you asked for a v2 that lets you upload your own reference through the same form instead of hardcoding it. So that is what this is.

I also recorded a short video where I run a full test end to end, if you'd rather watch it in action.

How it works:

You upload two things on one form: the document you want to test, and a reference to check it against. The reference can be a CSV (exported straight from Excel) or a PDF/image of the same table. The workflow extracts your document, compares every cell against the reference, and shows a pass/fail card with the accuracy, the mismatches, and how long the extraction took. Each run is logged to a Google Sheet so you can compare engines and track accuracy over time.

The clever bit is trust. A CSV is trusted as-is because a human made it. A PDF reference gets extracted first and shown back to you to confirm before it is used as ground truth, so you are never grading one guess against another.

A few takeaways even if you skip the video:

1. Don't eyeball table extraction. Scoring every cell against a reference tells you exactly which rows slipped, instead of scanning 20 rows by hand.
2. Trust your reference before you trust the test. If your ground truth comes from an extraction too, verify it first, or a "100%" means nothing.
3. When rows slip, refine the descriptions. The easybits Extractor lets you write a description per data field, and that context is usually what fixes it. Tightening a field's description often covers new layouts too, without touching the workflow.
4. Your reference CSV headers have to match your pipeline field names. That one mismatch silently fails every row, so I added a small column map in the workflow to line them up.

Grab the tester here: https://github.com/felix-sattler-easybits/n8n-workflows/blob/e203ef38bc69db58e08e282b18bc287d69d7d85b/easybits-data-table-extraction-testing-tool/easybits_data_table_extraction_testing_workflow.json

It sits in my repo with 20+ other n8n templates I have built with this community: https://github.com/felix-sattler-easybits/n8n-workflows

How do you currently check whether an extraction is actually correct, by hand or with something automated?

Best,
Felix

👋 Hey n8n Community,

I've built a lot of finance workflows over the last few months for friends who run small businesses, and going back through my library I realised I'd never shared the most basic one people keep asking for: a simple batch invoice extractor. So I cleaned one up and pushed it to the n8n template library: Extract batch invoice data from form uploads with easybits and Google Sheets.

The idea is simple. You upload one or many invoices (JPG, PNG, or PDF) through a single form, and it extracts the data from all of them in one go, instead of dragging every invoice in one by one. Each invoice lands as a row in a Google Sheet, and when the batch finishes, the form shows a summary marking every file with a ✅ or ❌ so you instantly see which ones need a second look.

How it's set up:

• An n8n Form takes one or more invoice files.
• The files get split into one item per file, keeping the original filename.
• It loops over the invoices one at a time, sending each to the easybits Extractor, which returns the fields (invoice number, date, vendor, total, and so on) as a structured data object.
• The filename gets reattached, and a check runs over the critical fields.
• One row per invoice is appended to Google Sheets, with a pass/fail status.
• A batch summary is shown as the form's completion message.

A few things from the build that might save you time on your own flows:

• The extractor bundles everything you hand it into one request. Pass it all the files at once and you get one merged result back, not one per invoice. Looping one file at a time is what gives you a clean result per invoice. This one cost me a debugging session.
• Treat "missing" as a signal, not an error. The extractor returns null when a field isn't on the document. Instead of fighting that, I lean into it: a small check flags any invoice missing a critical field, which is what powers the ✅/❌ summary. Worth catching the sneaky empties too (the string "null", empty strings, whitespace), so nothing slips through looking present when it isn't.
• The fields are yours to change. The mapped fields are just a starting point, so you can add whatever you need to pull from your own invoices, like a VAT ID, PO number, or IBAN. The extractor also has auto-mapping, so you can upload one example invoice, let it detect the fields, and tweak from there.

I also recorded a short video showing how it runs end to end, which I'll post alongside this.

For more free workflows, feel free to check my GitHub as well: https://github.com/felix-sattler-easybits/n8n-workflows. A star helps other builders find it, so I'd be really thankful for that support.

How do you all handle the invoices that fail extraction? Curious whether people flag them for manual review like this or route them elsewhere.

Have a good start to the week.

Best,
Felix

Your agent can now search data from 2,600+ top iOS apps: onboarding, paywalls, pricing, post-paywall and more.

Ask things like:
“Give me five app ideas based on recently launched subscription apps that make 50k+”
“Compare the paywalls of the top meditation apps”
“Show me streak mechanics that aren’t Duolingo clones.”

It works with any agent.

We also launched "Ask" directly on ScreensDesign, so you can try all of this without connecting anything.

I needed to drive traffic and improve my domain authority (DA) for SEO

so I compiled a list of sites where I could list my projects

these sites focus on AI projects

which ones should I add?

As a DevOps engineer, I’m so proud of this one. 🚀

httpsornot.com has been live for about 6 months, and we’ve already checked 15k+ domains. 💻 🤓

What it covers today:
- HTTPS/SSL grade (A+ to F)
- cert validity, issuer, expiry
- HTTP → HTTPS redirects + full redirect chain
- security headers (HSTS, CSP, etc.)
- mixed content
- response times per hop
- HTTP/3 (QUIC) detection
- bulk checks (up to 10)
- shareable report + PDF/JSON export
- domain monitoring with email/Slack/webhook alerts
- Certificate Transparency alerts for newly issued certs
- free public API for CI

Basic check needs no signup. 🔐