FAQs : Next Gen UI Rollout for Vertical Studio

FAQs : Next Gen UI Rollout for Vertical Studio

Summary
Oct 25, 2026 - New apps launch on Next Gen UI by default. Deprecation banner goes live for existing apps.
Dec 25, 2026 - Next Gen UI becomes mandatory for all orgs, across both Dev Console and subscriber orgs.
Extension requests must be submitted before Dec 25, 2026.
Partial adoption is not supported. The transition applies at the organization level - old and new UI cannot be mixed across apps.

General Overview

1. What is Next Gen UI?
Next Gen UI is a redesigned Vertical Studio workspace experience. It introduces reorganised navigation, flexible module views, a unified Interactions view, dark mode, and a fully responsive layout across desktop, tablet, mobile and many more.

2. What is the reason for this transition?
Next Gen UI is designed to reduce friction in everyday use - fewer steps to reach core actions, more efficient use of screen space, and a modernised interface. All existing functionality is preserved; this is a workspace redesign, not a reduction in capability.

3. Where does Next Gen UI apply?
It applies to two environments: the Developer Console (Dev org), where partners build and test applications, and Subscriber orgs, where end customers use the application.

4. Is adoption of Next Gen UI optional?
It is optional in the initial phase and becomes mandatory on December 25, 2026. Any new app created in Vertical Studio ahead of the mandatory date will use Next Gen UI by default, and partners may preview it at any time before then.

 Sequencing: Developer Console and Subscriber Orgs

5. Does the Developer Console transition ahead of subscriber orgs?
Yes. New apps in the Developer Console will default to Next Gen UI starting on October 25, 2026, giving partners advance exposure ahead of the subscriber-side transition on December 25, 2026.

6. Can an org remain on Next Gen UI in the Developer Console while keeping subscriber orgs on the old UI indefinitely?
No, this is not a supported configuration. Once October 25, 2026 arrives (or a grace period ends), both environments transition together.
7. Can individual apps within the same Developer console org be on different UI versions?
No, this is not possible. Before Stage 2 (December 25, 2026), the partner could request Next Gen UI for test accounts.

8. Is partial adoption supported under any circumstances?
No, mixed states are not supported, either between the Developer Console and subscriber orgs or across apps within an organization once the mandatory date takes effect.

Note: If the partner reaches out to us with such a request, the team will enable Next Gen UI in a test account.

 Grace Periods

9. Can a partner request additional time before transitioning?
Yes. Requests should be submitted to Vertical Studio support at support@zohoverticalstudio.com before December 25, 2026, and will be evaluated for a grace period.

10. Can a partner request a grace period for only one environment?
No, grace periods apply to the organization as a whole and cannot be applied selectively to the Developer Console or subscriber orgs.

11. Can a partner request an extension after the mandatory transition date has passed?
No, grace periods must be requested before the mandatory date. This process is designed to support proactive planning, not retroactive extensions once an organization has already reached the transition deadline.

12. Does an approved grace period apply to both the Developer Console and subscriber orgs, or only one?
Both. The organization transitions as a whole at the end of the grace period; grace periods cannot be applied selectively to one environment.

13. Who is authorized to approve grace period requests?
Zoho's support team, through the designated Vertical Studio support channel. Further details on this channel will be shared once finalized.

14. What information should accompany a grace period request?
At minimum: organization name, requested timeline, and a brief justification for why Next Gen UI adoption is not needed.
For instance, internal testing requirements, contractual obligations, or resourcing constraints.

 Previewing Next Gen UI

15. Can a partner/developer preview Next Gen UI before the mandatory date?
Yes. Since new apps default to Next Gen UI from Stage 1, creating a new app is the most direct way to preview the experience, and partners can request Next Gen UI for existing apps as well.

16. Can a partner preview Next Gen UI using a test subscriber account?
Yes. A test account allows partners to evaluate the subscriber-facing experience without affecting live customers.

17. What should partners review during a preview?

