Need advice about which tool to choose?Ask the StackShare community!
Nexmo vs Tropo: What are the differences?
Nexmo: API for SMS, Voice and Phone Verification. Nexmo connects your apps directly to carriers around the world. Integrate SMS and Voice messages using one simple API. Use Nexmo Verity to register users, verify transactions, and implement two factor authentication; Tropo: Add Voice and SMS to Your Applications. Tropo is a powerful yet simple API that adds Voice and SMS support to the programming languages you already know.
Nexmo and Tropo can be primarily classified as "Voice and SMS" tools.
Some of the features offered by Nexmo are:
- Inbound SMS
- Outbound SMS
- Outbound Text-To-Speech Calls
On the other hand, Tropo provides the following key features:
- Develop for FREE- Pay when you're ready- Tropo is completely free for developers. Pay when you deploy and only for what you use.
- Feature Complete- Get all the features you want, today. Speech input, multi-language, and more.
- Amazing Support- Ask us questions 24 hours a day. Via the web or IRC.
What is Nexmo?
What is Tropo?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Tropo?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Nexmo?
What are the cons of using Tropo?
What companies use Nexmo?
What companies use Tropo?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Tropo?
Sign up to get full access to all the tool integrationsMake informed product decisions
SmartZip
Nexmo vs Twilio ?
Back in the early days at SmartZip Analytics, that evaluation had - for whatever reason - been made by Product Management. Some developers might have been consulted, but we hadn't made the final call and some key engineering aspects of it were omitted.
When revamping the platform, I made sure to flip the decision process how it should be. Business provided an input but Engineering lead the way and has the final say on all implementation matters. My engineers and I decided on re-evaluating the criteria and vendor selection. Not only did we need SMS support, but were we not thinking about #VoiceAndSms support as the use cases evolved.
Also, on an engineering standpoint, SDK mattered. Nexmo didn't have any. Twilio did. No-one would ever want to re-build from scratch integration layers vendors should naturally come up with and provide their customers with.
Twilio won on all fronts. Including costs and implementation timelines. No-one even noticed the vendor switch.
Many years later, Twilio demonstrated its position as a leader by holding conferences in the Bay Area, announcing features like Twilio Functions. Even acquired Authy which we also used for 2FA. Twilio's growth has been amazing. Its recent acquisition of SendGrid continues to show it.
NexmoIt just works as expected within minutes -- you get both outbound/inbound messages, with delivery receipts or incoming callbacks -- all working in the easiest form.
NexmoWe fall back to Nexmo when Chikka (https://api.chikka.com) and Semaphore (http://semaphore.co) have downtime or deliverability problems. Chikka and Semaphore are local (Philippine) SMS APIs handled by SMART and Globe, respectively, and report higher deliverability rates than Nexmo (at lower cost).
NexmoSMS sending for harbour masters and sailors.