AsiaCel
shalom goyim
★★★★★
- Joined
- Nov 24, 2017
- Posts
- 30,123
- Online time
- 15h 39m
I hate android UI design so fucking much.
WHY ARE THERE SO MANY FUCKING PROPERTIES FOR A SINGLE CLASS IN ANDROID
WHY ARE THERE SO MANY FUCKING LAYOUTS FOR A SINGLE THING
WHY USING GOOGLE MATERIAL CLASS CRASH WITHOUT APP THEME
Why the fuck can't you chain two drawe layouts together and must use the trashy material modules?
Why does new Samsung phones close apps by swiping, making these drawer layouts stupid hard to use?
It's so frustrating that there is no "right". In the scripts, if you have the wrong class or data, it gives you an error with red underline — easy. But it doesn't work like that for UI.
I try to ask the AI bots to solve my UI issues but if you put their code in, your screen will go full white. AI can barely fix frontend shit.
If anyone tells me my UI is old once again, I will curse the pride of odin upon them.
Release me from this hell and send me back to the days of asp net bootstrap 5. Hell, even, I much prefer the android java async hell over this.
My UI was done already; then I was told to change it to "modern" because it looked "old". Well guess what, "modern" UIs are nightmare to deal with, even more so than making the old UIs in android.
It's not that I hate modern UI, but they're stupid difficult to deal with and a waste of time.
It didn't helped I was told to make it support portrait and landscape, which I have no experience in and don't want to deal with.
And also the stupid fucking animations. Just let me script a button that moves the UI from XY 1,1 to XY 2,2.
Modern UI is cool, but they don't pay me enough to make it "modern" and deal with all the fuckery.
Why do you need "modern" UI for an internal app used by like 3 people at max every few months anyway...
WHY ARE THERE SO MANY FUCKING PROPERTIES FOR A SINGLE CLASS IN ANDROID
WHY ARE THERE SO MANY FUCKING LAYOUTS FOR A SINGLE THING
WHY USING GOOGLE MATERIAL CLASS CRASH WITHOUT APP THEME
Why the fuck can't you chain two drawe layouts together and must use the trashy material modules?
Why does new Samsung phones close apps by swiping, making these drawer layouts stupid hard to use?
It's so frustrating that there is no "right". In the scripts, if you have the wrong class or data, it gives you an error with red underline — easy. But it doesn't work like that for UI.
I try to ask the AI bots to solve my UI issues but if you put their code in, your screen will go full white. AI can barely fix frontend shit.
If anyone tells me my UI is old once again, I will curse the pride of odin upon them.
Release me from this hell and send me back to the days of asp net bootstrap 5. Hell, even, I much prefer the android java async hell over this.
My UI was done already; then I was told to change it to "modern" because it looked "old". Well guess what, "modern" UIs are nightmare to deal with, even more so than making the old UIs in android.
It's not that I hate modern UI, but they're stupid difficult to deal with and a waste of time.
It didn't helped I was told to make it support portrait and landscape, which I have no experience in and don't want to deal with.
And also the stupid fucking animations. Just let me script a button that moves the UI from XY 1,1 to XY 2,2.
Modern UI is cool, but they don't pay me enough to make it "modern" and deal with all the fuckery.
Why do you need "modern" UI for an internal app used by like 3 people at max every few months anyway...
Last edited:





