I underestimated the work it would take to learn Haskell, deal with marginal support for iOS in Haskell, and the difficulty in redefining computing languages as well as spreadsheets.
In 1991, I significantly moved the state of the art for spreadsheets with Mesa. I figured if I could do it once, I could do it again. But... this time, I've got kids so I can't go into a fugue state for a week and come up with an approach nobody has ever thought of... I have to turn into a dad each night. That makes the problem harder. This time, my brain thinks differently and have many more ingrained thought patterns that make thinking "outside the box" more difficult. This time, I'm working with a language (Haskell) that's an order of magnitude more different than Scala than Objective-C was to C.
Put another way, I'm trying to do something that no ACM fellow, no university professor, no industry lab has been able to and do it in a way that's also usable and comprehensible to people who don't self-identify as computer programmers. It's one of the tallest mountains in computing. I was hoping to scale it in a year... but maybe it'll take 2 or 3... I've got time.
This is not an "adoption" issue (I've had plenty of offers to use Visi once it meets certain goals.) This is a "I'm going where nobody has gone in computer languages, ever," problem. Basically, every computer language we use today is some decedent of Lisp, Fortran, and VisiCalc. Trying to think outside those boxes and at the same time, defining a usable type system that allows expressions that even the most advanced research is just starting to think about (algebraic type transformations), is really darned hard.
Telling me that the web site is ugly and maybe that's the problem I should be solving doesn't help.