Anki-Android

ankidroid/Anki-Android

AnkiDroid: Anki flashcards on Android. Your secret trick to achieve superhuman information retention.

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 3, 2026
today
Ship score
100/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 11,586 → 11,876 (Aug 18 – Sep 29, 2026)
+220 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
11.9K
Forks
2.9K
Open issues
350
Watchers
152
Primary language
Kotlin
Created
Jan 20, 2013
Owner
ankidroid · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 6 startups in the directory ship primarily in Kotlin.

Topics

#android#anki#ankidroid#education#flashcards#kotlin#learning#srs

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose something else instead, and put os_startup at 24% (self-hostable 6%, hosted offering 25%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-03This is the badge for ankidroid/Anki-Android, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/ankidroid/Anki-Android.svg)](https://ossean.com/ankidroid/Anki-Android)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.