As the app already uses google's material TextInputLayout, it also should use its great-looking way to show errors.
there are places where showing error takes space in editText and it makes it look bad because of compression.
for example:

some screenshots of after using material TextInputLayout way to show error
| CarSelectionAttributes Fragment |
HSN/TSN Fragment |
 |
 |
 |
|
@SebaDro @asaikarthikeya what are your thoughts on this way to show an error?
would like to hear your thoughts
[using this issue as a discussion]
another thought: we can use discussions given by GitHub, so every time a person wants to request a new feature they can propose in discussions, and once approved they can create a new issue
I think it will help in decreasing the stale issues which are not required to work for now :)
As the app already uses google's material TextInputLayout, it also should use its great-looking way to show errors.

there are places where showing error takes space in editText and it makes it look bad because of compression.
for example:
some screenshots of after using material TextInputLayout way to show error
@SebaDro @asaikarthikeya what are your thoughts on this way to show an error?
would like to hear your thoughts
[using this issue as a discussion]
another thought: we can use discussions given by GitHub, so every time a person wants to request a new feature they can propose in discussions, and once approved they can create a new issue
I think it will help in decreasing the stale issues which are not required to work for now :)