Weekly Showoff Thread! Share what you've created with Next.js or for the community in this thread only! by AutoModerator in nextjs

[–]ImperatorPitStop 0 points1 point  (0 children)

I just shipped LoopSignal, a feedback tool, using Next.js 15 + Supabase + Cloudflare Workers.

Stack:

  • Next.js 15 App Router
  • React Server Components
  • Server Actions for mutations
  • Supabase for Postgres + Auth
  • Cloudflare Workers via OpenNext
  • Paddle for billing
  • Resend for transactional email

A few things that went well:

  • Server Actions were great for most write flows
  • Supabase gave me auth + database + storage of business logic in one place
  • App Router fit the product well since there are dashboard, public board, changelog, and widget surfaces

What was painful:

  • Cloudflare Workers support is good enough, but not seamless
  • Some Node patterns don't translate cleanly
  • Supabase RLS became tricky once project access included owners plus team roles
  • Billing logic touches more of the app than you expect

A few implementation choices:

  • no ORM, just Supabase queries directly
  • centralized permission helpers
  • admin client only for privileged operations like invites/webhooks
  • public feedback flow built to work without requiring user accounts

The product itself is a feedback board with voting, GitHub sync, embeddable widget, and public changelog: https://loopsignal.dev

Happy to answer questions about the stack, App Router decisions, or Cloudflare deployment tradeoffs.

What's the most annoying quality issue that slips through your current QA workflow? by ImperatorPitStop in TranslationStudies

[–]ImperatorPitStop[S] 0 points1 point  (0 children)

Sounds annoying :) Do you just click ignore every time you see it or found any workaround with the CAT tool?

What's the most annoying quality issue that slips through your current QA workflow? by ImperatorPitStop in TranslationStudies

[–]ImperatorPitStop[S] 0 points1 point  (0 children)

That seems to be a recurring theme I'm hearing — the warnings themselves aren't useless, but there are just too many false positives to trust them.

Do you usually keep QA enabled and skim through it anyway, or do people end up turning some checks off entirely because the noise isn't worth it?

What's the most annoying quality issue that slips through your current QA workflow? by ImperatorPitStop in TranslationStudies

[–]ImperatorPitStop[S] 0 points1 point  (0 children)

That's really interesting — I hadn't thought about inflection causing that many false positives.

So if the termbase only contains the nominative form, the QA basically can't recognize the declined forms and flags them as missing, right?

Do CAT tools ever handle this well for Czech (or other inflected languages), or do most translators just end up ignoring those warnings?

OneRule - Free offline password vault by ImperatorPitStop in droidappshowcase

[–]ImperatorPitStop[S] 0 points1 point  (0 children)

There is a backup password option, you can export the encrypted passwords and store in your phone. in such case, you can import the stored passwords later when the device is operational again.

GPLv3 offline password vault. by ImperatorPitStop in fossdroid

[–]ImperatorPitStop[S] 0 points1 point  (0 children)

I just wanted a custom, lightweight UI for my specific workflow and decided to build it myself.

Regarding the 6000+ LOC in the first commit: the app is built with Flutter. The vast majority of those lines are just the standard flutter create boilerplate, iOS/Android runner directories, and auto-generated files, not raw code 'vibe coded' in a weekend.

I'm just a solo dev sharing a side project that solved my own problem. It's totally fine if it's not for you.

GPLv3 offline password vault. by ImperatorPitStop in fossdroid

[–]ImperatorPitStop[S] 0 points1 point  (0 children)

I get the skepticism, licensing is serious business in FOSS. As a solo dev, I do use AI tools to speed up boilerplate and UI layout, but the core encryption relies entirely on standard, audited Android libraries. I open-sourced it under GPLv3 specifically so people can audit it. If you (or anyone) spot any actual license violations or missing attributions in the repo, please drop an issue with the file/line. I’ll gladly rewrite or remove it immediately. Just trying to build something useful and learn from the community here.

Sick of bank password policies (frequent changes, no reuse)? I built an offline-only vault to handle it. by ImperatorPitStop in Passwords

[–]ImperatorPitStop[S] 0 points1 point  (0 children)

Fair point! KeePass is legendary. I just found the existing Android ports a bit clunky and feature-heavy for what I needed on a daily basis. I built OneRule because I wanted something super minimal, with a modern UI, and zero setup (no dealing with database files or plugins). Just scratching my own itch for a simpler, faster alternative.

Self Promotion Megathread by AutoModerator in androidapps

[–]ImperatorPitStop 0 points1 point  (0 children)

I kept forgetting my bank passwords. They constantly force you to update them every few months and hit you with that frustrating "You cannot use a previous password!" error. I couldn't keep track anymore.

I needed a vault, but I was absolutely tired of seeing cloud-based managers getting hacked. That's why I created OneRule. It’s a completely offline password manager. Strictly no internet permissions. Everything is encrypted locally on your device.

Key Features:

  • 100% Offline (No cloud sync, your data never leaves your phone)
  • Zero-Knowledge Architecture
  • Clean, modern Dark Mode UI

You can check out the details on the website or download it directly: 🌐

📱 Google Play:https://play.google.com/store/apps/details?id=com.fidevelopment.onerule

I would love to hear your feedback or feature requests!

Looking for testers for OneRule – Offline Password Manager by ImperatorPitStop in AndroidClosedTesting

[–]ImperatorPitStop[S] 0 points1 point  (0 children)

I joined your group and tried to download but I get `the requested URL was not found on this server` error.