[FEATURE]: Enhancement of Onboarding Screen and Low Res Assets
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 61/100
Research direction
Start by locating the onboarding screen and its slide data, then inspect how accent colors and illustration assets are currently selected. Update the slides to use individual accent colors and sharper transparent illustrations, and check the active dots, buttons, and titles in light and dark modes. Done when each slide keeps its own branding across both modes and the illustrations render clearly.
Written by the indexing model from the issue text.
Description
Problem Description
The onboarding flow is currently tied directly to the global app theme (theme.colorScheme.primary). This creates visual clashes:
- Theme and Dark Mode Clashing: Switching themes or enabling dark mode causes dynamic primary colors to clash with the static illustrations.
- Low-Resolution Assets: The current onboarding PNGs are low resolution (~370x270 px) and render blurry on modern high-DPI displays.
- Uniform Accent: Every slide uses the exact same color rather than having distinct visual branding for each feature slide.
Proposed Solution
- Give each onboarding slide its own independent
accentColorso future theme changes in settings will not alter or break the onboarding design. - Replace low-resolution assets with clean, transparent illustrations from Storyset.
- Ensure active indicator dots, buttons, and titles adapt to the active slide's accent color in both light and dark modes.
Additional Context
Current Behavior
| Mode | Recording |
|---|---|
| Light Mode | |
| Dark Mode |
Code of Conduct
- I have joined the Discord server and will post updates there
- I have searched existing issues to avoid duplicates
- Dominant language
- Dart
- Stars
- 20
- Forks
- 39
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from StabilityNexus/Zplit
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
StabilityNexus/Zplit#77 · 1 comment ·
-
[GOOD FIRST ISSUE] [MINOR BUG]: Website uses default starter favicon instead of official Zplit logoPossibly taken A pull request linked to this issue is open or already merged. Opengood first issue
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
StabilityNexus/Zplit#73 ·
-
[GOOD FIRST ISSUE]: Documentation Cleanup - Addition of Contribution.mdPossibly taken @Logic769 claimed this 20 days ago. Opengood first issue
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
StabilityNexus/Zplit#64 · 2 comments ·
-
gsoc
Difficulty 4/5 3-5 days Newbie friendliness 48/100
StabilityNexus/Zplit#56 ·
-
gsoc
Difficulty 5/5 Over a week Newbie friendliness 35/100
StabilityNexus/Zplit#52 ·
All issues in StabilityNexus/Zplit
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
🚀 [firebase_core] Bump Firebase C++ SDK (14.1.0 → 14.2.0)Possibly taken @SelaseKay claimed this today. OpenNeeds Attention type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
firebase/flutterfire#18977 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AlphaWaveSystems/flutter-probe#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ubuntu/app-center#2306 ·
Maintainers usually reply within 1 day