Appcelerator (discontinued) vs. Azure App Service vs. Salesforce Lightning Components & Developer Experience

I do not think I can recommend Appcelerator at this point due to the issues with Appcelerator studio, lack of good debugging support, lack of thorough documentation and forums and the additional cost overhead of licenses. The pros are just that it allows for cross-platform development. However, Cordova does a much better job of it and excels at places where Appcelerator currently struggles

Incentivized

You may easily deploy your apps to Azure App Service if they were written in Visual Studio IDE (typically.NET applications). With a few clicks of the mouse, you may already deploy your application to a remote server using the Visual Studio IDE. As a result of the portal's bulk and complexity, I propose Heroku for less-experienced developers.

Incentivized

If you have a large customer base and a large amount of data on each of your customers, it is really strong in creating personalized content that your salespeople can use in their pitch meetings—and then setting up workflows for automated for lifecycle journey creations to automatically go out to customers.

Incentivized

• Adds structure to your code through Alloy framework.
• Easy to integrate with iOS SDK and to build and run iOS apps.

Incentivized

• Extremely easy to deploy and update from Visual Studio
• It integrates seamlessly with other Azure PaaS resources
• It has an in-depth integration with AppInsights, so you can understand errors and their root cause easily.
• Easy to create and delete, what is not the same case in a IaaS resource
• It escalates based on CPU workload and some other resource variables.
• Configuration changes are almost immediate
• Offers an excellent abstraction from hardware backend of the platform
• That's updated very often, saving time and the risk of a self-performed update over a IaaS
• That's really easy to develop for Web Apps
• It supports Function Apps and Web Apps into the same "cost black box"

Incentivized

• It has a very smooth integration with Salesforce and third-party tools, ensuring easy tracking of policies and assets.
• It also has impressive security features like used-based permissions and encrypted data.
• Everything can be managed from a centralized place which saves a lot of time.

Incentivized

• It is very hard to debug your code. Breakpoints never worked for us even with the latest Appcelerator Studio and we had to rely on log statements to debug.
• There is a need to purchase licenses from Appcelerator to run the code on a device or for creating iOS distribution builds. This is an additional cost when you have already paid for Apple developer program for precisely these things.
• If things are broken due to lack to support between Appcelerator and a new iOS version, you pretty much have to rely on a new version release from Appcelerator for the issue to be fixed.
• It is difficult to create enterprise distribution builds where the distribution certificate is owned by your organization's team and you only have a development certificate for the same.
• The forums on developer.appcelerator.com are seldom helpful. It is hard to find solutions for issues even on other forums like stack overflow.
• Documentation needs to be improved.

Incentivized

• Jumps between resource sizes can get expensive
• You may wind up putting a lot of eggs in one basket--not necessarily a con but something to keep in mind (most of your data will likely be managed and processed through Microsoft products/services if you fully commit to Azure App Service).
• Learning new technology. If you're moving from on-premises to Azure App Service (or any cloud solutions), you'll likely have to rethink how things are done to achieve the same end results (and/or resources may become expensive quickly).

Incentivized

• It takes a while before it recognizes bounced emails.
• We get so many notifications from a single action. Not sure if this can be modified in the settings though.
• Error messages are sometimes unclear which makes it hard for us to identify the problem.

I have given this rating because Azure App Service performs very well in terms of speed, reliability, and reducing overhead, and improves overall team productivity, with a little scope for improvement in complex testing scenarios and configurations, scalability concerns in a large setup, and similar tracking and audit needs.

Incentivized

It's very good, but it's still living in a little bit in an older design aspect, but I think a lot of it is about to come out, just hasn't quite gotten there yet. Still a little clunky from a you have to know it to know it or you know it to use it. It takes a little bit of training to get into it. It's not quite the, anybody can come in and start using it immediately, type feel.

Incentivized

Microsoft has always been known for providing a high standard in terms of customer support and Azure App Service (and as a matter of fact the whole Azure Platform) is no exception. Azure App Service never caused us any issues and we only contacted their customer support for questions regarding server locations and pricing. I feel pretty satisfied with how they treat their customers.

Incentivized

I am not an administrator so there may very well be outstanding Support and I am just not privy to it. On a user level it's hard to gauge the effectiveness and responsiveness of Support because nearly everything has to go through an administrator

Incentivized

Appcelerator makes you write a structured code whereas Cordova just packages your code and you are free to structure it. Appcelerator bridges your javascript code with native code and that would make it run faster than javascript code in Cordova apps. However, with recent mobile browsers, you would hardly notice any performance deterioration with Cordova apps. Appcelerator struggles with issues related to its IDE, debugging, documentation and forums and additional costs. Cordova makes it much more simpler to develop cross-platform apps with better developer support, debugging support, documentation and forums minus the additional costs.

Incentivized

When we chose it, we did so because of its integration with Microsoft applications; now we need to integrate with AI, and Azure doesn't offer a good integration. That is the main reason to change it. It is still great to develop Windows- and Microsoft-based applications, but if we need to integrate with AI, Google wins by far.

Incentivized

We were previously using an older version prior to it becoming Salesforce Lightning Platform so we were well adverse on the advantages of using a CRM, to begin with. It made sense to convert to Salesforce Lightning Platform after we were given a free trial of the platform. Certain reps were chosen to experiment with it and from there a decision was made to move forward. We've been customers ever since.

Incentivized

• We were able to build and deploy a mobile app with Appcelerator. However, the platform still has issues and does not cover our needs as much as some of its competitor like cordova does.

Incentivized

• Deployment of ASP.NET apps at the organization has been sped up.
• An option to offer access to the version control system on a third platform so that we could easily deploy our apps.
• Because of Azure App Service's scalability capabilities, the costs of running the services are kept to a minimum. As a result, we may save hundreds of dollars each month compared to the expenses of traditional servers by using fewer resources during slack periods.

Incentivized

• Better visibility of Accounts and Contacts interactions makes it easier to maintain during employee transitions.
• Tracking of current jobs and relating them to past jobs is very useful.
• More efficient use of Sales Reps time.
• Sales Managers have good visibility into how their people are working.

Incentivized