title: QPython or Kivy for Android programming with Python - producing installable apk
body: <p>Having read several Q&amp;A's on SO, I realize that one has 2 options i.e. QPython and Kivy to do programming for Android, however, apparently both take different approaches. I am trying to validate my understanding and see if I am missing some key piece of information.</p>
  
  <ul>
  <li>QPython allows usage of Kivy library for developing graphical applications</li>
  <li>QPython and Kivy both use SL4A, while QPython has expanded standard SL4A (or it's bindings for Python) by adding some NFC and similar functions</li>
  <li>QPython is used to create python scripts that can use wide range of modules, libraries, but they need QPython installed to be executed on target device. There is no way to package script into an apk.</li>
  <li>Kivy OTOH, allows developer to write applications that compile to apk, using their cloud based build system (alternative - local build system can be set up on Ubuntu Linux) [<em>However, I noticed that most of the sample apk's that use Kivy are pretty large, in the 40MB range. Did I miss anything ?</em>]</li>
  <li>QPython apk has 2 version i.e. one for Python-2.7 and another one for Python-3.x. For Kivy, I'm not sure which version it is.</li>
  <li>QPython example script (HelloWorld.py) doesn't seem to behave as expected, from latest QPython-3.x from Market, on an Android Kitkat (4.4.2) system. I get the dialog to enter text, but then I expect a Toast to popup, but nothing happens.</li>
  <li>Get the impression that both QPython and Kivy are developed by a single developer each (or only one person is really active at present), and don't yet have a biggish community. [<em>This is my biggest concern</em>] I notice that there are 3-4 questions with 'qpython' tag on SO, and more than thousand with 'kivy'!</li>
  <li>Also get the impression that at this moment Kivy development is somewhat more active (perhaps quite active), but for QPython I don't have a clear picture.</li>
  <li>Kivy seems to be trying to expand the nature of application that could possibly be written using it, compare to QPython. There are API's like <a href="https://github.com/kivy/plyer" rel="noreferrer">plyer</a> and <a href="https://github.com/kivy/pyjnius" rel="noreferrer">pyjnius</a> that help expand the possibilities. Perhaps quite significantly, compared to QPython.</li>
  <li>Both QPython and Kivy seem to be heavily under development. Program (/ script) crashes (/ failures) seem to be reported on both set of tools.</li>
  </ul>
  
  <p>Overall, the opinion as a result (of above points) appears to swing in favour of Kivy, a bit more. Is the understanding correct ? Did I miss any crucial point ? This is not a rhetorical question, and I am looking for factual answers only.</p>