amitvaria

So a scenario I run into often, but I'm not sure if this type of service would work very well for me. Before I go into specific cases, I initially wondered why an SMS interface? An app for the phone that works offline/online would be something I would more expect.

I tend to meet new people in bulk. For example, I go to meet a new client and get introduced to 5 people. Or I go to a networking event and am bouncing around meeting some new people. In either of these scenarios, your solution wouldn't work well for me.

In the first scenario, it would be a pain for me to send 5 different texts and walk through the prompts. So an interface for mass input would be great. In the second scenario, I'm not looking to break away from my conversations to type in information into my phone. This is a much tougher problem because really I want to remember who I just met without having to distract myself from my next conversation.

Good luck with SW!

True - but you have to understand the distrust people have with supplying a website with information like other people's phone numbers. What happens to the numbers after Tuesday? Will the data be used for anything else? Will the message include any additional advertising?

I'm sure you're doing this with the best of intentions, and commend you for that. But you have to understand that healthy skepticism on the internet is necessary to protect yourself.

So another way to look at it is having re-usable components that you can choose to include/exclude as needed. Then use LESS to customize, tweak, extend those components as needed to create the custom design you need. https://wrapbootstrap.com/ has some examples of work done in this area.

Looks great - any plans on Google Drive integration?

But consider Facebook's "friction-less sharing". Facebook now knows you just listened to a song, read and article, took a trip, had a baby, got married....

Now think of the targeting you can get there.