In this episode, @urbanclap Android Team meets the passionate #Android folks @Zomato.
We discuss Recyclerview, its Adapter, scalability and optimising performance with @SajalGupta94, @_prtks & @_yashikakatyal.
Do listen in. There is tons of information.
https://t.co/WQiYJJJkHY
#AndroidDev and wanna know all this fuss about #Jetpackcompose.
Don't sweat much.
In this episode, we sit with @rivuchakraborty and deep dive into the internals, best practices, backward compatibility, and much more of the same.
Have a listen.
#android#androiddeveloper
2020 was a tough year for everyone, and it's even tough to be a #AndroidDev now with @google and @jetbrains pushing nonstop updates.
We have summarised d year that passed by and all d important updates in the #Android ecosystem in one place.
HNY 2021.
https://t.co/hwutNDA1Ey
We are proud to support the upcoming live@Manning Conference on #WomenInTech, October 13, 12-5pm ET. Join industry leaders to learn, be inspired, and connect with others working to advance inclusion in tech. Register today for free! #ManningLive https://t.co/lHbQzIEsj6
#Androidiots#Podcast 18 : Custom Lint
Lints are 1 of the easiest ways to maintain some code sanity for an #AndroidDev
In this episode @hitanshudhawan from @urbancompany_UC guides us how lints works in #android and write one of your own.
https://t.co/OewWmLdnDq
We chat with a @Tushar13091993 a fellow #AndroidGeek at @urbancompany_UC who deep dives into what goes behind running the plugins we all use and what it takes to create one of our own.
Have a listen.
#Jetbrains
#KotlinBytes 21 : #Kotlin has support for Position-based destructing declarations syntax for lambda parameters
Just use {} that include all the parameters that we want to de-structure into
But is it secure for Property Renaming or Property Reordering ??
#AndroidDev#KotlinTips
Each Java method that takes a SAM, the #Kotlin compiler generates a version that instead takes a function as an argument
Compiler generates SAM constructors and function methods only for Java SAMs. It does not generate SAM constructors for Kotlin interfaces with a single method.
#KotlinBytes 20 :
Higher-order functions are bread and butter of #Kotlin.
But what about Interoperability with #Java, which doesn’t supports it natively.
Hence It achieves substitution by using #interfaces with only one method called a Single Abstract Method (SAM).
#AndroidDev
SAMs are often used as a replacement for function definitions
#Kotlin generates a SAM constructor with the function type as a parameter
Which allows us to create an instance of a #Java SAM interface just by calling its name and passing either #Anonymousfunctions or a #Lambda
The invoke method is an operator function, and it can be used in the same way as function invocation
println(idiotVar.invoke(1)) //print 11
But what happens when we are keeping function in a nullable variable??
#AndroidDev#Kotlin#Android
#KotlinBytes 19 :
We can define function as an object in #kotlin by using anonymous functions
Eg:
val idiotVar: (Int) -> Int = fun(i: Int) = i * 11
println(idiotVar(1)) //prints 11
If we see the byte code of function type we find
there is only the invoke method inside it
Generics has always been a confusing yet very powerful topic in #java or #android add IN and OUT classes of #kotlin it becomes a TLDR
Give a read to simple yet elegant article by @tpolansk
https://t.co/LamT4V5Air
or deep using @urHIGHnnesss take on it
https://t.co/cJCojeIYsN
If your company requires you to work nights and weekends, your company is broken. This is a managerial problem, not your problem. This is a process problem, not a personal problem. This is an ownership problem, not an individual problem.