I'm hopeful, while simultaneously ready to be disappointed.
The good news is they seem to be taking mobile more seriously now. I hope they reveal something better than their adaptive-view system, which becomes absolute chaos unless you have the contents of every breakpoint of the design mapped out in advance: the opposite of agile. Even so, none of it will matter if performance is (still) anemic on a phone. Competitors create prototypes that feel almost native, response-wise.
Axure is weakest compared to competitors on animation. I'm talking about performance, yes, but more directly about Axure's having no intelligence of when it should cancel/adjust an animation. Specifically, when a new animation is applied to a widget property that is currently animating. Example:
Make an animated accordion in Axure where only one child opens at a time. You can't without it completely devolving if you act upon it while any of its member's properties is animating. Because that currently animating property's endpoint is irrevocably fixed in time and space; a new animation on that same property has to wait (and will start in the wrong position), even though it's supposed to happen now. Meanwhile, Framer handles this automagically, at 60 frames per second. But Framer is hardly rapid prototyping. It's more like rapid programming.
This might seem like a nit to those new to Axure (and perhaps to its product owners), but if you are a motion desiger, or if you need a bullet-proof prototype, this is a rough one.
In my case, it's a big limitation because the prototype can't break while it's in a user test. This makes me anxious since "overall impression" is part of the score.