Skip to content

[jules] enhance: Add skeleton loading to mobile Home screen#298

Open
Devasy wants to merge 1 commit intomainfrom
jules/enhance/mobile-skeleton-loading-5893515721313771645
Open

[jules] enhance: Add skeleton loading to mobile Home screen#298
Devasy wants to merge 1 commit intomainfrom
jules/enhance/mobile-skeleton-loading-5893515721313771645

Conversation

@Devasy
Copy link
Owner

@Devasy Devasy commented Mar 8, 2026

What does this change?

This change adds a comprehensive skeleton loading experience to the mobile app's HomeScreen to improve the perceived performance and provide a better UX. It also implements a generic Skeleton component and refactors existing uses of inline loading states to utilize it.

Core Changes

  1. Created mobile/components/ui/Skeleton.js, a highly reusable component for generic loading states that utilizes Animated.loop for smooth pulsing.
  2. Created mobile/components/skeletons/GroupListSkeleton.js to specifically match the layout of the HomeScreen group cards.
  3. Updated mobile/screens/HomeScreen.js to render the GroupListSkeleton rather than a standard spinning ActivityIndicator while data is loading.
  4. Refactored mobile/screens/FriendsScreen.js to remove its messy, inline, and duplicated Animated skeleton logic and replace it with the new standard Skeleton component imports.
  5. Added relevant tracking updates to the todo.md, changelog.md and knowledge.md files in the .Jules folder.

This satisfies the UX todo: "Complete skeleton loading for HomeScreen groups".


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

Summary by CodeRabbit

  • New Features

    • Added animated skeleton placeholders to mobile screens during content loading, replacing spinner loaders with skeleton cards that preview the final layout.
  • Refactor

    • Standardized loading UI patterns across mobile screens with consistent skeleton components.

Creates reusable Skeleton and GroupListSkeleton components for the React Native App. Replaces the default ActivityIndicator on the Home screen and refactors the Friends screen to use the generic Skeleton instead of hardcoded Views.

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

Deploy Preview for split-but-wiser canceled.

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

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 8, 2026

Walkthrough

This pull request introduces a skeleton loading UI system for the mobile app. New generic Skeleton and GroupListSkeleton components are created, replacing previous ActivityIndicator and Animated-based loading visuals. HomeScreen and FriendsScreen are updated to use these new components, and project documentation is updated with changelog and development workflow notes.

Changes

Cohort / File(s) Summary
Documentation and Project Management
.Jules/changelog.md, .Jules/knowledge.md, .Jules/todo.md
Added changelog entry describing skeleton UI implementation; documented development workflows for mobile web builds, Playwright testing, and directory creation; marked skeleton loading task as completed with affected files and broader impact tracking.
Skeleton UI Components
mobile/components/ui/Skeleton.js, mobile/components/skeletons/GroupListSkeleton.js
Introduced generic Skeleton component with animated opacity transitions using theme-based colors, and GroupListSkeleton wrapper component for rendering multiple skeleton card items with configurable count.
Updated Screen Implementations
mobile/screens/HomeScreen.js, mobile/screens/FriendsScreen.js
Replaced ActivityIndicator and Animated-based loading visuals with new Skeleton components; removed legacy animation logic and hard-coded skeleton styles while preserving loading state behavior.

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 accurately describes the main change: adding skeleton loading to the mobile Home screen, which is the primary objective of this 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.

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.


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 Mar 8, 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     #298   +/-   ##
=======================================
  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: 3

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

Inline comments:
In @.Jules/changelog.md:
- Around line 127-130: The "### 2026-03-08" entry is nested under the earlier
"## [2026-01-01] - Initial Setup" section and lacks proper spacing; change the
heading "### 2026-03-08" to a top-level dated section (use "## 2026-03-08" or
the same format as other top-level dated headings) and ensure there is a blank
line immediately after that heading, and move the three bullet lines so they are
outside and below the initial setup section to form a standalone dated changelog
entry.

