4 ms·
Oh yeah I got why your system is easier but it does have the disadvantage of losing web interactivity. For example editing a comment, deleting a comment is eith
by quickthrower2 3y ago
Oh yeah I got why your system is easier but it does have the disadvantage of losing web interactivity. For example editing a comment, deleting a comment is either not possible or requires knowing the protocol. Formatting is probably another thing that needs to be more basic.
So that is the trade off: (a) your method is simpler vs. (b) a magic link allows web-based interactivity.
I just thought now though: your method could reply with a magic link for later use.
- asimpletune 3y agoO I see what you mean. That makes sense. I'll add that to the backlog. Thanks for the feedback!
- RileyJames 3y agoBoth perspectives make sense, it’s simply a trade off. But it seem like the perfect opportunity for progressive enhancement. An initial comment can be via email. Additional capabilities via a magic link received in response to the first email. I love this idea, and I think it’s quite powerful in how frictionless it makes the initial process. There’s a cognitive load to creating an account, even with a magic link interaction. Any requirement to “sign up” bring with all the baggage of experienced passed. This manages to break out of that space for me, which makes it a very interesting proposition.
- asimpletune 3y ago> An initial comment can be via email. Additional capabilities via a magic link received in response to the first email. That's pretty close to what I do now. After you submit a comment via email, you receive an 'auto-r3ply' telling you it worked, along with a link to a preview. I just haven't implemented the edit/delete functionality, but it's coming. > I love this idea [...] There’s a cognitive load to creating an account [...] This manages to break out of that space for me, which makes it a very interesting proposition. Thank you!!!