Skip to content

[jules] ux: Add skeleton loading to mobile HomeScreen#293

Open
Devasy wants to merge 1 commit intomainfrom
jules-ux-mobile-skeleton-8108891635608244981
Open

[jules] ux: Add skeleton loading to mobile HomeScreen#293
Devasy wants to merge 1 commit intomainfrom
jules-ux-mobile-skeleton-8108891635608244981

Conversation

@Devasy
Copy link
Owner

@Devasy Devasy commented Feb 26, 2026

Implemented a complete skeleton loading system for the mobile HomeScreen to improve perceived performance.

  • Created a reusable Skeleton component (mobile/components/ui/Skeleton.js) using Animated for a pulsing opacity effect, with support for react-native-paper themes.
  • Created GroupListSkeleton (mobile/components/skeletons/GroupListSkeleton.js) that mimics the exact layout of the group list items (Avatar + Title + Subtitle).
  • Replaced the generic ActivityIndicator in HomeScreen.js with GroupListSkeleton.
  • Updated .Jules/todo.md and .Jules/changelog.md to track this enhancement.

PR created automatically by Jules for task 8108891635608244981 started by @Devasy23

Summary by CodeRabbit

  • New Features
    • Added animated skeleton loading state to the Home Screen group list, featuring pulsing placeholder cards that replace the loading spinner and prevent layout shifts when content loads.

Co-authored-by: Devasy23 <110348311+Devasy23@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 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.

@Devasy Devasy requested a review from vrajpatelll as a code owner February 26, 2026 19:45
@netlify
Copy link

netlify bot commented Feb 26, 2026

Deploy Preview for split-but-wiser canceled.

Name Link
🔨 Latest commit 4056a92
🔍 Latest deploy log https://app.netlify.com/projects/split-but-wiser/deploys/69a0a2e26d942d0008ebefd7

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 26, 2026

Walkthrough

This pull request introduces a pulsing skeleton loading UI for the HomeScreen group list. It creates a reusable Skeleton component with animated opacity transitions and a GroupListSkeleton component that renders five skeleton cards. The HomeScreen is updated to display GroupListSkeleton instead of ActivityIndicator during loading.

Changes

Cohort / File(s) Summary
Documentation Updates
.Jules/changelog.md, .Jules/todo.md
Updated changelog with new Mobile Skeleton Loading feature and marked the related task as completed on 2026-02-18.
Skeleton Components
mobile/components/ui/Skeleton.js, mobile/components/skeletons/GroupListSkeleton.js
Introduced reusable Skeleton component with animated opacity fading and GroupListSkeleton that renders five skeleton cards mimicking group list layout.
HomeScreen Integration
mobile/screens/HomeScreen.js
Replaced ActivityIndicator loading state with GroupListSkeleton component and added corresponding import.

Possibly related PRs

Suggested reviewers

  • vrajpatelll
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: adding skeleton loading to the mobile HomeScreen, which matches the core objective of the PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov
Copy link

codecov bot commented Feb 26, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@9404621). Learn more about missing BASE report.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #293   +/-   ##
=======================================
  Coverage        ?   63.55%           
=======================================
  Files           ?       21           
  Lines           ?     2456           
  Branches        ?      254           
=======================================
  Hits            ?     1561           
  Misses          ?      831           
  Partials        ?       64           
Components Coverage Δ
Authentication System 71.35% <ø> (?)
Expense Management 70.15% <ø> (?)
Group Management 73.78% <ø> (?)
User Management 97.16% <ø> (?)
Backend Core 70.78% <ø> (?)
🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@mobile/components/skeletons/GroupListSkeleton.js`:
- Around line 14-17: The Card.Title left callback currently uses hardcoded
dimensions for the avatar Skeleton; update the left prop in GroupListSkeleton
(the Card.Title left callback) to accept the { size } argument and pass that
size to the Skeleton (both width/height and borderRadius if appropriate) so the
skeleton avatar matches the Card.Title avatar sizing in react-native-paper v5.

ℹ️ Review info

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9404621 and 4056a92.

📒 Files selected for processing (5)
  • .Jules/changelog.md
  • .Jules/todo.md
  • mobile/components/skeletons/GroupListSkeleton.js
  • mobile/components/ui/Skeleton.js
  • mobile/screens/HomeScreen.js

Comment on lines +14 to +17
<Card.Title
title={<Skeleton width={150} height={20} />}
left={() => <Skeleton width={40} height={40} borderRadius={20} />}
/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🌐 Web query:

react-native-paper Card.Title left callback props style size v5

💡 Result:

In react-native-paper v5, Card.Title’s left prop is a callback that receives an object with a single field: size: number. You render your avatar/icon using that size (and optionally add your own styles). (oss.callstack.com)

Type

Related styling props

  • leftStyle?: StyleProp<ViewStyle> – styles the left-element wrapper (oss.callstack.com)
  • style?: StyleProp<ViewStyle> – styles the Card.Title container (oss.callstack.com)

Example

<Card.Title
  title="Card Title"
  left={({ size }) => (
    <Avatar.Icon size={size} icon="folder" />
  )}
  leftStyle={{ marginRight: 8 }}
/>

(oss.callstack.com)

Citations:


Use the provided size prop in the left callback for proper avatar alignment.

In react-native-paper v5, the Card.Title left callback receives only { size: number } and should use it to dimension the skeleton. The current code with hardcoded dimensions may misalign compared to real list items.

💡 Proposed fix
          <Card.Title
            title={<Skeleton width={150} height={20} />}
-           left={() => <Skeleton width={40} height={40} borderRadius={20} />}
+           left={({ size }) => (
+             <Skeleton
+               width={size}
+               height={size}
+               borderRadius={size / 2}
+             />
+           )}
          />
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<Card.Title
title={<Skeleton width={150} height={20} />}
left={() => <Skeleton width={40} height={40} borderRadius={20} />}
/>
<Card.Title
title={<Skeleton width={150} height={20} />}
left={({ size }) => (
<Skeleton
width={size}
height={size}
borderRadius={size / 2}
/>
)}
/>
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@mobile/components/skeletons/GroupListSkeleton.js` around lines 14 - 17, The
Card.Title left callback currently uses hardcoded dimensions for the avatar
Skeleton; update the left prop in GroupListSkeleton (the Card.Title left
callback) to accept the { size } argument and pass that size to the Skeleton
(both width/height and borderRadius if appropriate) so the skeleton avatar
matches the Card.Title avatar sizing in react-native-paper v5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant