Closed Bug 1826883 Opened 2 years ago Closed 10 months ago

Rename Juno onboarding references to represent new user onboarding

Categories

(Fenix :: Onboarding, task, P3)

All
Android
task

Tracking

(firefox122 fixed)

RESOLVED FIXED
122 Branch
Tracking Status
firefox122 --- fixed

People

(Reporter: jonalmeida, Assigned: rsainani)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxdroid])

Attachments

(1 file)

Based on an offline conversation with :jmahon, the new onboarding flow will be retained within our codebase after the Juno release, so we should avoid using that naming convention as there will be no long term reference to what "Juno" means after this release.

For a few examples, consider renaming:

  • isJunoOnboardingShown -> isNewUserOnboardingShown
  • JunoOnboardingFragment -> NewUserOnboardingFragment
  • JunoOnboardingMapper.kt -> NewUserOnboardingMapper.kt

We have discussed this in https://github.com/mozilla-mobile/firefox-android/pull/1442#discussion_r1150978629. We could certainly use this bug to track this work.

Copying my comment from Bug 1826967 to close that as a duplicate:

(I hadn't seen this ticket prior to writing this comment, sorry!)

I'm worried about the conceptual debt involved in encoding the term "Juno" into the codebase. After the Juno marketing moment passes in June 2023, the term "Juno" will be somewhat confusing to see still floating around. E.g., we shouldn't refer to the new card-based onboarding flow as "Juno Onboarding", since that might imply it's only part of the Juno release (v114), whereas this new onboarding redesign will be used in perpetuity after Juno.

I think it'd be helpful to remove references to Juno - at least in places where it's easy to do so - to prevent this confusion. If simply calling it "onboarding" isn't specific enough, perhaps a descriptive name would work better, e.g. "cardBasedOnboarding" or "onboardingV2" to distinguish it from the previous flow.

Duplicate of this bug: 1826967
Severity: -- → N/A
Priority: -- → P3

Now that the older scrolling onboarding has been removed, we can simply remove the Juno prefix and not add a New prefix as that'll be incorrect after a while too.

Assignee: nobody → rsainani
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Flags: qe-verify+
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: