Your suggestion is pure genius. We'll just call it a roguelike and that would explain the 'no save button'. I'll be sure to recommend you at the next 'dark pattern' meeting! /j
As for the latter, if we're going in that direction, we might as well go all the way and implement some COM-like thingy for the web, so users can attach multiple whatevers and work on them in the email. This seems more efficient than turning each email to a unique embedded app which can embed only one type + maybe attachments.
Despite all this being possible in Outlook-land, everyone I'm familiar with prefers opening the attachment and working in a separate window, but I guess some people would rather work inline?
I meant that in Windows there is an alternative to attachments to an extent. COM allows an application to embed in another application. i.e. I can paste some Excel into Outlook and it will keep the table formatting and I can manipulate it in Outlook as if it were Excel. It's not the best implementation though (pretty bad on the other side), and there probably is a much nicer way to do it.
You could be right, with a better implementation there would be more that choose to work that way. I still think the risk outweighs the possible limited benefit though.
As for the latter, if we're going in that direction, we might as well go all the way and implement some COM-like thingy for the web, so users can attach multiple whatevers and work on them in the email. This seems more efficient than turning each email to a unique embedded app which can embed only one type + maybe attachments.
Despite all this being possible in Outlook-land, everyone I'm familiar with prefers opening the attachment and working in a separate window, but I guess some people would rather work inline?