Live data from Hacker News

Python on Android

kivy.org

31–40 of 51 posts

Re: Python on Android

#32
post #16
post #7

So, I've actually been working for the past while on a project to allow building more native apps on Android using Python. It is built on the Kivy tools, but I have had to make some changes to python-for-android specifically because it's not as seperated from Kivy as the developers think. I've also had to make a small change to PyJNIus, as it has a dependency on SDL when on Android. The reason I chose to work on this…

Good god, here's a Kickstarter I'd get behind.

Yes, grandparent, please consider this :)

Re: Python on Android

#33
Kivy is a fun little library, not without its quirks, but overall I felt comfortable with it.

In particular, it's nice how they built everything around GLSL shaders, this allows for very interesting styling and visual effects.

Also personally I found that the easiest way of getting into Kivy is by dissecting someone else's toy projects. E.g. there is this book with many small programs written in Python with Kivy: https://www.packtpub.com/application-development/kivy-bluepr... -- it's an OK foundation. (You don't have to get the actual book, the source code is here: https://github.com/mvasilkov/kb)

Re: Python on Android

#34

Kivy is really cool, but getting started on it sort of sucks. Lots of compilation errors (especially if you're trying to install on windows) due to its dependencies on pygame (and therefore cython, and therefore a particular version of MSVS for the specific dll... all a hassle). The on-site tutorials are sort of obtuse too, if you're looking to do UIs rather than games - until other resources[1][2] became available,…

I've never used Kivy, but I'm using Vagrant (https://www.vagrantup.com/) on a daily basis for development and it made all problems with setting up the dev environment the thing of the past for me. I've found something like this for Kivy: https://github.com/Peradine/kivy-android-vagrant it's been 2 years since last commit, but it can be a starting point.

There's also a Dockerfile (http://docker.com/): https://github.com/timlinux/docker-kivy which also can be used in this case (but personally I like Vagrant more for such use case).

Re: Python on Android

#35
post #6

Is kivy production ready ?

kivy is a lot better than it was 6 months ago - i like it

I think I tried it maybe 2 years ago (I think) and back then it really bothered me how big the resulting APKs were. Now, I think, most people don't even care anymore.

Re: Python on Android

#36

I would much rather Google focus on Python than Dart for Android.

Google does not seem to focus on Dart either, it is just an experiment from the Dart team.

I am curious though, why do you think that Python would be a better match for the platform ?

Re: Python on Android

#38
post #26

OT: > the unimaginatively-named python-for-android project. I love that name. Much better than the "imaginatively" named grunt, travis, react, kivy, vagrant, etc.

I teach intro CS to non-majors, and having to explain terminology is cumbersome. For instance, we call things "strings", "floats", and "dictionaries". And then I make them download Anaconda so they can get Spyder to write Python programs. I can't help but wonder what goes through their heads.

Isn't "map" the proper CS term rather than a dictionary?

Re: Python on Android

#39

I would much rather Google focus on Python than Dart for Android.

Scala on Android seems promising.

There are also lesser known alternatives such as Kotlin (by JetBrains), and you can use Groovy too.

There's a very nice testing framework in Groovy, by the way: https://code.google.com/p/spock/ - and you reportedly you can use it on Android too (I didn't try it myself yet): https://github.com/pieces029/android-spock

Re: Python on Android

#40
post #20

I would much rather Google focus on Python than Dart for Android.

Too bad google suffers from a NIH syndrome.

As evidenced by using Java in the first place, and considering C# for Android at one time ("If Sun doesn’t want to work with us, we have two options: 1) Abandon our work and adopt MSFT CLR VM and C# language, or 2) Do Java anyway and defend our decision, perhaps making enemies along the way")?

Or choosing Groovy-based Gradle as the main build system for Android?

Or not integrating Dart VM into Chrome?

Unlike Microsoft in their evil era - their policy has changed a lot since - they don't seem to be pushing forward their own standards and inventions at all costs, they seem very pragmatic about it.

Post reply on HN