(this is just a draft, to be completed "some time in the near future")

Common Lisp and QML on Mobile

* EQL5 desktop
  - you'll need it if you want to develop the app on the desktop first (acting
    as your 'instant/interactive simulator')

  - one of the neatest experiences for developing any UI, considering
    interactive development
  - (a few lines of) JS glue code needed in some situations

* Interactive development -- both Lisp and QML -- directly on the device
  - usual Lisp REPL (Slime)
  - reload QML (reloads all UI files, images etc.)
  - interactively get and set QML properties, call QML functions, call JS
    (glue code) functions

* EQL5-Android
  - more developer freedom than with iOS, but also more troublesome regarding
    possible issues on different devices
  - C level debugging possible, but a little complicated to set up
  - no Android Studio needed (thanks God!)
  - never tried to run in simulator (both desktop and real device work well

* EQL5-iOS
  - specific issues to get things to work in some special use cases (but
    workarounds are easy, if you know Qt)
  - environment setup much simpler, C level debugging trivial to do (through
  - no Xcode needed (thanks God!), except for deployment
  - running in simulator needs another round of cross-compiling both ECL and
    EQL5 (can be done, but tedious to build)

* Cross-compiling ASDF systems for arm
  - if we use the byte-codes compiler as a fast meta-step, it becomes trivially
    easy (see 'make.lisp' in e.g. REPL example)

* Monetizing: in-app purchases and subscriptions
  - in-app purchases already integrated in QML
  - subscriptions require a 3rd party library, which in turn requires 
    integrating with either Java or Objective-C