Okay, that clears it up . I’ll put you down as a “prefer to keep as-is” then. Since I don’t care either way on this particular issue I hope we’ll get some more opinions before I lock it in one way or another. Plus, it can always become yet-another-setting.
When I launched FD I deliberately didn’t include any analytics since I respect people’s privacy, but I’m starting to occasionally wonder how many features in the app are used by just one or two people… With fewer than 500 users in total and dozens of settings, there must be a couple of those.
I’m pretty privacy conscious myself and usually opt out given the opportunity. However I absolutely see the value in having analytics as well, especially in cases like figuring out crashes and configurations.
If you do decide on adding some analytics I suggest that perhaps you make it an option to opt-out which would satisfy most people I think, and having it an opt-out rather than an opt-in makes it so that most people that don’t care as much would probably leave it on. Adding a small snippet that says “no personally identifiable information is collected, your help is appreciated” or something to that effect would probably also help (if that’s the case, where you’re more interested in usage analytics).
Yeah, if you want usage statistics you kinda need opt-out, opt-in will usually give a skewed result.
I see, I’m not familiar with how stringent Google is with developers following all of the regulations but it makes sense you’d want to do it properly or not at all. (programmers and their documentation, right )
I think it should work pretty much like it currently does
I like to deal with meaning and reading together and I don’t want to retry X items later if I get either of them wrong. I just want to immediately correct my mistake and move onto the next item. The current implementation is therefore great for me.
I also use meaning-first, but purely to prevent this sort of thing happening:
FD asks for the meaning.
I get the meaning wrong.
FD asks for the reading (but my brain wants / expects the meaning again to correct it)
I realise I’m probably in a very small minority with the desire to “correct” immediately, but it works for me
That button is turned off by default, but the good news is you can set it to on while doing reviews and can then still ignore that.
You have to click on the three dots in the upper right corner to open the drop down menu, and the click ‘settings’, then scroll down to advanced settings and enable them. Then you can go to ‘other advanced settings’ and enable the ignore or undo button.
You have to be a bit careful there which function you assign it. You could theoretically also assign the undo function to it, which means the review would go back into the queue. Ignore acts as if you got it right.
You’ll have to wait for the audio download background tasks to complete, you’ll see those displayed on the main screen. Also make sure to select the Settings > Audio Settings > Voice preference to “Random”. After that, choose “Sync now” from the main menu again.