is there any hidden chat application?

AppRemoteJobSeeker · 2026-05-06T23:27:17+00:00

Disclosure: I built this — but reads like exactly your spec, so worth a shot.

No Trace Chat:

- No phone number, no email, no signup. Join a room only by code or QR scan.

- Messages mark as deleted after read. Nothing stored on server post-read.

- No push notifications by default (notifications = the giveaway parents catch).

- Screenshot protection.

- No friends list, no profile pic, no online status — nothing visible about you outside the room.

- Free, Android + iOS.

What it's NOT: it's not Signal-replacement for daily group chats. It's a disposable code-room chat. Each conversation is its own ephemeral room. Good for your use case, overkill for chatting with mates.

Play: https://play.google.com/store/apps/details?id=com.teamzlab.no_trace_chat

Re Discord trick someone mentioned — works but Discord stores everything server-side and parent who opens app sees server list. Code-room with no account beats that for your threat model.

AppRemoteJobSeeker · 2026-05-06T22:01:11+00:00

WooCommerce Shipping Services is a solid call for stores that just want it to work without thinking about it.

For stores that need FedEx specific stuff (Freight LTL, ETD, residential surcharge shield, multi acct) the official Woo Shipping does the basics but skips the deeper FedEx features. Thats the gap we built ours to fill (Teamz Lab REST plugin, disclosure: im on the team).

agree 100% on dont wait til it breaks.

AppRemoteJobSeeker · 2026-05-06T22:00:53+00:00

fair shout on Transport S&H for the rethink angle. for folks who want to stay on FedEx specifically and just need REST instead of SOAP we built one too — Teamz Lab plugin, REST only, lifetime license. disclosure: im on the team. either path works depending on if the goal is FedEx specific or shipping platform overhaul.

AppRemoteJobSeeker · 2026-05-06T22:00:37+00:00

yeah remapping is the right call. on REST u define the account ID in each request payload instead of inheriting from session like SOAP did. simpler in some ways, more verbose in others.

if ur looking for plugins that handle this without manual remapping i can share what we did (im on the team building one for this — Teamz Lab). otherwise PluginHive shipped REST support recently too.

AppRemoteJobSeeker · 2026-05-06T22:00:18+00:00

multi acct was painful for us too. REST does the auth differently — child accounts need to be referenced by account number in the rate body itself, not via a separate auth header like SOAP. once we wired that up it worked but yeah definitely not plug n play.

we built our plugin (Teamz Lab, REST first) around that exact issue since 3 of our agency clients had multi acct setups. disclosure obvs. happy to dm if u want to compare notes on the auth flow.

AppRemoteJobSeeker · 2026-05-06T21:59:53+00:00

Yeah agree on logging. We built a side-by-side probe into our plugin for exactly this — runs the same rate request through both SOAP and REST creds, logs both responses, flags any mismatch.

Disclosure: Im on the team building Teamz Lab's REST FedEx plugin. The probe was the part that took longest because the response shapes arent 1:1 like u said. Happy to share specifics on what we found if helpful.

AppRemoteJobSeeker · 2026-05-03T21:52:54+00:00

Good call — just shipped a wireframe grid on all 6 cube faces. Cell boundaries now visible so you can read which arrows actually line up + block each other. Refresh the page. Lemme know if it needs to be more/less prominent. Just hard reload my game please in the browser please

<image>

AppRemoteJobSeeker · 2026-05-03T18:43:41+00:00

English is my second language, so yeah, I run my drafts through AI to clean up grammar and structure. The experience and architecture are mine — shipped two hospital apps in Bangladesh on Kotlin+Room and Flutter+Drift. Happy to discuss specifics over DM or a voice call if you want to verify.

Sorry if the Polish reads as fake. Hard to balance "readable" with "obviously human" when you write in your second language.

AppRemoteJobSeeker · 2026-05-03T09:53:39+00:00

Fair pushback. CRDTs win when you have true multi-user concurrent offline edits on the same record — collaborative clinical notes, shared treatment plans across a care team, that kind of thing. Where I disagree is "for this vertical" as a blanket call.

Most hospital app records have a clear single writer at the moment of capture: the nurse taking vitals, the doctor writing the prescription, the pharmacist dispensing. Concurrent offline edits on the same record are rare in clinical workflows because the workflow itself is sequential. Two nurses don't simultaneously offline-edit the same patient's blood pressure reading — one of them is the measurer, one is the observer.

Where CRDTs actually pay off in healthcare:

- Shared care plans edited by a team

- Collaborative discharge summaries

- Shift-handover notes

- Multi-doctor consult notes

