@stevimigaku I think the point that OP is trying to make is that Migaku seems to be heading down a route of making its own SRS which has seemingly sucked resources away from refining the existing Migaku product. Community engagement seems pretty low and turnaround times to get an actual response from the dev team seems like forever (devs literally respond after months). People have had concerns about the future of Anki support for a while and it hasn't really been addressed. In fact, nobody can even see the roadmap anymore because the content is being blocked when trying to render in an iFrame due to a site error (the direct link to the Trello page can be found here for anyone interested btw.
For a lot of people Anki is just too much to get into and our SRS will allow those people to get the same benefits but with less hassle.
This statement is potentially true in isolation, but how true is it for your customer base? Have you asked your community whether or not they'd prefer a Migaku-specific solution over Anki? I have a sneaking suspicion that most of your community belongs to a demographic that has no problem using Anki would not want to use a new SRS since switching between SRS tools has a pretty steep cost associated. Additionally, most SRS-as-a-service offerings lock you into their system so that you don't switch back to things like Anki.
OP raised a valid point when they asked whether or not you've even asked your customers what they want. You mentioned that all the ideas you have for improving the SRS experience aren't doable in Anki, but nobody here even knows what those ideas are. You have people that have paid for an existing product under the impression that it would be a part of the Anki ecosystem long-term and yet the funding is going to things people didn't ask for rather than the things that people paid for.
Looking at the roadmap with the direct link I provided above there is not a single mention of the word Anki. Most of the focus seems to be directed towards developing new things rather than improving the existing ones. Given that there is a slow dev-response time and that updates take seemingly forever, it calls into question how the team will be able to support all of the existing stuff as well as the new stuff given that the dev team seems very small, stretched thin, and likely working on this project out of passion in their part time rather than as a full-time job.