Hello, Guido.
First, it seems that a number of your useful feedbacks were still in the queue of items to be processed for our development team. Sorry, I know that's probably a little frustrating (and it is for me, too), but I'm pushing your items to the top of the queue. Some specific comments based upon about an hour's time spent looking at your various notebooks:
- There are definitely bugs and missing implementation issues here. One of the big things missing is the slideshow experience, as you've no doubt observed.
- There was some kernel functionality which was accidentally missing related to Entity frameworks. That should be fixed in the next beta.
- Some of the problems you experience have to do with the fact that your Manipulates are computationally intensive, which can cause two kinds of problems.
- First, iOS devices do not have storage-backed virtual memory like traditional desktop devices. If you use too much memory, iOS simply kills your app. We try very hard to be conservative about memory usage, but the problem with exposing the full Wolfram Language is, of course, that you can choose to very easily allocate a ton of memory in your code.
- Second, the A8/A9/A10 processors, while being extremely capable mobile processors, simply don't hold a candle to desktop CPUs for raw computational power. Some of your Manipulates are slow even on the desktop (which I noticed on my Mac Pro!), and these are likely to be killed by the
TimeConstrained
that we wrap around all synchronous Dynamics.
- Also, related to the above, the beta doesn't support asynchronous Dynamics. It simply runs them as if they were synchronous (we might not be able to fix this in time for the initial v1 release).
Ultimately, notebooks will have to be tailored to be computationally lightweight. There's just no avoiding that as long as the computation is local. Apple devices are a moving target, of course, so "computationally lightweight" isn't something I can give a fixed definition.
As for various other features, we are re-creating 25 years of development, so there will be some holes. I appreciate your patience, and please keep reporting the things that you find.