I hope you do not mind if I split in two your comment.
Starting with "simple" stuff
I think that without the log-in process your users were not able to fully understand the goal of the test
I agree, as you said, it looks like a complex journey and there's a lot of stuff to read and learn
I agree, IMO, screenshots displayed in a static way are not engaging
I can give you an example according my experience.
For our platform (responsive and native), often, we release new features and to attract user focus we decided to use the progressive disclosure.
For example the new QR code payment functionality with the.
We decided to deliver the short tutorial only if you browse the pay section. The CTA of the feature has a "new" label and if you click/tap on it, for the first time, you receive a dialog with a brief description of the functionality.
The user is always in control and she/he can decide whether to keep the suggestion appears again or dismiss it putting check the option "I understand, do not show again."
After many tests (both qualitative and quantitative), we noticed that the so-called "content on the go" is much less invasive and useful to users because it provides a specific piece of information when this is necessary to them to complete the task.
We decided to implement the feature starting with this JS library: http://introjs.com/
I don't remember how we delivered the same in the native environments, if you're interested in I can ask some developers.