Closed
Description
Goal/Intended Outcome
Users are aware of JetBrains IDE’s when they first use Gitpod so that if they are a regular JetBrains user they can configure all future workspaces to use JetBrains.
Proposal
- Introduce a prompt for onboarding users (e.g. first workspace start)
- Present users with the current alternative IDE (JetBrains, etc) options, but also allow to dismiss
- If possible, we can directly update the preferences (or alternatively routing to the preferences page)
- On subsequent workspace starts we revert to the existing flow / respect existing preferences
Consideration(s)
- Embedding of logo's might help user perception (but not mandatory as part of the design)
- We should see this work as iterative, implement an experiment, and we can adapt/alter based on the results
Measurement (Experiment Dashboard)
- Increased conversion rate through the onboarding funnel
- Increase in retention for users who are more likely to use JetBrains as a daily driver
- Increased general adoption of the JetBrains feature
Note: Some dropoff to be expected by adding additional friction/step into the onboarding flow.
Out of scope
- VS Code Desktop (unless v.easy)
- Vim / SSH flows
- Implementing as A/B test
Issues
- Property aware users that they can choose IDEs with onboarding dashboard #9433
- Allow user to configure IDE configurations when onboarding start workspace #9534
- Analytics: Extend
ide_configuration_changed
analytics event withlocation
(e.g. dashboard, preferences, workspace start) #9791 - Analytics: Track modal dismissal #9790
- Analytics: git command events from JetBrains #9792
See Figma [1]
Metadata
Metadata
Type
Projects
Status
Done