[Barbing]

Oh yeah, this one’s worth hyperlinking

https://dictator.robgough.net

Great work Rob! Indeed private as promised per App Privacy Report, “Domains contacted directly by app”:

  cas-bridge.xethub.hf.co; huggingface.co; mzstorekit.itunes.apple.com

Site could identify our device and send iOS visitors to the iOS page (or maybe that’s against the vibe and we should tap it ourselves).

App might be able to launch the keyboard settings directly but I suppose Apple doesn’t like devs using those undocumented URIs (uhg but maybe can understand part of it).

Keyboard, given manual app switchbacking + manual pasting, is less convenient for some of my use cases compared to an action button shortcut. (Reference Spokenly w/Local-Only Mode.)

Separating dictation and the history, and having a syncable scratch pad, are some welcome innovations!

>Gemma E4B … takes up 6-7GB RAM.

Google has a spyware-adjacent dictation app (maybe not really, but they demand to connect to servers after you enable their offline toggle). Just like yours, they thought of a cute name too (Google AI Edge Eloquent). Do you know what language model they install on the iPhone? Not a very good one but I’m sure over the next year or two…

[robgough]

I appreciate the kind words. Thank you.

I really wanted to have background audio and make it so the keyboard would directly record audio etc, but my first pass didn't make it through app review (and that was just keeping background audio listening AFTER you'd already started a recording). I could maybe have fought it, but figured if I was already butting up against app review there was little point as they'd likely reject in a future release anyway.

Re: analytics, It is quite weird having no idea how many people are using the app. It does leave you a little blind, but I figure people will get in touch if they have big enough problems with it.

For the Google app, I believe Gemma E2B and E4B both have audio input, so I suspect they're using one of those.

[Barbing]

Analytics: if you generate them on my device, and bury an option to manually send them to you when I have a bug--or...

you instead bury an opt-in to automatic telemetry, and let us CC ourselves each ~month when the analytics get sent in to you (so we can verify it's all boring data)...

It's hard for me not to opt in to stuff like that, at least periodically. If I'm opted-in by default? Ehhhhh.... I totally get it, weird "flying blind" (quoting a different dev w/similar philosophy), but I guess I'm still weird myself and hence looking for that autonomy or something? Oh and if somebody makes something opt in, and then certainly if they furthermore stick the option somewhere slightly off the beaten path, that seems pretty darn trustworthy.

(I wonder if we'd have enough public data for a decent statistician to calculate a likely number range of how many users you have by extrapolating from the 1% to 10% or 20% of users who'd chose to opt in...)

PS: "bury" concept likely not actually important :)