u/MainEnd8636

Foster and kinship parents are asked to document a lot — visits, no-shows, contact attempts, meds, behavior, court dates, expenses — and most end up doing it on paper or in Notes. I built an app that keeps all of it on the device (no account, nothing uploaded) and exports a clean, dated PDF on demand.

I'd genuinely value input from workers here too: what does documentation look like from your side that a parent's app should make easier to hand over? I'm the developer and happy to adjust based on what actually helps a case move.

Taking in family comes with a mountain of paperwork you didn't sign up for — visits, appointments, school stuff, meds, and every expense you're hoping to get reimbursed. I couldn't find a tool that wasn't locked to a specific agency, so I made my own.

It keeps everything on your phone (no account, nothing uploaded) and turns any date range into a clean PDF for a caseworker or court in one tap, plus a CSV of expenses/mileage for taxes. It also tracks meds with reminders and logs calls/texts for when you're documenting contact.

I'm the developer, and honestly I want to know if this fits kinship situations specifically or if I've built it too "foster-agency" shaped. What's the most frustrating part of the record-keeping for you?

Between visits and no-shows, med logs, appointments, behavior notes, and mileage/expenses, I ended up with a binder plus three different Notes files and still couldn't find anything when a caseworker asked. Every app I tried was tied to a specific agency, so it was useless unless your agency adopted it.

So I built the thing I actually wanted. Everything stays on the phone — no account, nothing uploaded anywhere — and when someone needs documentation, one tap turns any date range into a clean, dated PDF (or a CSV of expenses/mileage for taxes). It tracks visits and no-shows, a communication log for when bio parents don't answer, court/custody dates with reminders, behavior/health/school notes with photos, and meds with reminders you clear by confirming the dose.

I'm the developer and I'm not trying to sell anything here — free tier is fully usable for 30 days. What I actually want to know: what's the most painful part of documentation for you, and is a private, agency-independent tool like this useful, or does your agency already cover it? Honest answers help me more than downloads.

**Unmineable-Mac is a native macOS GUI for the unMineable pool. It now

actually works on M3, M4, and M5 Macs.**

and

"Mining KawPow on a Mac actually works again (open-source, in-tree miner)"

If you remember trying it earlier and giving up because the GPU

hashrate looked fine but no shares ever got accepted on your worker —

that was a real bug, not your config. The bundled GPU miner

(`thinminerpro`) was a closed-source binary from 2022 that silently

fails to submit accepted shares on Apple Silicon M3 and newer.

That miner has been replaced in-tree with **kawpow-mac** — a

clean-room Swift + Metal rewrite. The new app:

- Mines CPU (XMRig / RandomX) and GPU (kawpow-mac / KawPow) — toggle

either or both

- Shows live hashrate and **accepted-share count per miner**

- Has an inline live-log panel so you can watch the stratum traffic

- Auto-detects the right miner binaries per architecture; the build

script clones + builds kawpow-mac for you

- Open-source end to end — no opaque blobs

Verified: the first share submitted by the new miner came back accepted

on the first try (against kp.unmineable.com on epoch 584). Pool

acceptance now works the same way it does on any other supported

hardware.

Caveat as always: mining on a Mac is not profitable. It's a "what can

this hardware do" exercise plus a salvage of a useful GUI for users

who already have the Macs.

Unmineable-Mac

(https://github.com/shiftingeden/Unmineable-Mac)

Bug chronicle (5 separate algorithmic bugs, with the diagnostic for

each): [BUGS_AND_FIXES.md](https://github.com/shiftingeden/kawpow-mac/blob/main/BUGS\_AND\_FIXES.md)