If you have been working with ServiceNow for a while, you have probably spent a good amount of time in UI Builder – I certainly have. This tool has made it much easier to build modern ServiceNow experiences without having to build everything from scratch.
But recently, I started exploring ServiceNow’s newer developer tooling around experience development, and it made me look at ServiceNow UI development a little differently.
The interesting part is not simply another tool for building UI, but a significant shift towards a more developer-friendly, code-first, and AI-assisted way of building ServiceNow experiences.
What’s Actually Changing?
Traditionally, a lot of ServiceNow UI development has looked something like this:
Open UI Builder → Select a page → Add components → Configure properties → Bind data → Configure events → Preview → Repeat.
This works well, especially for low-code development. But as applications become more sophisticated, developers often want things they are already used to in modern software development:
- VS Code
- Local project structure
- Source files
- Git
- Reusable components
- Faster iteration
- AI coding assistance
- Build and deployment workflows
This is where the ServiceNow AI Experience Lab for VS Code becomes interesting. It brings experience development into VS Code and allows developers to create and extend experiences, pages, and widgets using a more familiar development workflow.
My Experience So Far
I recently started experimenting with this myself. The first thing that struck me was that the experience feels much closer to modern application development than the traditional ServiceNow configuration experience.
You work with an actual project structure containing things such as:
now.config.json
package.json
src/
You can work from VS Code, use the ServiceNow development tooling, make changes locally, and then build and preview your experience.
Coming from a ServiceNow background, this is an interesting change in mindset. Instead of thinking, “Which configuration do I need to change in the instance?” you start thinking, “What am I building, how should it be structured, and how can I make it reusable?”
Does This Mean ServiceNow UI Builder Is Going Away?
I don’t think developers should look at it that way. UI Builder is still a very useful tool for visually creating and configuring ServiceNow experiences. I’d rather look at it as an expansion of our options.
ServiceNow UI Builder
Think: Configure and compose visually.
- Build pages visually.
- Configure components.
- Connect data.
- Configure events.
- Create page variants.
- Make changes quickly.
- Enable low-code development.
New ServiceNow Developer Tooling
Think: Build and extend using code.
- Create custom experiences.
- Build reusable widgets/components.
- Work from VS Code.
- Use source control.
- Follow a modern development workflow.
- Leverage AI coding assistants.
- Have more control over the underlying implementation.
So I don’t see this as UI Builder vs. VS Code – I see it more as: UI Builder + Pro-code + AI-assisted development.
Why Is This Important?
For me, the biggest advantage is developer experience. ServiceNow has historically been extremely powerful, but developers have often had to learn a ServiceNow-specific way of doing things for almost every layer of development.
The newer approach feels more familiar. You can have: VS Code → Source → Build → Preview → Deploy. And you can use tools that developers already understand. That can make experimentation much faster, and it becomes even more interesting when you introduce AI.
Instead of manually creating every piece of a UI, developers can increasingly use AI-assisted development to generate, modify, and iterate on code. The developer moves from being purely the person who writes every line to becoming the person who defines what needs to be built, reviews the implementation, and guides the AI.
That’s a very different development model.
What Does This Mean for ServiceNow Developers?
I don’t think this means we should abandon our existing ServiceNow skills – quite the opposite, in fact. If anything, I think the developer who understands both low-code and pro-code will have an advantage.
So, if you’re a UI Builder developer today, I’d continue learning UI Builder, but I’d also start becoming comfortable with:
- JavaScript/TypeScript
- Web components
- ServiceNow SDK
- VS Code
- Git and source control
- Component-based development
- AI-assisted coding
Because the line between a “ServiceNow configurator” and a “ServiceNow developer” is likely to become even more interesting.
Final Thoughts
The thing I’m most interested in isn’t actually VS Code, but the direction behind it. ServiceNow is making it easier for developers to build experiences using modern development practices, while still keeping the platform’s low-code capabilities.
That gives us something much more powerful than simply replacing one UI tool with another. We get a choice: for a simple change, use the visual tooling, and for something more complex, use code.
When AI can help with the implementation, the developer can focus more on the architecture, business problem, and user experience.
That’s where I think things get really interesting. UI development on ServiceNow isn’t disappearing – it’s evolving. As ServiceNow developers, this is probably a good time to start learning the new way of building, because we’re going to have more ways to build than ever before.
If you want to experiment yourself, check out the free app: ServiceNow AI Experience Lab for VS Code.