First iteration for making in-app trials 1 step with lead page
What does this MR do and why?
First iteration for making in-app trials 1 step with lead page
- break up !192026 (merged) into smaller, more reviewable chunks.
- working towards the goal of making trial submission 1 step instead of 2.
- introduce new in-app trial form with only lead parts
- align the layout methodologies between user registration lead form and in-app trial lead forms so that advantages bits can be shared and for general standardization.
- see https://gitlab.com/gitlab-org/gitlab/-/issues/532644
- see #556777 (closed)
Screenshots or screen recordings
Click to expand
| page | Before | After |
|---|---|---|
free: /users/sign_up/company/new
|
 |
 |
free: /users/sign_up/company/new mobile |
 |
 |
trial: /users/sign_up/company/new
|
 |
 |
trial: /users/sign_up/company/new mobile |
 |
 |
/-/trials/new |
 |
 |
/-/trials/new mobile |
 |
 |
/-/trials/new video |
Screen_Recording_2025-05-30_at_2.03.43_PM | Screen_Recording_2025-05-30_at_1.58.45_PM |
How to set up and validate locally
Click to expand
- Setup gdk to simulate SaaS - https://docs.gitlab.com/ee/development/ee_features.html#simulate-a-saas-instance and restart GDK
Ultimate trial
- In rails console enable the feature flag
Feature.enable(:ultimate_trial_single_form) - visit
/-/trials/newpath.
Company/new
- go to
/-/trial_registrations/new, complete sign up form and welcome page, you should see the company form page. - go to regular signup, complete sign up form and welcome page, you should see the company form page.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #532644
Edited by Doug Stull