G2

Jaiswal A.

Senior Software Engineer

Enterprise (> 1000 emp.)

11/5/2026

"Rapid Low-Code App Delivery on the Now Platform with Flow Designer"

4.5/5

What do you like best about ServiceNow App Engine?

What I value most is how quickly a business process can move from a whiteboard idea to a working application, without needing a heavy development cycle. App Engine Studio and its low-code tooling allow our team to build request forms, approval chains, and tracking apps in days rather than months. Just as importantly, the people closest to the process can participate in building the solution, instead of only documenting requirements for someone else.

Because everything runs on the Now Platform, new apps can inherit what’s already in place: role-based access, notifications, audit trails, reporting dashboards, and existing user and CMDB data. That means we’re not rebuilding logins, workflows, or integrations for every new app, which saves effort and helps keep governance consistent across the organization.

Flow Designer is a real standout. It enables us to automate multi-step logic—like routing approvals, updating records, and calling external systems—through a visual interface that non-developers can understand and maintain. And when we need more control, we can still drop into scripting, so we don’t hit a ceiling as requirements evolve.

It’s also reassuring that apps can be built, tested, and deployed within a single governed environment. Update sets, application scoping, and instance-to-instance promotion make it easier to move changes from development to production in a controlled way. For an enterprise that cares about security and compliance, that matters just as much as speed. Review collected by and hosted on G2.com.

What do you dislike about ServiceNow App Engine?

The biggest drawback is the cost. Licensing is complex, and the price can climb quickly as more users, apps, and add-on capabilities come into play. It’s often difficult to predict the total spend up front, and smaller teams or departments may struggle to justify the investment for simpler use cases.

The learning curve is also steeper than the “low-code” label suggests. Basic apps come together quickly, but anything involving custom data models, complex access control, or advanced scripting requires real platform knowledge. Teams without experienced ServiceNow developers can end up with apps that technically work, but are difficult to maintain over time.

Upgrades and customization require care as well. Heavily customized apps can run into conflicts during platform releases, which means regression testing takes time and discipline. Without clear governance, it’s also easy for instances to accumulate overlapping apps, tables, and scripts that nobody really wants to own.

The user interface is another sore spot. Apps look consistent, but getting a polished, modern front end often takes extra effort with UI Builder or custom components. Compared with dedicated front-end tools, the design flexibility can feel limited.

Finally, the documentation and community resources, while extensive, can be uneven. Finding the right guidance for a specific scenario sometimes takes more digging than it should, and best practices can vary depending on the release you’re on. Review collected by and hosted on G2.com.

What problems is ServiceNow App Engine solving and how is that benefiting you?

Before App Engine, many of our departmental processes depended on email threads, shared spreadsheets, and ad hoc tools. Requests were easy to lose track of, approvals stalled because no one was sure who owned the next step, and we had no dependable way to check status or report on turnaround times. App Engine gave us a single place to replace those workarounds with proper applications that track each request from submission through closure.

It also reduced our reliance on a central IT backlog. Business teams used to wait months for small custom tools, and by the time they arrived the underlying process had often changed. With low-code development, a small group can now build apps themselves and adjust them as needed, while IT maintains oversight through shared governance. The outcome has been faster delivery and less friction between IT and the business.

It has also helped with data silos. Because the apps are built on the same platform as our existing ITSM and HR workflows, they can reuse user records, assignment groups, and service data instead of relying on duplicate lists or manual syncing. That has reduced errors and given managers a more consistent view of work across teams.

In practical terms, we’ve seen shorter processing times, fewer manual handoffs, clearer accountability through audit trails and dashboards, and lower maintenance effort compared with the patchwork of tools we used before. Leadership can now spot bottlenecks as they happen, rather than discovering them after the fact. Review collected by and hosted on G2.com.