Assignment 1, Task 2 - Update onboarding flow

[nriedman]

Customized onboarding flow with updated text and symbols

♻️ Current situation & Problem

The onboarding pipeline had default text and symbols from the Spezi Template.

⚙️ Release Notes

Updated the first and second screens to include Intake specific text and symbols. The first onboarding screen has an introduction to the Intake app, and the second describes the user journey through the app, listing the key components of the medical intake form the app will help them complete. I made sure all the strings were localized.

📚 Documentation

I did not make significant changes to the back-end code. I only changed text and symbols in the welcome and interesting_modules views.

✅ Testing

For this request, I will be relying on the default tests that we run every time we merge to main.

📝 Code of Conduct & Contributing Guidelines

By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

• [Y] I agree to follow the Code of Conduct and Contributing Guidelines.

[codecov]

Codecov Report

Attention: 18 lines in your changes are missing coverage. Please review.

Comparison is base (725e22f) 40.37% compared to head (ff1bd94) 40.03%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   40.37%   40.03%   -0.34%     
==========================================
  Files          30       30              
  Lines         939      947       +8     
==========================================
  Hits          379      379              
- Misses        560      568       +8     

Files	Coverage Δ
Intake/Onboarding/Welcome.swift	94.60% <100.00%> (ø)
Intake/Onboarding/InterestingModules.swift	0.00% <0.00%> (ø)

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 725e22f...ff1bd94. Read the comment docs.

[philippzagar]

Hi @nriedman ,

Thank you for the PR and the improvements. It's a great first version that only needs some more very minor changes!

Thank you for using the PR template! Please also add a more descriptive and clear title focusing on the added functionality rather than the assignment task. Also, fill out the Documentation and Testing part of the PR template, it's completely fine to state that you didn't do anything in that aspect within your PR.

Please also read through the "Keeping your pull request in sync with the base branch" documentation to ensure that your branch is up to date with the main branch before you merge it into the main branch.

Please re-request a review once you updated the branch to the main branch, you have updated the PR description, and addressed some of the in-line comments and I am happy to approve the PR to get it merged 🚀

[philippzagar]

@nriedman Please merge the main branch into your feature branch and resolve the merge conflicts in the Localizable file.

[philippzagar]

Thanks the last changes @nriedman, the PR is now ready to merge! 🚀