I love developer tools or platforms that productize things everyone keeps rebuilding. Great idea, @astaub.
What information are you using to suggest people to invite?
@rrhoover thanks!
Our suggestions are based on number of mutual address book contacts. So we suggest friends with whom you have lots of common friends. Similar to Facebook or LinkedIn's suggested friends algorithms.
We'll add other ways to target in the future.
@astaub smart! I'm not sure what's available through the iOS API but if you could identify which people you recently texted with, that might be a good signal to use.
Looks like something most app devs repeat coding over and over. Makes sense.
Wondering about how it ties together the invite codes to give credits to the right people. Guessing it's more complicated than just a drop in solution since they have manage and close the loop on which code gets attributed to which account and make sure all the promo codes are verified
@kristofertm Thanks!
We have two simple ways to work with invite codes.
One option is to just include the invite code in the copy of the invite message and it works just like any other invite mechanism.
We also send out the invites with links that we attribute through the app store. So when someone opens the app for the first time, we have a call developers can make to find out if the user came from an invite, and if so, from who.
We use Mave beta at SWIG and it has been great for acquiring new users. On average, an inviter personally invites 5.375 people. They have a really easy-to-use dashboard for tracking your referral success too. Well worth the 30-minute integration.
@tedp thanks! Our dialog gets more invites sent.
Apple's SMS dialog is built for messaging. If you use Apple's SMS dialog your users need to think of a friend and then type in their name. If they want to invite multiple friends they have to send a group message.
We built our SMS dialog for invites. We suggest friends to invite and allow the user to send multiple individual SMS invites at the same time.
I've worked a lot on mobile invites and I believe any startup using your SDK is opening themselves up to a huge amount of legal liability since it is in violation of the Telephone Consumer Protection Act. You are not sending the SMSes from the user's phone number, but rather you're using Twilio. Voxer, Path, and Slide, etc, just to name a few, have been sued for millions of dollars for similar practices.
See Hickey v. Voxernet, Montes v. Path, Sterk v. Path, Pimental v. Google
@jwegan_com Thanks for bringing this up. You are right that there is potential liability when using SMS for invites. This is true whether you are using Twilio or not.
In at least some of the cases that you mentioned the companies were allowing users to click select all buttons and send hundreds/thousands of invites at a time. In some cases it may not even have been clear that text messages were going to be sent.
We don’t allow users to select all of their contacts at once and we’ve made it very clear that the inviter is sending a text message, designing our page to look like the native SMS client. The user must manually select a contact and tap send, which is far from being an automatic dialing system (which is what the law explicitly restricts).
The FCC is actually going to clarify the issue some time soon (hopefully): https://www.fcc.gov/document/cgb.... The latest lawsuit, which is against Lyft (who was allowing invite all) is currently suspended until the FCC rules.
@astaub just out of curiosity, is implementing 'invite all' functionality only prohibited when using SMS or also using 'invite all' via email? Could you shed some light on this?
@joshtiinkk Invite all with SMS is not actually prohibited. I was just trying to explain that we are not doing the same thing that some of these other companies were. The laws are ancient and unclear. Cases were being based on laws that were written about auto-dialing spam phone calls in the early 90s. That's why the FCC is supposed to clarify the issue.
The laws related to email are more clear, because of the CAN-SPAM Act. I'm not a lawyer but I'd say invite all with email is less risky.
https://www.ftc.gov/tips-advice/...
Looks good, though is somewhat confusing I have to select an existing app in order to "Create Application", but wouldn't this naturally be used while an app is development? Seems like would be extra work once an app is released.
@asherraph Thanks for the feedback!
You can actually complete "Create Application" without an itunes app id. We'll make that more clear. Your invite links would then just go to your website instead of the app store.
Hi. Co-founder here. We're building Mave to help apps grow.
We help optimize virality, while allowing app developers to focus on what makes their product uniquely valuable. Prior to Mave, we built Venmo's growth engine, so we know how hard it is to grow an app.
We're offering instant access to our beta to Product Hunters. :)
We'd love feedback and questions!
We use Mave in @nibbly_! It's great to know a team of smart people are just focused on invite optimization so we can focus on the other parts of our product.
@babu_ck Thanks!
Our suggestions are based on number of mutual address book contacts. So we suggest friends with whom you have lots of common friends. Similar to Facebook or LinkedIn's suggested friends algorithms.
We'll add other ways to target in the future.
Product Hunt