Oh boy, kotlin and its world of statics and lambdas are glorious 💗💗💗

I just finished this attendence counter app i have been working on for last 4 days.its quite simple so i tried to add as much constraints as possible:
-Good practices and minimal warningy
-Room database
-Viewmodel and livedata
-constraint layout
-everything in kotlin

Although i already have worked with room and livedata previously but i dont even have a hello world experience in kotlin . However it doesn't felt that bad tho for a newbie

Every code here is so small . Synthetic binding? Love at first sight.Although at some places its irritating , not having ?: Operator or its ugly 'when' logic, but overall its Awesome!!

!Rant && !Believe what I am seeing 😓

Just downloaded Android studio 3 to give kotlin a go to find out their designer is soooo much better now, I tried editing an activity with constraint layout and many elements inside without a single freez 😨

Android studio is a PATHETIC excuse of an IDE!! And managing a constraint layout inside a scroll view is worse than having my nails pulled out while a bamboo is growing into my spine at record time! Screw this piece of shit IDE!! I suck at front end bad enough to have to deal with its buggy frontend IDE!! Aaaah!!!! - pulls lumps of hair out-

GOD ALMIGHTY I HATE SWIFT & XCODE...

Why the fuck does it take a horrendous amount of time to muck about with layout constraints. Why the heck does xcode choose to add constraint layouts to elements that already have pissing constraints! Why does dealing with something as trivial as tables have to be so god damn fucking involved when HTML and CSS let me create and style tables in fuck all lines.

And what the hell is up with how pissing long xcode takes just to figure out that 1 extra line of code I've just added. You jump to another file and xcode finally decides to be an ide again and bitch at the fact that you've forgotten to add some parameter or that they've decided to rename paramter "x" since version fuck nows what.

Working with abstract classes is fun, lets use protocols (because interfaces are too old school) and then lets tack on something we call extensions and then lets make people piss about with convenience initializers.

And lord almighty, what the fuck is up with casting, what all this ?! BS. What's wrong with just checking if the value is null in the first place, or whats wrong with giving something an initial value, oh because having to unwrap shit is more elegant right??

And good god, I need to own a fucking cinema screen just to have the storyboard open, there's less fucking panels on the Sistine Chapel ceiling
then there is in xcode.

Constraint Layout is the best thing Google has ever made for responsive Android design, when it works.

Half the time it suddenly stops finding any elements I want to attach my selected one to, so it can't constrain what I want it to constrain.

A restart fixes it though...

Not sure if I am Allowed to ask general questions here but here's the thing. I just began making Android apps. I have made a few basic of them and I use constraint layout via the layout editor in Android Studio. Is it okay? Do professionals do the same or do they actually type in the xml code?

Constraint layout

To all android Devs who used to or still change Constraint layout as the root element of the view despite Google forcing it on us.
Your time is near....

I hate AndroidStudio when it adds constraint-layout as a dependency in my build script whenever I create a new Activity.

Damn. I just broke my ergonomic keyboard. I love learning Flutter, but it's layout system sometimes causes an unbounded rage constraint error in my brain.

Got an assignment yesterday. I was required to create an Android app. I used constraint layout for the app. However, instructor told me today not to use constraint layout. Instead use relative layout. He did not gave any explanations for it. What you think might be the reason? How many of you still use relative layout, and why?

Am I the only one waving around when working with the Constraint Layout in android....feeling like am directing traffic

when you enter to android studio 2.2.x..and you see how they just added the "constraint" layout... xcode? is that you?..

Fellas, what do you think about the performance of the Android Compose? Some time the first launch is too slow, I took 5 seconds to start the app. I had some problems with constraint layout too, simple constraints as link the bottom to top doesn't works well, the content stayed over the view, seems as the link was made to the bottom and not to top