01
Python Foundations
Variables, loops, functions, and classes — covered through examples drawn directly from game logic rather than abstract exercises.
- Data types
- Control flow
- Functions
- OOP basics
Learning Program
.jpg)
Python mobile game development
A structured path from Python basics to a published Android game — built around sequential lectures, hands-on exercises, and real project work.
12wk
Program length
5+
Core modules
6h
Per week
1game
Final deliverable
Five modules — one complete game
Each module builds directly on the last. There are no standalone units — the game you start building in module two is the same one you ship in module five.
02
Kivy Setup and UI
Install Kivy, understand the widget tree, and build your first interactive screen with touch-responsive elements and a basic layout file.
- Widget tree
- KV language
- Layouts
- Touch events
03
Game Mechanics
Implement the core loop — movement, collision detection, scoring, and animation — using Kivy's Clock scheduler and Canvas instructions.
- Clock scheduler
- Collision logic
- Scoring system
- Sprite animation
04
Assets and Audio
Load sprites, tile maps, and sound effects into the application lifecycle. Manage memory carefully so the game runs smoothly on low-end Android devices.
- Image atlases
- SoundLoader
- Tile maps
- Memory limits
05
Android Deployment
Configure Buildozer, generate a signed APK, and test on a physical device. Optional: prepare a Play Store listing with screenshots and a description.
- Buildozer config
- APK signing
- Device testing
- Store listing
06
Project Review
Submit your completed game for structured feedback. The review covers code quality, game feel, and performance on the target device — not just whether it runs.
- Code review
- Performance audit
- UX feedback
- Next steps
Who teaches and what to expect
Two instructors share the program. Each brings a different background — one focused on Python architecture, the other on mobile product development. Lectures are pre-recorded and available on demand, with written feedback provided on submitted exercises.
Théodore Vanbremeersch
Python Architecture Lead
Covers modules 1 through 3. Has been writing Python professionally since 2011, with a focus on clean structure in small-team environments.
Solène Aubriet
Mobile Product Developer
Covers modules 4 and 5. Shipped six Android applications between 2017 and 2023, three of which used Kivy as the primary framework.
Format
All lectures are delivered as sequential video recordings. Each module contains between four and seven lectures, each under 20 minutes. Written summaries accompany every lecture so you can review key points without re-watching.
Exercises
Each module ends with a practical exercise that extends the game you are building. Exercises are submitted through the platform and reviewed within five working days. Feedback is written, specific, and references your actual code.
Prerequisites
No prior programming experience is required. You will need a computer that can run Python 3.10 or later and a willingness to spend time debugging — which is a normal part of the process, not a sign that something has gone wrong.
Do I need prior programming experience?
No prior experience is required. The program begins with Python fundamentals and builds incrementally. Students who already know Python basics typically move through the first module quickly and spend more time on the Kivy-specific content.
What tools will I need to install?
Python 3.10 or later, the Kivy library, and Buildozer for the deployment module. All tools are free and open source. A setup guide with exact commands is provided at the start of module one. Windows, macOS, and Linux are all supported.
Will I have a finished game at the end?
If you complete all modules and exercises, yes — you will have a packaged APK of a game you built yourself. The quality and complexity of that game depends on how much time and effort you put in during the project work sections.
Is the program self-paced or scheduled?
The lectures and exercises are fully self-paced. There are no live sessions or fixed deadlines. The 12-week estimate assumes roughly 6 hours of work per week — some students finish faster, others take longer.