NativeScript vs. Twilio

I gotta be honest, after a PoC period, we choose to rewrite the whole application in a different cross-platform app. Our developers had to invest a lot of time and effort to debug a lot of plugin-related issues, which we needed to utilize the android mobile phone capabilities. QR reader, special visualizations, and fine-tuning were really hard and often resulted in writing native Android code instead of using the shared Angular code. In the end, we think that writing a standalone Android app and an Angular app would have been a better alternative, as the shared code base was so unreliable that it did not save us any time.

Incentivized

Twilio is well suited to sending SMS reminders to prospects on the lead-up to sales appointments. This has helped us improve attendance rates for these meetings. We also use Twilio to communicate with these prospects post-meeting to make offers on products and services and for feedback on their meeting.

Incentivized

• True native app. The app uses native components and that is quite noticeable in the overall performance of the app. NativeScript is also awesome in the way we can access the native APIs, so we are never really constrained by the framework. If we need, we can just dive into the native APIs without leaving our environment and language (JS).
• Cross-platform. Builds for Android and iOS. It deals with the platforms differences very well.
• Support for Vue.js. Even though it is just a community effort, the NativeScript-Vue plugin is the best alternative to build native Apps with Vue.js. That was a major factor to go with NativeScript.

Incentivized

• Easy to see my team in one place, when they log in and out and what call status they are in.
• Twilio is a simple, user friendly way to log in and out of work activities.
• Excellent services and support.
• The omnichannel feature which allows agents to get request from all channels.

Incentivized

• The need to know the native Android and iOS APIs to access device hardware and other platform-specific functionality
• Not all user interface components are available for free
• NativeScript has no HTML and DOM, which requires some deep knowledge of different UI tools to be implemented instead

Incentivized

• Segment’s email identifier is case-sensitive, which is ridiculous because emails themselves are not case-sensitive. This means that if I send a capitalized email address in an identify call, it will create a duplicate user rather than matching it with the lowercase email. I think this is a technical oversight that should be corrected.
• I’d like to see more information about the eventual transition of existing Frontline customers to Twilio Flex
• I’d like to see some integrations between Twilio Studio and OpenAI or another open source LLM to provide automated responses, if this hasn’t been done already
• I would like to be able to drag and move the actual lines connecting the steps in Twilio Studio, sometimes mine can get pretty messy
• I think a Bug Report form would be beneficial for developers

Incentivized

The hybrid is ok but native is better for performance and the right use case I want to go for is the performance without dealing with too many development tools.

Incentivized

Unless we can get this handled quickly -- less than 1 week -- we will likely switch to another provider who, in my opinion, we'll have to spend close to $3,000 in development time to build a new integration for texting. Our clients need texting and I feel Twilio has failed us miserably.

Incentivized

Twilio has well documented APIs and examples. There are several tutorials, videos and Q&As regarding their services. So, usability is very good. I must say that advanced knowledge of telephony, API/Programming and error-handling is essential to make good use of Twilio. It's not just plug-and-play unless you are integrated with a system that has all of the programming built for it.

Incentivized

The problem tends to be us, the user, rather than Twilio. We don't reach out to support fast enough (spend time struggling), but when we have, they've solved our issue immediately. We are rural, so there are signal issues to accommodate, however, we find that a few staff on a few cellular networks can triangulate where we all have signal to put up a sign.

Incentivized

The community support is excellent.
They have a slack community as well as a discourse forum
forum.nativescript.org
Both of these offer community driven support.
The forum is more for a threaded discussion. The slack community is more for a quick talk.

Incentivized

I have not had to communicate with Twilio support in the last 3 years but my past experience with them has been very positive. They replied to my previous requests promptly and kept me well informed to resolve my inquiries. With their documentation that's available, I hardly imagine why anyone would need to contact support since it's all there in a concise and easy to understand format. It would probably take you longer to type out a support ticket than to just open their doc websites.

Incentivized

The developer APIs and SDKs are super easy to follow.

Incentivized

Ionic Ionic is an excellent Angular-based framework for mobile, and it does give a lot of access to the native device api's. However, the technology is based on Cordova, which means the apps being built are just webviews, with html, css and JS all running on the UI thread, and potentially creating very slow experiences for users. NativeScript is a truly native solution, and so provides a faster user experience. ReactNative We evaluate ReactNative, and found it much the same as NativeScript. The main difference is that your JS is all written with React, while NativeScript lets you choose between normal JS, Angular, and Vue. For our team, Angular was the most appropriate choice.

Incentivized

Twilio was referred to me by a business colleague, and I can't be more thankful! Twilio has helped my Facebook page by leaps and bounds, and I haven't even considered trying another chat option for my page. It is easy to set up, and customer service is quick to answer any and all questions you may have. I highly recommend it!

Incentivized

Being in South Africa, direct local currency support would be nice

Incentivized

• The poor quality of NativeScript documentation has the potential to weigh heavily on development timelines, budgets, and QA resources in a NEGATIVE manner.
• The poor interoperability of NativeScript plugins can significantly increase development time.
• The need to seek out professional instruction to learn how to use NativeScript effectively may become a burden on your budget.
• The number of breaking changes between versions of NativeScript, may cause your development efforts to lag further behind the most recent releases of NativeScript and your other chosen environments than you are accustomed to.
• NativeScript still does not support the latest major version of Angular. Any significant changes to the other environment components of your systems may hold you back even further while NativeScript plays catch-up.

• It helps drive the adoption of multi-factor authentication by making second-factor authentication quick and easy.
• Decreases the number of times a user spends migrating to a new device from an old one.
• Enables easy access to second-factors of authentication by offering multi-device support, making multi-factor authentication painless.

Incentivized