The main problem with all of this is that you've done no research to validate your 'problems'.

Start with research, prototype, iterate etc...

You've basically taken what YOU see as problems and changed things round without testing anything with users.

Yup

The joke didn't work because it was inaccurate. Woe betide anyone who critique's something on here right?

Surely the MVP of a chair would be a cushion/pad to sit on as that is the main purpose of a chair... to be sat on.

The V stands for Viable... a stick is not a Viable MVP of a chair.

/rant

Looks interesting. A few questions

• Does this handle responsive design? as in components that can interact and respond to one another dependant upon screen size.
• Does it have advanced typography settings?
• What about colour management?
• Are prototypes ran from the app or are they able to be shared publicly?

If they slowed down the time between the transitions it would work much nicer, don't have to time take things in visually.

In your first flow, items 2, 3 and 4 are entirely subjective.

2. Recall which email address they used Hardly, they just typed it into the forgot password field

3 and 4, you’re assuming a lot of things here. You’re assuming that they use a browser to view their email and you’re also assuming that if they do then they won’t have it bookmarked or already open. The reason you’re doing this is to give credence to your theory and push your answer.

As for your solution, it wouldn’t work in the majority of cases… How are you going to determine how someone accesses their email? By the domain? Wrong, just because someone has a Gmail or a Yahoo account that doesn’t mean they use the web interface to access them. If you tried to direct me to Gmail’s site when I use Mailbox to access my gmail account I’d be pretty annoyed.

http://plonsdale.vsco.co/

Looks fantastic, looking forward to trying it.

Any ideas on how soon it will be released?

Just don't view the source... eek