Proposal: Overhauling Add-Ons and Shared Decks Pages

Anki Suggestions
1

I’ve now got more free time on my hands so if there’s enough community interest I’d consider investigating the possibility of also overhauling the Add-Ons and Shared Decks pages. I’m all for refactoring them and integrating them into the current landing page. Let me know your thoughts, and I’d also appreciate criticism of the current sites, ideally pain points and features you’re interested in. I’ll see what I can do.

3 Likes
2

Those areas of ankiweb are closed source, meaning you won’t be able to contribute to them.

I think dae mentioned that he plans to use it as a backup revenue plan, in case sales from the mobile iOS app dry out.

1 Like
3

The Landing page was also not available previously, I’m once again proposing a black box re-implementation. The front-end being open source doesn’t mean that the access couldn’t be restricted as required in the future if this was true.

1 Like
4

I have asked for open-source frontend before, dae’s response to that:

2 Likes
5

I’m only proposing to improve the shared decks add-ons pages as these display user provided content. This does not extend to the AnkiWeb platform as a whole - I respect dae’s reasoning and I would rather work on the Anki desktop UI if/when svelte makes its way there.

6

It would be best to divide the addons into categories such as: card editing, revision, management, appearance, statistics, import/export, gamification, developer tools, etc.
It would also be legal to know which addons are the most downloaded.

1 Like
7

If you decide to rework the add-ons page, consider developing an alternative ranking algorithm (dare I say, a better one?). The current system is quite frustrating for many developers, even though Dae has his reasons for sticking with it.

2 Likes
8

While I don’t object to the idea in principle provided you were working within the constraints of the existing backend API, I think it’s going to be a bit tricky in practice to implement and maintain this, if part of the frontend is being updated in a separate repo. Those endpoints are best hosted on ankiweb.net not apps.ankiweb.net, and some actions like searches/downloads impose lower limits on users who aren’t logged in.

2 Likes