Appian vs Heroku Platform

• I have observed after version 17.1 we have a lot of good features in Appian that improve usability (UX). This adds real value in this competitive Digital space.
• You can understand business use case and convert it to a logical process automation.
• Process Modeller has improved a lot and providing smart services use adds more value.
• Service integration helps us to seamlessly integrate with third-party systems

Read full review

• Heroku has a very simple deployment model, making it easy to get your application up-and-running with minimal effort. We can focus on our efforts the unique aspects of our application.
• The robust add-on marketplace makes it easy to try out new approaches with minimal effort and investment -- and when we settle on a solution, we can easily scale it.
• Heroku's support is quite good -- their staff is quite technical and willing to get into the weeds to diagnose even complicated problems.

Read full review

• Advanced functionality requires use of the Appian expression language. The more advanced the logic, the harder it is to build with the expression language. This means development expertise is more relevant if you need advanced functionality, which I imagine applies almost all the time. I would much prefer if they allowed some common language such as JavaScript out of the box.
• Debugging has proved difficult. It’s easy for developers to get the app to or feature to a “working” state but it needs robust alpha testing.
• Deployment can be tricky. When a solution gets big and there are many teams and dependencies, it needs a careful process to ensure things don’t break.
• Reasuability of Appian objects is both a pro and con. Reusing objects across apps may be more trouble than its worth because of creating heavy dependencies. Experience is helpful to strike the right balance.

Read full review

• Large price jumps between certain resource tiers (2x Dyno for $50 per month versus Performance Dyno for $250). Free Postgres next jumps to $50 per month.
• Marketing/Branding to non-technical stakeholders. As the years pass, I've had to fight more to convince stakeholders on the value of Heroku over AWS.
• Improve Buildpack documentation. This is one area where Heroku's documentation is fairly confusing.

Read full review

• Our objective to reduce customer effort when dealing with government by 25% was exceeded. In the process of applying for an alcohol licence renewal alone, we saw approximately 80% reduction in time and effort for the business customer - and that was just a prototype! Imagine the possibilities when this is taken into a live environment!

Read full review

• Heroku allowed us to get up and running fast. Deployment was really easy and connecting to our codebase was, too. The deployment integration with GitHub is pretty slick.
• The add-ons provisioning is so simple and the documentation is so thorough that, at least at first, it means you don't have to hire a dedicated devops person to manage this stuff.
• Heroku has tools that allow the collaborators (those with access to the Heroku dashboard) to be able to quickly and easily do triage from just about anywhere, including your smartphone.

Read full review