Checklist:

    1. Check that all modules and their settings (fields, layouts, buttons, and workflows) are reachable and that the "+" Quick Create menu lists everything.
  2. Module Views
    1. Check that data displays correctly across Split, Grid, Chart, and Timeline views—including custom fields, widgets, filters, and sort orders.
  3. Interactions View
    1. Check that the new unified Interactions view shows everything correctly.
  4. Reports & Analytics
    1. Check Reports and Analytics, including folders, dashboards, and charts.
  5. Theming
    1. Check custom theme colors in both light and dark modes.
    2. Check logo/branding is visible and readable in the new sidebar/header
  6. Preview Coverage
    1. Preview in both environments : a new app in the Dev Console and a test/sandbox subscriber account.
  7. Before the Deadline
    1. Request a grace period early if you need more time
    2. Plan your one-month subscriber notice before the switch takes effect
    3. Remember that there's no reverting once you've transitioned.

 Theming and Customization 

18. Will a partner's existing theme settings carry over exactly as they are today when Next Gen UI is enabled?
No, theme settings need to be reviewed as part of this transition. There are some differences in theme colours between the old and new UI. A partner's existing color scheme may render slightly differently under Next Gen UI. 

NotesAdditional note: The partner does not need to publish anything for this. Next Gen UI switches on automatically at the transition point - no manual action required on the partner's side. So publishing a new app version won't change how the theme colors render either; that rendering difference comes from the platform-level UI change itself, not from anything in the app's published state. For now, the only thing a partner can do is preview their theme in a test account and change theme from Next Gen UI if it looks off.

 Publishing, Versioning, and Technical Behaviour

19. Does a partner need to publish a new app version when Next Gen UI is enabled?
No, next Gen UI is a platform-level interface change and does not require a new app version. It is applied automatically at the point of transition.
20. If the Developer Console transitions, does the subscriber org update automatically, or does the partner need to take action?
The transition is automatic and governed by the rollout timeline or the organization's grace period end date. No manual publishing action is required on the partner's side.
21. Will custom code, widgets, or client scripts be affected?
They will not be affected. This is a navigation and workspace redesign, not a functional change, and existing customizations will continue to operate. Partners are encouraged to preview their app in Next Gen UI in advance to confirm layout and appearance.
22. Will integrations, APIs, or webhooks be affected?
No, they will not be affected.
Next Gen UI is a front-end interface change only. Underlying APIs, integrations, and data structures are unaffected.
23. Will this change impact application performance?
No negative impact is expected. Next Gen UI is built to be more efficient than the current interface.
24. Is localization and language support retained in Next Gen UI?
Yes. Localization support is unchanged, as this update affects the interface layer only.
25. Are there any features that are not supported in the new UI?
Teamspace, Team Modules, Work Queue, and Zia-related features are not currently supported in the new UI and are planned for a future release. The Tab Groups feature will be deprecated with the introduction of the new UI.

 Reverting to the Previous UI

26. Can an organization revert to the old UI once fully transitioned?
This is not possible . Once an organization completes the transition, whether voluntarily or at the mandatory date, the previous interface is retired and reverting is not supported.
27. What if a partner transitions early via a new app and wishes to revert?
Since new apps default to Next Gen UI at creation, reversal at the individual app level may not be technically feasible.

 Communication and Support

28. How will partners be informed of the transition?
Partners will be informed through multiple channels: in-app deprecation and reminder banners (beginning October 25, 2026), direct email communication with specific dates, and the support channel for questions or grace period requests.
29. What happens if a partner takes no action?
The organization will transition automatically at Stage 2 (December 25, 2026) or at the end of an approved grace period. No action is required for the transition itself to occur; action is only needed if requesting additional time.
30. Will subscribers experience any data loss, downtime, or need for reconfiguration during the transition?
This is a UI-layer change only, with no impact on data, application settings, or configuration.
31. Who should partners contact with questions or to request an extension?
The designated Vertical Studio support channel. Until this channel is finalised, requests should be routed through the standard support process.
32. Is there training or enablement material available for partners?
Currently available resources include the public announcement post and the in-app "Learn more" panel. Additional enablement material, such as a walkthrough, should be flagged to the enablement team if needed.