|
|
|
|
|
|
by robgough
15 days ago
|
|
|
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. |
|
|
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 :)