Bug: Hardcoded Height and Width Used Throughout the Codebase

[ganidande905]

Description:

I have noticed that the height and width values are hardcoded at various places in the codebase, even though Get.height and Get.width (or similar responsive utilities) are available for dynamic dimensioning.

Disadvantages of Hardcoding Height and Width:

1.Lack of Responsiveness:

• Hardcoded dimensions do not adapt to different screen sizes or orientations, leading to poor user experience on devices with varying resolutions.

2.Inconsistent UI:

• Hardcoded values may cause inconsistencies across different screen sizes.

3.Difficulty in Maintenance:

• Updating UI for new screen sizes or layouts requires manually changing hardcoded values throughout the code, which is error-prone and time-consuming.

4.Inflexibility for Dynamic Content:

• Hardcoded dimensions can break layouts when the app content changes dynamically (e.g., localization, font scaling, or varying data).

5.Reduces Code Reusability:

• Widgets or components with hardcoded dimensions are less reusable, limiting modularity and scalability.

6.Inefficient Testing:

• Testing becomes cumbersome as hardcoded values need validation for multiple screen configurations and edge cases.

Suggested Solution:

• Utilize Flutter widgets like LayoutBuilder or MediaQuery in cases where Get.height and Get.width are not directly applicable.

By addressing this issue, we can enhance the responsiveness, maintainability, and overall quality of the app's user interface

Solving this issue could also solve the issue #611

[ganidande905]

hey @AryanSarafDev could you just go through this issue and assign this to me and also the issue which is co-related to this issue #611