FEAR Launcher Master UI/UX Redesign

[minetwice]

User description

This commit completely removes any leftover silver/white button styles and replaces them with a gorgeous, high-end FEAR Launcher Master UI/UX redesign. Key visual changes include:

• A new 'premium_play_button_bg.xml' featuring a stunning cyber-blue neon glow, state transitions, gloss shine overlays, and rounded corners.
• Refined glassmorphism backing inside 'premium_glass_black_bg.xml' leveraging a subtle blue neon glowing outline stroke.
• Perfectly aligned and modernized Header (Top Left Logo & Title; Top Right Avatar, Notification, and 3-Dot slide-drawer trigger).
• Updated central card layout for both landscape and portrait orientations hosting the Minecraft Version spinner, Username, JVM status labels, edit/settings sub-buttons, and the large hero Play button.
• Registered click listeners and functionality inside MainMenuFragment.java to support all interactive elements.

PR created automatically by Jules for task 12816839325924262630 started by @minetwice

---

CodeAnt-AI Description

Refresh the launcher home screen and account flow, and remove the startup splash

What Changed

• The launcher now opens directly into the main screen instead of playing the splash animation first
• The home screen and side drawer were redesigned with a new header, larger Play button, skin head preview, rotating chat messages, and new shortcuts for skin settings, account hub, addons, and creators info
• The account manager now lets users select an account, switch to it, add Microsoft or local profiles, and remove accounts from a menu, with username checks shown for local profiles
• Addon browsing can open straight to mods, resource packs, or shaders, and search results stay available even if one source fails
• Skin previews now render sharper, show only the head when needed, and display textures correctly on the model
• System telemetry was removed from the drawer, and the creators/info view was added with links to the project channels

Impact

✅ Faster app startup
✅ Fewer account-switching mistakes
✅ Quicker access to mods, shaders, and resource packs

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[codeant-ai]

CodeAnt AI is reviewing your PR.

[codeant-ai]

Suggestion: These new dashboard entry points open the full-screen dialog without first collapsing settings_tray, unlike the existing tray dashboard action; if the tray is already open, dismissing the dialog leaves stale tray state visible underneath. Reuse the same flow as the tray action (collapse tray before opening dashboard) to keep UI state consistent. [logic error]

Severity Level: Major ⚠️

- ⚠️ Main menu tray can remain visible after dashboard.
- ⚠️ Header/avatar dashboard entry points ignore tray lifecycle.
- ⚠️ UI/UX inconsistent with tray Settings button behavior.

Steps of Reproduction ✅

1. Open the launcher main screen so `MainMenuFragment` is active; the fragment uses layout
`R.layout.fragment_launcher` via its constructor at
`app_pojavlauncher/src/main/java/net/kdt/pojavlaunch/fragments/MainMenuFragment.java:124-126`,
and binds the new header and card buttons in `onViewCreated()` at lines 139-147 and their
click listeners at lines 165-179.

2. Tap the hamburger menu button (`R.id.hamburger_menu_icon`) on the header; its click
handler at lines 189-203 sets `settings_tray` visible and plays the slide-in animation,
leaving the tray open on top of the main layout.

3. With `settings_tray` still open, tap either the center-card settings button
(`R.id.settings_button_main`) or the header avatar card (`R.id.header_avatar_card`); their
listeners at lines 165-171 and 173-179 call `openCommandDashboard()` directly without
invoking `collapseTray(settingsTray)`, unlike the tray Settings button flow at
`app_pojavlauncher/src/main/java/net/kdt/pojavlaunch/fragments/MainMenuFragment.java:318`
which first calls `collapseTray(settingsTray)` before `openCommandDashboard()`.

4. In the full-screen dashboard dialog created by `openCommandDashboard()` at
`app_pojavlauncher/src/main/java/net/kdt/pojavlaunch/fragments/MainMenuFragment.java:427-170`,
press the Back or Done buttons wired at lines 175-184; they dismiss the dialog but never
touch `settings_tray`, so after dismissal the slide-out tray remains visible in its
previous state underneath, producing inconsistent UI state compared to the tray-initiated
dashboard flow.

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖

This is a comment left during a code review.

**Path:** app_pojavlauncher/src/main/java/net/kdt/pojavlaunch/fragments/MainMenuFragment.java
**Line:** 165:179
**Comment:**
	*Logic Error: These new dashboard entry points open the full-screen dialog without first collapsing `settings_tray`, unlike the existing tray dashboard action; if the tray is already open, dismissing the dialog leaves stale tray state visible underneath. Reuse the same flow as the tray action (collapse tray before opening dashboard) to keep UI state consistent.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

👍 | 👎

[codeant-ai]

Suggestion: Adding GlassParticleView as a full-screen always-visible layer on the main launcher screen introduces continuous rendering work; this view invalidates itself every frame, so keeping it permanently mounted here will cause unnecessary CPU/GPU usage and battery drain. Pause/remove this layer when idle or throttle its redraw rate before using it on the home screen. [performance]

Severity Level: Critical 🚨

- ❌ Launcher idle screen continuously consumes GPU/CPU cycles.
- ⚠️ Increased battery drain while launcher stays open.
- ⚠️ Potential frame drops on lower-end devices.
- ⚠️ Performance regression versus static background designs.

Steps of Reproduction ✅

1. Open the launcher home screen which inflates `fragment_launcher.xml` via
`MainMenuFragment` (constructor at
`app_pojavlauncher/src/main/java/net/kdt/pojavlaunch/fragments/MainMenuFragment.java:124-126`);
the layout now includes a full-screen `GlassParticleView` at lines 10-13
(`android:layout_width="match_parent"` and `android:layout_height="match_parent"`).

2. At runtime, Android constructs `com.kdt.mcgui.GlassParticleView` from
`app_pojavlauncher/src/main/java/com/kdt/mcgui/GlassParticleView.java`; its `onDraw()`
implementation at lines 31-55 iterates particles, draws them, and then calls
`invalidate()` unconditionally at line 55.

3. Because the `GlassParticleView` covers the entire launcher background and
`invalidate()` is called every frame, the view continuously redraws while the fragment is
visible, even when the user is idle on the home screen, causing ongoing GPU/CPU activity
instead of a static background.

4. Leave the launcher open on this screen; the continuous invalidation loop from
`GlassParticleView.onDraw()` keeps the render pipeline active for the lifetime of the
fragment, leading to unnecessary battery drain and performance overhead on the main UI
surface.

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖

This is a comment left during a code review.

**Path:** app_pojavlauncher/src/main/res/layout/fragment_launcher.xml
**Line:** 10:13
**Comment:**
	*Performance: Adding `GlassParticleView` as a full-screen always-visible layer on the main launcher screen introduces continuous rendering work; this view invalidates itself every frame, so keeping it permanently mounted here will cause unnecessary CPU/GPU usage and battery drain. Pause/remove this layer when idle or throttle its redraw rate before using it on the home screen.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

👍 | 👎

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[codeant-ai]

CodeAnt AI is running Incremental review

[codeant-ai]

CodeAnt AI Incremental review completed.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Incremental review completed	235772b	Jul 24, 2026 · 00:37	00:38
✅ Incremental review completed	84aad97	Jul 22, 2026 · 11:33	11:34
✅ Incremental review completed	62b9d29	Jul 22, 2026 · 08:26	08:27
✅ Incremental review completed	f525e3a	Jul 22, 2026 · 04:36	04:37
✅ Incremental review completed	8ac03ed	Jul 22, 2026 · 01:41	01:42

[kings880]

Fix it