Fit screen texts to Figma in string.xml or other

[taghizadlaura]

Description

The task focuses on refactoring the Sign In and Sign Up screens by moving all relevant texts, including placeholders, error messages, and button labels, into the strings.xml file. This aligns with the guidelines provided in the individual grade of M2. The task also involves adding text resources for Profile, Settings, Alert, and Chat features to ensure consistency across the app and improve localization support.

NOTE: The task focuses only on text refactoring in the strings.xml file. UI-related color adjustments will be handled in a separate task.

Done

Specific, measurable criteria to confirm the task is complete:

• Functional Requirements: All texts on the Sign In and Sign Up screens, including placeholders, error messages, and button labels, should be moved to strings.xml. This also applies to Profile, Settings, Alert, and Chat screens.
• Quality Standards: The text resources in strings.xml should be well-organized, follow naming conventions, and be easily understandable for localization.
• Testing Requirements: Ensure that all screens are using the correct string resources, and that there are no hardcoded strings in the UI. Update unit and UI tests to verify this.

Preconditions

• Existing UI for Sign In, Sign Up, Profile, Settings, Alert, and Chat screens.
• Existing layout files with placeholders, labels, and error messages.
• App follows a consistent theming structure, with UI components relying on the strings.xml for text rendering.

Steps to Completion

• Timer texts in string.xml #329
• SignIn/SignUp/Map texts in string.xml #334
• Create Profile / Edit Profile / Profile / Settings texts in strings.xml. #336
• Create Alert / Edit Alert / Alert Lists texts in strings.xml. #338
• Chat texts in strings.xml : It will be done directly in the next PR of the Chat implementation.

Points to Consider / Known Risks

• Localization: Consideration for different languages and the impact of longer or shorter text strings.
• Backward Compatibility: Ensure no existing features are broken due to this refactoring, particularly if the strings are deeply integrated into various UI components.
• Testing Complexity: Extensive testing across the Sign In, Sign Up, Profile, Settings, Alert, and Chat screens will be necessary to ensure consistency and correctness of the changes.