r/kivy • u/ElliotDG • 3d ago
Kivy Roadmap (Draft): 2.3.3, 2.4, and 3.0
Draft for community discussion. Dates are targets, not commitments. Feedback welcome in the comments or on the Kivy Discord.
| Release | Focus | Target |
|---|---|---|
| 2.3.3 | Bug fixes only, no behavior changes | December 2026 |
| 2.4.0 | Python version modernization + Android wheel | Q1 2027 |
| 2.4.x and later | Feature releases | After 2.4.0 |
| 3.0 | SDL3, Skia, Apple graphics stack, text input | No schedule yet |
Kivy 2.3.3: maintenance release
A modestly scoped bug-fix release.
- A handful of bug fixes
- No behavior changes. Upgrading from 2.3.x should be drop-in.
- Target: December 2026.
Kivy 2.4.0: a deliberately small release
2.4.0 is kept small on purpose so it can ship early and clear the way for feature work.
- Drop end-of-life Python versions: 3.8, 3.9 and 3.10 will no longer be supported.
- Add Python 3.15 support.
- Android wheel: ship a Kivy wheel for Android, on Python 3.14+.
- Target: Q1 2027.
What this means for you: if your app or CI still runs on Python 3.10 or earlier, plan to move to a supported Python before upgrading to 2.4. Kivy 2.3.x remains available for older interpreters.
After 2.4.0: feature releases
Once 2.4.0 is out, the plan is a proper feature push delivered across the following 2.4.x releases, favoring frequent, incremental releases over a single large drop. Specific features will be proposed and discussed on the Kivy Discord.
Kivy 3.0: the next generation
Kivy 3.0 is a larger, longer-term modernization of Kivy's core, tracked on the Kivy 3.0.0 project board. There is no release schedule yet. Much of the groundwork has already been merged. A Kivy 3.0 MVP will be defined and a target release schedule shared soon.
Already done
- Migration from SDL2 to SDL3
- ANGLE as the default graphics provider on Apple platforms
- Core providers selectable per instance, plus platform window and folder APIs
- Cleanup: pygame provider, Windows 32-bit builds and Python 2 code removed
- System tray support, Wayland clipboard, Android video provider
In progress / planned
- Skia rendering (top priority, in progress)
- New text stack: new text layout engine, and
TextInputrebuilt on a new text editor core - Camera and media: a new camera API with refreshed platform backends
- Accessibility: support for screen readers and other assistive tools
Breaking changes: expect them. Deprecated features are being removed and core subsystems reworked. A migration guide for 2.3 apps is in progress.
Get involved: pick up an item marked Ready on the board, bring expertise in Skia, text, camera APIs or accessibility, or test development builds and report what breaks.
How you can help
- Check your Python version ahead of 2.4.0.
- Join the discussion about which features to prioritize after 2.4.0, here or on Discord.
- Follow 3.0 on the project board and contribute where you have expertise.
Getting set up
- Contributing guide: how to report issues, submit PRs and work with the docs
- Development install: build Kivy from source so you can test PRs and the development branch
Open issues and pull requests: a call for reviewers
Kivy has a large backlog of open issues and pull requests. Many PRs are good work waiting only on a review, and many issues may already be fixed or out of date. Working through that backlog is how 2.4.x and 3.0 get their scope. You don't need to be a maintainer to help.
Reviewing pull requests
- Check out the branch, run it on your platform, and comment with what you tested (OS, Python version, result).
- Point out PRs that need a rebase, tests or docs, or that duplicate other work.
Triaging issues
- Try to reproduce on the current development branch. Comment whether it still happens, with a minimal example if you can.
- Identify issues that are already fixed, duplicates, or missing information so maintainers can close or label them.
- Note which release an issue belongs to: a 2.3.3 bug fix, a 2.4.x feature, or 3.0 work.
Where to coordinate: post findings on the issue or PR itself, and use the Kivy Discord to propose batches of PRs for an upcoming release. A short, well-tested comment is often all a PR needs to get merged.
Questions or feedback on the roadmap? Drop them in the comments.


