As a dev, I implemented something similar. And I can't speak for TaskEasy but mine wasn't on purpose. Really complex process made simple: 1. Start out with an

As a dev, I implemented something similar. And I can't speak for TaskEasy but mine wasn't on purpose. Really complex process made simple: 1. Start out with an email transaction that follows up purchases done in the MVP to registered users. All that receive the emails have accounts since the MVP required it. It's not hard to setup automatic emails through code... It's hard to think of edge cases though. 2. Change in spec: more people buy if we change the UX and cut the registration. 3. Send an email to the customer. Oops - no account to unregister. 4. (This is the step that was missing) Change the code that handles emails so everyone can unsubscribe. Sometimes it's important to get something out quick and things aren't always dark UI / UX on purpose. Users are often blaming us devs for our dark evil powers when all we did was shake out some code on a too tight deadline.