In @.Jules/knowledge.md:
- Around line 760-763: The Markdown heading "### Development Workflows"
currently has no blank line before the list which triggers markdownlint MD022;
insert a single blank line immediately after the "### Development Workflows"
heading so the subsequent bulleted list is separated from the heading (update
the block around the heading in .Jules/knowledge.md where "### Development
Workflows" appears).

In `@mobile/components/skeletons/GroupListSkeleton.js`:
- Around line 15-16: Remove the Skeleton from the Card.Title title prop
(currently using <Card.Title title={<Skeleton ... />}>), because title is
rendered inside a Text and cannot contain a View; instead move the Skeleton into
Card.Title's left or right render prop (use Card.Title's left={props =>
<Skeleton ... />} or right={...}) or replace Card.Title with a custom header row
component outside of Card.Title that composes a Text for the title and a
Skeleton View for the placeholder; update the GroupListSkeleton component to
render the Skeleton via the left/right callback or a custom header so no
Animated/View is passed into the title prop.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 259bb953-a769-4cd3-bc54-bc262a6f7008

📥 Commits

Reviewing files that changed from the base of the PR and between 9404621 and 3ef97fb.

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

Comment on lines +127 to +130
### 2026-03-08
- Added generic `Skeleton` component and `GroupListSkeleton` component to mobile app
- Replaced basic ActivityIndicator loading screen with `GroupListSkeleton` on mobile `HomeScreen`
- Refactored `FriendsScreen` inline skeleton logic to use the new generic `Skeleton` component
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

Make this a standalone dated changelog section.

This March 8 entry is currently nested under ## [2026-01-01] - Initial Setup, which makes the timeline misleading and also triggers the heading-spacing lint. It should be promoted to its own top-level dated section, with a blank line after the heading.

Suggested fix
-### 2026-03-08
+## [2026-03-08] - Mobile skeleton loading
+
 - Added generic `Skeleton` component and `GroupListSkeleton` component to mobile app
 - Replaced basic ActivityIndicator loading screen with `GroupListSkeleton` on mobile `HomeScreen`
 - Refactored `FriendsScreen` inline skeleton logic to use the new generic `Skeleton` component
📝 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
### 2026-03-08
- Added generic `Skeleton` component and `GroupListSkeleton` component to mobile app
- Replaced basic ActivityIndicator loading screen with `GroupListSkeleton` on mobile `HomeScreen`
- Refactored `FriendsScreen` inline skeleton logic to use the new generic `Skeleton` component
## [2026-03-08] - Mobile skeleton loading
- Added generic `Skeleton` component and `GroupListSkeleton` component to mobile app
- Replaced basic ActivityIndicator loading screen with `GroupListSkeleton` on mobile `HomeScreen`
- Refactored `FriendsScreen` inline skeleton logic to use the new generic `Skeleton` component
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)

[warning] 127-127: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.Jules/changelog.md around lines 127 - 130, The "### 2026-03-08" entry is
nested under the earlier "## [2026-01-01] - Initial Setup" section and lacks
proper spacing; change the heading "### 2026-03-08" to a top-level dated section
(use "## 2026-03-08" or the same format as other top-level dated headings) and
ensure there is a blank line immediately after that heading, and move the three
bullet lines so they are outside and below the initial setup section to form a
standalone dated changelog entry.

Comment on lines +760 to +763
### Development Workflows
- The mobile project is configured with `react-native-web`. You can test it in a browser using `npx expo start --web`.
- Use `AsyncStorage` values (`auth_token`, `refresh_token`, `user_data`) directly into Playwright's `window.localStorage` to bypass login flows for Playwright testing via react-native-web.
- When creating files in new subdirectories inside `/mobile/`, use `mkdir -p` before the write operation to ensure the path exists.
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

Add a blank line below this heading.

