The Quest for the Pocket-Sized Python
summary
State of the claim: full native apps in Python remain awkward — packaging a Kivy app adds about 6 MB and has a nontrivial startup cost, and pure-Java/Objective‑C APIs don’t map cleanly to Python. Practical paths that actually work: make mobile web backends that expose compact, idempotent APIs and give each client state a unique URI so wrappers can restore exact screens, or use Kivy for games and custom UIs while using pyjnius/pyobjus to access Android/iOS hardware. Hybrid apps with Python core and native UI layer prove the most reliable.
AI-written summary · about
chapters (37)
- 0:00Intro
- 1:23The Land That Python Forgot
- 2:35Todays Talk
- 3:47Recap
- 4:34Pocket PC
- 5:43Touch Screens
- 6:07Keyboards
- 6:49App Stores
- 7:20Python
- 7:33iOS
- 8:28Swift
- 9:15Android
- 11:10Take Home Message
- 12:21Design Standards
- 12:57Commercialization
- 13:28Summary
- 13:44Web
- 15:01Touch
- 17:01Hands
- 17:35Responsive Design
- 19:28Accessibility
- 23:08PhoneGap
- 24:07Python Apps
- 24:47Kivi
- 25:31What is Kivi
- 26:13What Kivi doesnt let you do
- 27:48Hardware APIs
- 28:10Pygenius
- 29:26Player
- 30:27Native UI
- 30:53Android UI
- 31:37Python Framework
- 32:27Hybrid Approaches
- 32:47Web Services
- 34:55Hybrid App
- 36:18Conclusion
- 37:08Questions
related talks
30mThe Quest for the Pocket-Sized Python
33mPython on your phone: Building mobile apps with Kivy
29mKivy: Pythonistas can develop cross-platform (yes, even mobile) GUI Apps
31mPython on the move: The state of mobile Python
29mDeploy to Android: Adventures of a Hobbyist
53mPython All the Things
30mExploring Kivy in the classroom - GUI and App development for Python
32mCovered in Bees! Deploying an app to 6 platforms in 20 minutes