Skip to content

[Mobile] Add skeleton loading to HomeScreen#294

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

[Mobile] Add skeleton loading to HomeScreen#294
Devasy wants to merge 1 commit intomainfrom
jules-ux-mobile-skeleton-16733077764637405702

Conversation

@Devasy
Copy link
Owner

@Devasy Devasy commented Feb 27, 2026

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

Changes:

  • Created mobile/components/ui/Skeleton.js: A generic pulsing skeleton primitive using Animated and Surface.
  • Created mobile/components/skeletons/GroupListSkeleton.js: A composite skeleton mimicking the HapticCard group list layout.
  • Integrated GroupListSkeleton into mobile/screens/HomeScreen.js, replacing the ActivityIndicator.
  • Updated .Jules/todo.md and .Jules/changelog.md.

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

Summary by CodeRabbit

  • New Features
    • Added skeleton loading animation for the mobile group list, displaying a pulsing visual placeholder that mirrors the final content layout during data loading.
    • Improved accessibility with dedicated screen reader announcements for the loading state.

Co-authored-by: Devasy23 <110348311+Devasy23@users.noreply.github.com>
@Devasy Devasy requested a review from vrajpatelll as a code owner February 27, 2026 20:21
@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.

@netlify
Copy link

netlify bot commented Feb 27, 2026

Deploy Preview for split-but-wiser canceled.

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 27, 2026

Walkthrough

This pull request introduces a skeleton loading feature for the HomeScreen group list. It adds a generic Skeleton component with pulsing animation, a GroupListSkeleton component that mirrors the HapticCard layout, and integrates both into HomeScreen to replace the existing activity indicator loading state.

Changes

Cohort / File(s) Summary
Documentation Updates
.Jules/changelog.md, .Jules/todo.md
Added changelog entry documenting the new mobile skeleton loading feature and marked the corresponding task as completed (2026-02-09).
Skeleton Loading Components
mobile/components/ui/Skeleton.js, mobile/components/skeletons/GroupListSkeleton.js
Introduced two new components: a generic Skeleton primitive with configurable dimensions, border radius, and pulsing animation via theme colors, and a GroupListSkeleton that renders a FlatList of skeleton-styled group items matching the HapticCard layout with accessible labels.
HomeScreen Integration
mobile/screens/HomeScreen.js
Updated the loading state to use GroupListSkeleton instead of ActivityIndicator spinner when data is being loaded.

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 pull request title clearly and concisely summarizes the main change: adding skeleton loading UI to the HomeScreen component in the mobile app.
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 27, 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     #294   +/-   ##
=======================================
  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/ui/Skeleton.js`:
- Around line 30-37: The Skeleton component is announcing every instance as a
progressbar via the Animated.View accessibilityRole and accessibilityLabel;
change the primitive to be decorative by default by removing or disabling those
attributes and adding an explicit opt-in prop (e.g., a boolean prop like
announce or accessibleLabel/announceAccessibility) that, when provided/true,
sets accessibilityRole="progressbar" and accessibilityLabel to the given string.
Update the Animated.View usage in Skeleton.js to default to non-accessible
(accessible={false} or omit accessibility props) and wire the new prop so
callers (only when needed) can opt-in to screen-reader announcements; update
GroupListSkeleton renderers to not opt-in so the high-level "Loading groups"
remains the single announcement.

ℹ️ 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 c9ef50a.

📒 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 +30 to +37
<Animated.View
style={[
{ opacity },
style,
]}
accessibilityRole="progressbar"
accessibilityLabel="Loading..."
>
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 | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check if files exist and examine the current Skeleton.js implementation
echo "=== Checking Skeleton.js ==="
if [ -f "mobile/components/ui/Skeleton.js" ]; then
  cat -n mobile/components/ui/Skeleton.js
else
  echo "File not found at mobile/components/ui/Skeleton.js"
  # Try to find it
  find . -name "Skeleton.js" -type f 2>/dev/null | head -10
fi

Repository: Devasy/splitwiser

Length of output: 1817


🏁 Script executed:

#!/bin/bash
# Check GroupListSkeleton.js
echo "=== Checking GroupListSkeleton.js ==="
if [ -f "mobile/components/skeletons/GroupListSkeleton.js" ]; then
  cat -n mobile/components/skeletons/GroupListSkeleton.js
else
  echo "File not found at mobile/components/skeletons/GroupListSkeleton.js"
  # Try to find it
  find . -name "GroupListSkeleton.js" -type f 2>/dev/null | head -10
fi

Repository: Devasy/splitwiser

Length of output: 2201


Do not announce each skeleton block as a progressbar.

Every Skeleton instance exposes itself as a separate progressbar with "Loading..." label via lines 35–36. In GroupListSkeleton.js, the renderItem() function creates 4 Skeleton instances per card (title, subtitle, avatar, status), which renders 5 times in a FlatList—resulting in 20 total progressbar announcements. This creates repetitive noise for screen-reader users and poor focus navigation, even though the container already has a high-level "Loading groups" announcement (line 30 of GroupListSkeleton).

Make this primitive decorative by default with accessibility opt-in only when needed.

Proposed fix
-const Skeleton = ({ width, height, borderRadius = 4, style }) => {
+const Skeleton = ({
+  width,
+  height,
+  borderRadius = 4,
+  style,
+  accessible = false,
+  accessibilityLabel,
+}) => {
@@
     <Animated.View
+      accessible={accessible}
       style={[
         { opacity },
         style,
       ]}
-      accessibilityRole="progressbar"
-      accessibilityLabel="Loading..."
+      accessibilityRole={accessible ? "progressbar" : undefined}
+      accessibilityLabel={accessible ? (accessibilityLabel || "Loading") : undefined}
     >
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@mobile/components/ui/Skeleton.js` around lines 30 - 37, The Skeleton
component is announcing every instance as a progressbar via the Animated.View
accessibilityRole and accessibilityLabel; change the primitive to be decorative
by default by removing or disabling those attributes and adding an explicit
opt-in prop (e.g., a boolean prop like announce or
accessibleLabel/announceAccessibility) that, when provided/true, sets
accessibilityRole="progressbar" and accessibilityLabel to the given string.
Update the Animated.View usage in Skeleton.js to default to non-accessible
(accessible={false} or omit accessibility props) and wire the new prop so
callers (only when needed) can opt-in to screen-reader announcements; update
GroupListSkeleton renderers to not opt-in so the high-level "Loading groups"
remains the single announcement.

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