This just struck me. When we get range proofs a "queued transaction" option would be amazing. For those who are unaware with the introduction of rage proofs comes the scaling of transactions by number of outputs at log(n). This would massively reduce fees for a lot of users and atleast some amount of network load. It would in a way allow monero to do micro transactions. Or something maybe pretty close to it.
So lets say we are talking about the gui. When you prepare a transaction right below the "send" button there could be a "queue" button. Just queue up any sort of transaction that is non critical. If you want to make a donation to your favorite artist. Or you owe a friend some money but he isn't in a hurry to get paid back. Or you want to buy something but you aren't in a hurry to get it right away. Don't send it just queue it. Once you get a decent amount of things queued the fees would be drastically reduced. Up to 80% ontop of the already 80% savings being brought by range proofs.
And incentivizing people to queue in-order to save themselves money has the added benefit of saving everyone else who uses the network money too. Holy virtue cycle.
Note that queuing is more difficult in Monero as change outputs are locked for 10 blocks. You could, however, queue some transactions if you have multiple inputs.
I only mean saving the intention of making the transaction for later. It really would be sort of an aesthetic thing. Not very different from having a todo list in a text file and adding addresses and amounts to it to save for combining later. I'm just imagining that it saves the address that you want to send to and the amount that you want to send and then adds those, with your permission, as outputs on your next pertinent transaction.
You might say that it isn't really the job of the monero core team to code something that could be done with a text file in another window. But, if people were provided a nice little convenient tool for doing this, it would have the effect of explaining to everyone that this is a good practice and help the network scale more since more people would naturally engage in this good practice more often.
Or am I missing something? Is it actually difficult to produce a transaction with say 1 input and 5 outputs?