Show HN: Locent – Mailchimp for SMS
locent.com
locent.com
Firstly, since you're using a responsive front-end framework (Bootstrap), you should configure the viewport meta tag:
<meta name="viewport" content="width=device-width, initial-scale=1">
should work nicely. Add 'minimum-scale=1' to the meta tag's content to enable rasterization (better FPS when scrolling etc.)You also have a bug in your markup which causes content to overflow outside of the viewport, resulting horizontal scrolling being possible at 1x scale when it shouldn't be.
This is because the #benefits row should be wrapped by a containing element with 15px left and right padding to balance out the Bootstrap row element's negative margins.
This issue is actually present on other pages as well. You'll want to add 15px left/right padding to the #support element, the #login element, and the .register element on their respective pages.
Typically, rows in Bootstrap are intended to be wrapped by a div with either the 'container' or 'container-fluid' class, which add the aforementioned padding.
The beauty of the Bootstrap grid is that the rows' negative margins allow grids to be nested without squashing columns with ever increasing gutters. This negative margin comes at a price: it adds to the containing element's width, meaning that padding must be added to eat this inflation.
Finally, the mixpanel link is clickable just beneath the clients image, when the button is actually at the bottom of the page. This is because the image is positioned relatively and offset by 250px, yet the containing anchor is not, and appears in its normal place.
To fix this last issue, replace this:
#home #mix {
position: relative;
top: 240px;
}
and with this: .featured a {
position: relative;
top: 240px;
}I noticed that the Features page is a bit broken, probably not finished yet. The markup is a bit odd-looking to me. Not because Angular's involved, but because it looks like it tries to re-invent some wheels Bootstrap already has covered.
I'm not an Angular developer per se, as I've largely avoided frameworks by rolling my own over the years, but I did mock-up what might be a simple but effective way of structuring the page using Bootstrap's grid system.
The trick would be to use whatever the Angular equivalent of Bootstrap's jQuery-based tabs is.
Hopefully it's of some use as well:
I hope users who would like to see bulk messages on their phone chose to opt-in (manually, not auto-opt-in). Your terms of use do not demand this.
In the US: "FCC rules ban text messages sent to a mobile phone using an autodialer unless you previously gave consent to receive the message"
I would wonder deeply about opt-in rates as well. How are you keeping track of how much users enjoy receiving these messages? (Not just click rates because people might click something they hate to receive)
Also, confusingly, your terms of use state:
> You agree that You will not use the Service to send.. "promotional materials"...
But that's what's shown as an example on the front page?
Our business model is built around keeping subscribers opted in. When subscribers decide they no longer want to receive messages, we lose money. We track satisfaction by examining - among other variables - opt-out rates, click-through rates and response rates. The crux of our business is subscriber satisfaction and we take it very seriously.
- having a single opt-in code is not enough;
- it would be nice to offer lower prices for non-profits;
- any plans for an API?
Thanks for reviewing our product! We built Locent to help you reach customers more effectively using SMS (text messaging). Think of us as Mailchimp for SMS. We help you build a full text marketing program in minutes. All the ordinary email use cases apply with text messaging, we just have higher read rates and conversion rates particularly on smartphones. Really appreciate your feedback!
Also, what about templating based on user profile data? For example "We will be launching product Foo in {{ user.city }} soon. Stay tuned!"
The service looks cool and I'll give it a shot for my next side project.
PS your site looks great!
Are there volume limits that would get you blocked from carriers (ie. AT&T, Verizon, Sprint, T-Mobile) even if you have two way consent?
The specific limits vary based on a number of factors like volume per period, inbound/outbound ratio and so on, but carriers empowered the short code industry (5 or 6 digit phone numbers) to allow mass messaging to happen on terms they're comfortable with. When you create a short code, you specify what they should expect from you and if they approve you get to send 30+ messages per second.
That said, DIY gets complicated very quickly in this space (hence why we built Locent).
not as turnkey though and not really marketing based
We charge you per active subscriber per month, meaning that you only pay for people who have agreed to receive your messages. We have skin in the game to make sure you do well. If you don't, we don't get paid.