What This Update Actually Is
App Pages with UI Extensions is a new capability inside HubSpot's developer platform. It lets app builders create dedicated, full-page experiences that live directly inside HubSpot.
These aren't pop-up panels or sidebar cards. They're complete, routed pages with their own navigation, header actions, and data fetching. Think of it as giving your app its own section of HubSpot.
You build it using the same UI Extensions SDK you'd use for CRM cards or settings pages. The new pieces are PageRoutes for multi-page navigation, PageLink for linking between those pages, and a PageHeader wrapper for primary and secondary actions. It's React all the way through.
Once deployed, the app shows up under the Marketplace icon. Humans inside a HubSpot portal can reach it from "Recently visited apps" or via a direct app URL. No new login. No new tab. No context-switching.
Why HubSpot Shipped This
The external problem: apps built on HubSpot had no real home inside the platform. If your app needed a dashboard, a setup wizard, or a help section, you had to send humans to an external URL. That breaks the workflow and kills trust in the tool.
The internal frustration: we've seen it across dozens of portals. A team installs a HubSpot app, and three weeks later nobody's using it. Not because it wasn't useful. Because the onboarding lived somewhere else, the config lived somewhere else, and the reporting lived somewhere else. The app felt disconnected.
HubSpot's answer is to make the app a first-class citizen inside the portal. Give it a home. Give it pages. Give it navigation. Close the loop so the entire experience stays inside one platform.
How to Use It Step by Step
- Run hs project add in the CLI and select "Pages" to generate the React and configuration files for your app pages.
- Build your primary page using standard UI components from the UI Extensions SDK. Wrap the top section with the PageHeader component to add primary and secondary action buttons.
- Add additional pages to your app alongside the primary page. Each page is a separate React component in the project structure.
- Use the built-in PageRoutes component to register your pages and define the routing structure between them.
- Use PageLink components inside your UI to create navigation between pages. This keeps routing native and consistent with HubSpot's UX patterns.
- Deploy the project using the standard HubSpot CLI deployment flow. Your app pages go live alongside any existing CRM cards or settings pages.
- Verify access by clicking the Marketplace icon in the HubSpot nav, finding your app under "Recently visited apps," and confirming all routes and header actions render correctly.
What It Touches in Your HubSpot Strategy
This update is primarily a developer-side capability, but its ripple effect hits real operational decisions. Here's where it shows up.
App adoption and onboarding flows. If your team uses a third-party or custom-built HubSpot app, that app can now surface its entire onboarding experience inside the portal. No more "go to this URL to finish setup." That one change alone removes a common adoption failure point.
Key Takeaway
App Pages can host onboarding, reporting, configuration, and support resources all in one native location. If your team has abandoned apps mid-setup before, this is the fix.
Custom reporting and dashboards. Developers can now build full reporting views with native data fetching directly inside the app page. This is meaningful for RevOps teams that need data pulled from an external system displayed alongside HubSpot activity, without building a separate report destination.
Integration UX quality. For any integration partner or custom app builder, this changes the quality bar. A well-built app page can feel indistinguishable from a native HubSpot screen. That matters for buy-in from the humans who actually use the tools every day.
This update fits a larger pattern HubSpot has been building toward. If you've been tracking the platform's direction, our breakdown of 34 recent HubSpot updates and the four signals behind them covers how "frictionless UX" keeps appearing as a consistent theme across the product roadmap.
Portal complexity management. As portals grow, tool sprawl becomes a real problem. An app that has its own home inside HubSpot means one fewer external bookmark, one fewer login, one fewer browser tab pulling humans out of their flow.
Key Takeaway
If your RevOps stack includes custom or third-party HubSpot apps, ask your dev team or app vendor whether App Pages are on their roadmap. A native page experience can meaningfully reduce tool churn and support tickets.
On the onboarding side, scattered tooling is one of the most expensive mistakes a growing company makes. It's a theme we cover in depth in the seven biggest HubSpot onboarding mistakes. A fragmented app experience is exactly the kind of friction that stalls adoption at week one.
Who Should Care Most
This update is most immediately relevant to three groups.
- HubSpot app developers and ISV partners who want to deliver a polished, fully native experience without routing users to external pages. This is the biggest quality-of-life upgrade the SDK has received for app UI in recent memory.
- RevOps and operations leaders at companies with custom-built HubSpot apps. If your internal dev team has built something that currently lives partially outside HubSpot, this gives them a path to bring it home. Available on all tiers, so there's no upgrade required to take advantage.
- Agencies and consultants managing portals for clients who use third-party apps. Ask your app vendors whether they're building App Pages. If they aren't yet, the ones who ship it first will have a meaningful UX advantage over competitors in the same category.
This update is less urgent for teams that use only native HubSpot tools with no custom or third-party apps. But if integrations are part of your stack, it's worth understanding what's now possible.
George's Take
I've watched teams install genuinely useful apps in their portals and then abandon them within a month. The problem was never the app itself. It was the experience. Every time a human had to leave HubSpot to do something in that app, there was a small but real moment of friction. Those moments add up fast. App Pages with UI Extensions removes that excuse. Developers now have the tools to build something that feels like it belongs inside HubSpot, because it actually does. If you're running a custom integration or you manage a stack with third-party apps, this is the moment to have a real conversation with your dev team about what the experience should look like going forward.
“The app was never the problem. The disconnected experience was. App Pages finally closes that gap.”
This sits alongside a broader push toward cleaner, more connected HubSpot experiences. We covered a similar theme in our three-bucket breakdown of the May 1 HubSpot release wave, where "frictionless UX" showed up as one of the clearest through-lines in recent product decisions.
If you want to talk through whether your current app setup is costing you adoption, or if your dev team needs a sounding board on architecture decisions for App Pages, book a strategy call with the Sidekick team. We've seen what works across hundreds of portals and we're here to help you build it right.
Frequently Asked Questions
What are HubSpot App Pages with UI Extensions?
App Pages with UI Extensions lets developers build full, multi-page experiences inside HubSpot using React and the existing UI Extensions SDK. These pages have their own navigation, header actions, and native data fetching. They live inside the HubSpot portal under the Marketplace icon rather than pointing users to an external URL.
Who can use HubSpot App Pages?
App Pages are available across all HubSpot hubs and tiers as of April 14, 2026. Any developer building an app on HubSpot's platform can start building App Pages today. There's no paid tier requirement, but you do need to use the HubSpot CLI and the UI Extensions SDK to build and deploy them.
How do users access App Pages inside HubSpot?
Users access App Pages by clicking the Marketplace icon in the HubSpot navigation bar and selecting their app from "Recently visited apps." Apps can also be accessed via a direct app URL. No external redirects or separate logins are required.
How is an App Page different from a CRM card in HubSpot?
CRM cards appear inside contact, company, or deal records as a panel or sidebar component. App Pages are full-page, standalone experiences with their own routing, multi-page navigation, and dedicated header actions. They're designed for dashboards, onboarding flows, configuration screens, and reporting views that don't belong in a single CRM record.
What SDK components are needed to build HubSpot App Pages?
You need the HubSpot CLI and the existing UI Extensions SDK. The new components are PageRoutes to register and manage multi-page routing, PageLink for navigation between pages, and PageHeader to add primary and secondary actions at the top of each page. Standard UI components from the SDK work on all pages.
Can existing HubSpot apps be updated to include App Pages?
Yes. App Pages can be added alongside existing CRM cards and settings pages in any HubSpot app project. Run hs project add in the CLI, select "Pages," and the necessary React and configuration files are generated. Existing functionality in your app isn't affected by adding App Pages to the project.
