Enhanced Frontend Flow and Usability for Tasks, Care Plan and Daily Reports

[Manshant7]

Description

This PR focuses on improving the frontend usability, consistency, and overall flow of the Tasks, Care Plan, and Daily Report sections in the Guardian application.
The assigned task was to refine task-related screens, care plan screens, and daily report pages. Based on this, I reviewed how users interact with these features and made several improvements to ensure smoother navigation, clearer data presentation, and better UI behaviour.
Along with the assigned work, I also made additional improvements to enhance the overall user experience and frontend stability.

Work Completed

1. Reviewed task-related screens and improved their structure and usability
2. Refined care plan screens to display information more clearly
3. Improved daily report pages for better readability and organisation
4. Improved page behaviour to ensure smoother interaction
5. Enhanced frontend flow between different screens
6. Improved consistency across UI components

Additional Improvements

1. Fixed minor UI inconsistencies and alignment issues across screens
2. Improved button interactions and navigation behaviour
3. Cleaned up frontend code to improve readability and maintainability
4. Improved handling of Firebase data to ensure correct and stable display
5. Ensured smoother transitions between activities/fragments
6. Made small stability improvements to reduce unexpected UI issues

Why these changes were needed

The previous implementation had some inconsistencies in user flow and UI behaviour, which could affect how users interact with important features like tasks and care plans. These updates improve clarity, usability, and make the application more stable from a frontend perspective.

Testing

• Manually tested navigation between Tasks, Care Plan, and Daily Report screens
• Verified correct data display from Firebase
• Checked UI consistency and responsiveness across screens

Notes

These changes mainly focus on frontend improvements and user experience, with no major backend modifications.

[sakthiarajapandian27]

This PR delivers meaningful frontend improvements across the Tasks, Care Plan, and Daily Report sections of the Guardian app. Key highlights include proper input validation before Firebase writes, button disabling to prevent duplicate submissions, Firebase listener deduplication to avoid stale callbacks, and null/empty state handling to prevent crashes on missing data. Loading states and user-friendly error messages have also been added throughout, improving overall UX consistency.
The code is clean, well-commented, and applies good defensive programming patterns consistently across all modified files.
I am unsure about gitignore, if that can be apporved.
Good work!

[KudratAroraa]

Approved from the scope side of this PR.

The work done within the intended scope of this PR looks meaningful and aligned with the stated goal of improving the Tasks, Care Plan, and Daily Report sections. The changes improve frontend usability, strengthen validation, reduce repeated listener issues, and make several screens behave more consistently from a user experience perspective. From a scope and implementation direction point of view, this is a solid contribution and the intended improvements are valid.

A few good points in this PR are the added validation before saving tasks, improved button-state handling to avoid repeated actions, cleaner care plan summary rendering with fallback values, and better handling of empty or missing data. These are practical frontend improvements that help stability and make the screens easier to use.

For future scope, the Daily Report flow can be improved further by replacing the current placeholder or demo-style behaviour with full data-backed functionality. The report can later be connected to real persistence, real reporter details, actual navigation flows, and proper submission handling so that it moves beyond frontend demonstration and becomes part of the complete patient workflow. It could also be extended with better state restoration, clearer success/error feedback, and stronger integration with the related patient and task modules.

However, for now this PR should not be merged into main yet because it contains several out-of-scope files, especially local IDE/configuration files such as .idea and related project-environment files, which are not part of the functional scope of this work. The PR needs to be cleaned up so that it includes only the files relevant to the actual Tasks, Care Plan, and Daily Report improvements. Once that cleanup is done, it should be in a good state to merge.

[KudratAroraa]

Remove the unwanted files.