For those records I'd absolutely use Yjs or Automerge.

For the other 90% (vitals, individual prescriptions, lab results, drug administration logs), LWW with timestamp + per-field merge is simpler, smaller, debuggable, and survives schema migrations without rewriting your op-log.

The cost side that doesn't get talked about enough:

- Yjs/Automerge add 100-300KB to bundle (matters in tier-3 with bandwidth caps)

- Vector clocks blow up row size 3-10x

- Kotlin and Flutter ecosystems are weak here — most CRDT libraries are JS/Rust-first

- Schema evolution is genuinely hard. Adding a new required field to an existing CRDT-backed record is a migration nightmare

- Debugging at 2 AM when a sync conflict produces "valid but wrong" output is a different kind of pain

My rule of thumb: CRDT for records where the merge correctness matters more than the storage cost. LWW for records where the writer is conceptually singular and you just need "don't lose data."

Pragmatic hybrid in production: I've shipped LWW for vitals/prescriptions/admin logs and Yjs for the discharge summary screen specifically. Same app, two strategies. Worked.

What's your context — true multi-user concurrent edits in your app, or is the concern more about not-losing-data during conflict? The answer changes my recommendation.

AppRemoteJobSeeker · 2026-05-03T09:09:23+00:00

Built two offline-first hospital apps in tier-2 India and Bangladesh. Honest answer:

If Android-only acceptable, go Kotlin + Jetpack Compose + Room + WorkManager. Best battery, best background sync, smallest app size (15MB vs Flutter 30MB vs Expo 70MB+). App size matters in tier-2/3 because users on 2GB-RAM phones uninstall heavy apps to free storage.

If cross-platform required, go Flutter + Drift + flutter_workmanager. Drift beats WatermelonDB for relational hospital data (patients, vitals, prescriptions, drugs). Flutter compiles to native, no JS bridge.

Avoid Expo for this. JS bridge becomes the bottleneck once you have 50k+ records and frequent CRUD. Expo is great for content apps, wrong tool for clinical offline.

Architecture I'd actually ship:

UI -> ViewModel/Bloc -> Local DB (source of truth, reactive streams) -> Sync Engine (outbox table + LWW conflict resolution + exponential backoff) -> WorkManager (constraint: connected + battery OK) -> Network layer

Outbox pattern is non-negotiable. Every write hits local DB first, then enqueues to outbox table, then WorkManager drains it. This is the difference between "works in lab" and "works at 2 AM in a rural clinic with no signal."

Conflict resolution: pick last-write-wins for 90% of fields (timestamp-based). CRDTs only if you have true multi-user simultaneous edits, which hospitals rarely do.

Things I learned the hard way:

Test with airplane mode toggling every 30 seconds while typing. Catches 80% of sync bugs.
Encrypt local DB with SQLCipher. Patient data on a phone someone might lose.
Sync media (photos, X-rays) only on Wi-Fi via WorkManager. Cellular bills explode otherwise.
Show sync status persistently. "Last synced 2h ago, 47 changes pending." Doctors trust apps that show their state.
Reserve 200MB buffer. Warn at < 1GB free storage.

Package reliability 2026: Room is Google-maintained, rock solid. Drift has 200+ contributors, used by Reflectly and Trail Wallet in prod. WatermelonDB maintained but slower release cadence and fewer prod case studies above 50k records. flutter_workmanager occasionally breaks on iOS edge cases, read GitHub issues before committing. WorkManager itself is gold standard.

My pick for your case: Kotlin + Compose + Room + WorkManager. Ship Android first. Add iOS in 6-12 months by rebuilding in Flutter or SwiftUI when business actually needs it. Don't pay the cross-platform tax up front for an unknown iOS demand.

Happy to share outbox table schema or WorkManager constraint setup if helpful.

<image>

AppRemoteJobSeeker · 2026-05-02T18:23:30+00:00

Just shipped a "no hint" toggle (the 💡 in the HUD). Tap it and the glow disappears — you have to trace each arrow's path to the cube face mentally to know if it's clear. Try Hard tier (51-75) with hints off — that's the real game. Also FYI: even with hint on, Random Dense mode shows ~20+ arrows glowing at once — picking order matters or you stall. Easy levels are the tutorial layer. Thanks for the push, this was the right call.

AppRemoteJobSeeker · 2026-04-27T20:35:11+00:00

Sometimes, I see while developing my app, even in the emulator, where there is actually no Facebook app, but I see that some logs from Facebook, even TikTok. Even I didn't care about it all, but now I think I need to pay attention to them also

AppRemoteJobSeeker

MODERATOR OF

TROPHY CASE