I think this is a great start to solving what has evolved into a real world problem. However, I think that this idea needs to be explored further. As others have indicated, the resulting User Experience for the Sender is not that great. The time investment requirement has shifted from the Receiver to the Sender, which does not really solve the problem. I think a truly elegant solution to this problem will lower the time investment for both the Sender and the Receiver. So with this said, I like the approach, and I think Boris is half way there (with a strong focus on the Receiving End at this point).
If it were my project, I would now brainstorm and focus on how to make the User Experience better on the Sender end. He mentions that he plans to eventually have an iPhone/Android App (aka UI of some sort on the Senders End), which I think is a 'must' in terms of facilitating a good User Experience for the Sender.
If it were my project, I would now brainstorm and focus on how to make the User Experience better on the Sender end. He mentions that he plans to eventually have an iPhone/Android App (aka UI of some sort on the Senders End), which I think is a 'must' in terms of facilitating a good User Experience for the Sender.