I agree Suggestion: ExtensionKit as next gen replacement for URL schemes is the better solution, with the assumption the new api could be enabled via a callback, so apps could prompt the user to enable it, instead of instructing them, which is a big UX hurdle.
I just want a working system for duplicate checks which doesn’t rely on tedious callbacks, and is instant.
My solution can have desyncing and could require manual syncs of “target word”’s by the user, but should reduce the rate users click “add card” just to see they already had a card made which is a horrible user experience. Or users not wanting to mine words due to the fatigue of it failing enough.
From my understanding your suggestion would remove callbacks all together (if it requires users hitting a flag to enable the api and I can’t use a callback to prompt the user to enable it, your proposal would be a deal breaker for me, but I assume adding a callback for it shouldn’t be the worse)
My concern though is it has been almost 3 years and that proposal isn’t avaliable. If it could be implemented in a reasonable timeframe (not years again, hopefully within this quarter or less), than I am more then happy. I am assuming my callback proposal is less then 100 lines and would 100x UX for mining on iOS, greatly reduce the about of callbacks a user makes, which inturn greatly reduce the fatigue of mining on iOS.
I just want a real solution to happen, because right now mining on iOS sucks. Duplicate checks (before adding a card) is insanely important for UX.
I would prefer your solution (with callback to enable API), but if we got my proposal in I would be insanely happy as it would provide such a better experience for Language Learners than what is avaliable on iOS today. I assume my proposal is less work, but I just want a solution at this point. Whether it is optimal UX or a massive UX increase, the current experience is painful. I just want a win.