markdownlint is right here: the new ### Development Workflows heading is immediately followed by a list, so this block currently violates MD022.

Suggested fix
 ### Development Workflows
+
 - The mobile project is configured with `react-native-web`. You can test it in a browser using `npx expo start --web`.
 - Use `AsyncStorage` values (`auth_token`, `refresh_token`, `user_data`) directly into Playwright's `window.localStorage` to bypass login flows for Playwright testing via react-native-web.
 - When creating files in new subdirectories inside `/mobile/`, use `mkdir -p` before the write operation to ensure the path exists.
📝 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
### Development Workflows
- The mobile project is configured with `react-native-web`. You can test it in a browser using `npx expo start --web`.
- Use `AsyncStorage` values (`auth_token`, `refresh_token`, `user_data`) directly into Playwright's `window.localStorage` to bypass login flows for Playwright testing via react-native-web.
- When creating files in new subdirectories inside `/mobile/`, use `mkdir -p` before the write operation to ensure the path exists.
### Development Workflows
- The mobile project is configured with `react-native-web`. You can test it in a browser using `npx expo start --web`.
- Use `AsyncStorage` values (`auth_token`, `refresh_token`, `user_data`) directly into Playwright's `window.localStorage` to bypass login flows for Playwright testing via react-native-web.
- When creating files in new subdirectories inside `/mobile/`, use `mkdir -p` before the write operation to ensure the path exists.
🧰 Tools
🪛 markdownlint-cli2 (0.21.0)

[warning] 760-760: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.Jules/knowledge.md around lines 760 - 763, The Markdown heading "###
Development Workflows" currently has no blank line before the list which
triggers markdownlint MD022; insert a single blank line immediately after the
"### Development Workflows" heading so the subsequent bulleted list is separated
from the heading (update the block around the heading in .Jules/knowledge.md
where "### Development Workflows" appears).

Comment on lines +15 to +16
<Card.Title
title={<Skeleton width={120} height={20} borderRadius={4} />}
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 | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

In react-native-paper 5.14.5, how does Card.Titlerender thetitle prop, and when supplying a custom component instead of text should it be passed as a render function?

💡 Result:

In react-native-paper@5.14.5, Card.Title renders title as children of a text component:

  • It picks TitleComponent = theme.isV3 ? Text : Title, then renders:
    • <TitleComponent ...>{title}</TitleComponent> (github.com)

Because title is placed inside Text/Title, it will only work with a string or <Text>-based node (anything that ultimately renders as React Native <Text>). Passing a component that renders a <View> (or contains one) will fail with the usual “<View> within <Text>” nesting error. (callstack.github.io)

For a “custom component” title:

  • Do not pass a render functiontitle is not a render-prop; it’s a React.ReactNode rendered directly as children. (callstack.github.io)
  • If you want custom layout (icon + text, multiple views, etc.), use left/right (which are render callbacks) or build your own header row instead of relying on title. (callstack.github.io)

Citations:


Remove Skeleton from title; use left/right render props or build a custom header row instead.

Skeleton renders an Animated.View, but Card.Title's title prop is rendered directly as children of a Text component. Passing a view component here violates React Native's text nesting rules and causes a runtime error. The title prop does not accept render functions.

Use the left or right render callbacks (which accept functions) to place the Skeleton component, or build a custom header row outside of Card.Title if you need finer control over layout.

🤖 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 15 - 16,
Remove the Skeleton from the Card.Title title prop (currently using <Card.Title
title={<Skeleton ... />}>), because title is rendered inside a Text and cannot
contain a View; instead move the Skeleton into Card.Title's left or right render
prop (use Card.Title's left={props => <Skeleton ... />} or right={...}) or
replace Card.Title with a custom header row component outside of Card.Title that
composes a Text for the title and a Skeleton View for the placeholder; update
the GroupListSkeleton component to render the Skeleton via the left/right
callback or a custom header so no Animated/View is passed into the title prop.

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