The Mac app feels unfinished — connections, files, etc. aren't draggable, reshare doesn't work (can't even select the files), but all of that is stuff you'll obviously get around to.
I'm using it now, and it's so close to being exactly what I need, with two necessary pivots that seem almost predestined to happen from your current position. The current basis of it being an inbox for files is already on the right track, and something I haven't seen attempted before, but it needs a little more verisimilitude to email:
1) The requirement to invite / induce signup / confirm "connections" needs to be ruthlessly optimized out — I should be able to just send a file to any email easily, forming a 'weak' connection. Maybe they have to do a 3 second signup to download the file, but it needs to be all in one motion. This obviously brings up a ton of issues like how to display the now 4 types of connections and unsolicited files, but it's essential to you getting traction.
2) 'sent' files need to behave like a outbox — remember that one of the biggest uses of email attachments is just sending stuff to yourself. Really you should just implement that straight up, it's the biggest use I'd have, and one I think you would find yourself as soon as you get the iOS client going. The dropbox iOS app's UI is terrible for it (pick one photo at a time and wait), plus really the filesystem metaphor is all wrong anyway! I actually want the transactional inbox feel of email here. If you don't explicitly support this I'm just going to end up using it with a computers account and an iPhone account.
Hmm, all of those things you described up top are working well for us - can you tell us what version of OSX you're running on? Also what version of Receivd are you using?
1. You can send a file to any email right now - once you invite an email, they'll be greyed out in the sidebar, then drag any files to them as you would with a confirmed user. They don't even have to signup to download the file. You can even add those folks to a list.
2. Interesting point. We'll think more about this.
Thanks a lot for your comments. Can we reach you directly somehow to figure out why you're seeing these issues?
OS 10.6.6 (10J567), Receivrd 0.7.5 (16). I expect to be able to drag a connection to a list, and drag a file from inbox/connection/list activity/received lists and the "sharing activity" lists to all other targets (including outside the app). The Re-Share button has not lit up, which did not surprise me given that I can't really get a file into a selection state. If all this is working for you, I can just try updating / rebooting.
I can send a file to any email now, but there's a lot of sharp edges. You make me click through a modal sheet wizard to intentionally setup a contact first, there should really be an email textbox / fb friend selector / etc. in your app. The worst part about the current setup is that it forces you to first send a no-context invite email minutes before sending a meaningful "x has shared y with you" email. The first kind of email really needs to only ever get sent when a user is explicitly inviting other people to share with them, which is probably not going to be the default path.
My email is in the 'about' area of my profile if you want to reach me.
I'm using it now, and it's so close to being exactly what I need, with two necessary pivots that seem almost predestined to happen from your current position. The current basis of it being an inbox for files is already on the right track, and something I haven't seen attempted before, but it needs a little more verisimilitude to email:
1) The requirement to invite / induce signup / confirm "connections" needs to be ruthlessly optimized out — I should be able to just send a file to any email easily, forming a 'weak' connection. Maybe they have to do a 3 second signup to download the file, but it needs to be all in one motion. This obviously brings up a ton of issues like how to display the now 4 types of connections and unsolicited files, but it's essential to you getting traction.
2) 'sent' files need to behave like a outbox — remember that one of the biggest uses of email attachments is just sending stuff to yourself. Really you should just implement that straight up, it's the biggest use I'd have, and one I think you would find yourself as soon as you get the iOS client going. The dropbox iOS app's UI is terrible for it (pick one photo at a time and wait), plus really the filesystem metaphor is all wrong anyway! I actually want the transactional inbox feel of email here. If you don't explicitly support this I'm just going to end up using it with a computers account and an iPhone account.